Adding an engineer takes a minute. You send them an email, they set their own password and get themselves connected, then they're on your team and Mucka can book them into jobs.
Send the invite
Head to Settings → Team → People (the account card at the bottom of the sidebar). Tap Invite teammate and fill in:
- First and last name
- Email address (their personal one is best, since they'll tap the invite on their phone)
- Role (Owner, Manager, Engineer or Subcontractor)
Hit send. The new teammate gets an email with a one-tap link.
Or just ask Mucka
Tell Mucka "invite Kyle to the team" and it asks for his email, reads the name, email and role back, and sends the same invite once you say yes.
It also comes up on its own. Ask Mucka to put somebody on a job who isn't on your team yet and it won't book the job without saying anything: it tells you they're not on the team and asks whether to invite them. Give it their email and the invite goes. The job is booked without an engineer for now, because nobody can be put on a job until they've accepted. Once they have, ask Mucka to put them on it.
If they were invited already and haven't accepted, Mucka tells you that instead of sending a second invite.
Two things still happen on this page rather than by asking: resending an invite, and adding the first paid teammate to a one-person account. Subcontractors are free, so Mucka can invite those either way.
What happens next
- They tap the link and set a password
- They get a short setup of their own: pick the Mucka voice they'd like, connect WhatsApp, turn on phone alerts
- They appear in your Team list with a green "active" tag
- You can start assigning them to jobs straight away
Connecting WhatsApp is the one step they can't skip, and it's the important one. It's how your jobs, your changes and your messages actually reach them — without it there's nowhere for any of it to land, and nothing tells either of you it didn't arrive. Their side of it is written up in you've been invited onto a team if they get stuck.
Subcontractors skip that setup and go straight in, because Mucka never WhatsApps a subbie.
If the invite expires (rare, but it happens after 7 days), hit Resend next to it under Pending invitations on the same Team tab — that sends a fresh email and gives the link another 7 days.
Teammates that came in with your data
If we brought your jobs in from other software (JobLogic, say), your engineers came with them — they're already in your Team list with their job history attached, marked with a No login tag because they can't sign in yet.
Getting them signed in is one tap: hit Invite on their row. They get the same email, set a password, and they're in — as the same person, with all their existing jobs and history. No retyping, no duplicates.
Add their mobile number
Once they've joined, their row in Settings → Team → People has a Mobile box. Type their number and click away, it saves itself.
A number here is a number to ring — it isn't a way to message them. That's what their WhatsApp connection is for, and they set that up themselves during their own setup. Putting a mobile in for someone doesn't connect them.
Worth doing for everyone. It's the number Mucka gives you when you ask how someone's getting on, so you're not digging through your phone to find it. Type it however you like, 07700 900123 or +44 7700 900123 both work. If Mucka can't make sense of what you've typed it'll say so rather than save a number that won't work.
Pick the right role
Roles control what each person can see and do:
- Owner sees and changes everything, including billing and team
- Manager runs day-to-day operations (scheduling, quoting, invoicing) but not billing or team admin
- Engineer sees their own jobs, their own schedule and chats with Mucka about their day
- Subcontractor sees only the jobs you put them on, and their own schedule. No clients, no prices, no invoices
You can also build your own roles if none of those quite fit. See engineer roles and permissions.
Engineers can't see other engineers' jobs or your full client list. That's deliberate, it keeps day-to-day focus on what each person actually needs.
Assignable on jobs
Each person's row in Settings → Team → People has an Assignable on jobs box. It decides who you're offered when you book work, and that's all it does.
With it ticked, they're in the engineer list when you create or edit a job, they get their own row on the Schedule, and Mucka can book them in or suggest them for a free slot.
Untick it for someone you don't want booked in, like an office seat that's never on the tools, or somebody you only ever send as a second pair of hands. They drop out of the engineer list, their empty row comes off the Schedule, and Mucka won't book them or offer them as free.
What it doesn't do:
- It doesn't change what they can see. Prices, invoices and clients come from their role, not this box.
- It doesn't take them off jobs they're already on. Work already booked to them stays booked, it stays on the Schedule under their name, and it stays on their own diary. To move a job, open it and change the engineer.
- It doesn't stop you messaging them. See message your team.
Common gotchas
- Spam folders. First-time invitation emails sometimes land in junk. If the new teammate says they haven't seen it, ask them to check spam first.
- Wrong role. Pick the closest fit, you can change it later from the Team tab.
- Engineer can't see jobs. Make sure you've actually assigned them to jobs (either as lead engineer or supporting engineer). Until they're on at least one job, their schedule will look empty.
- Subcontractors are free. A subbie doesn't count towards your seats. See add a subcontractor.