Add a Teammate
Mobile Service Sync supports multiple users per account: an Owner, additional Admins, Office Managers, and Technicians. Each role has a different set of permissions — the Owner sees everything, Technicians see only the jobs they're assigned to, and the in-between roles fall between.
You'll find user management under Settings → Team.
The four roles
| Role | What they can see and do |
|---|---|
| Owner | Full access. One per organization. The seat that gets created on signup. |
| Admin | Same as Owner, except they can't change billing, delete the account, or transfer ownership. Useful for a co-owner or operations manager who runs the day-to-day. |
| Office Manager | Full schedule + customers + invoices + work orders. Can't change app settings, integrations, or the team. The classic dispatcher / front-office role. |
| Technician | Sees only their own assigned work orders, time entries, and the day's schedule. Can complete jobs and add notes. Can't see other techs' work, customer profiles outside their assignments, or billing. |
Permissions are enforced consistently across the app — a technician who opens a link to something they don't have access to gets a "Not found" page rather than a permission warning.
Invite a teammate
Open Settings → Team
From the sidebar, click Settings, then Team.
Click "+ Invite teammate"
The form takes:
- Email — required. The address they'll use to sign in.
- Name — required. Shows in the team list and on work orders they're assigned to.
- Role — Owner, Admin, Office Manager, or Technician.
- Pay rate (optional) — sets per-hour or per-job rate for time tracking and payroll exports. Editable later.
Send the invite
The invitee receives an email with a link to finish setting up their account. As long as they sign up using the same email you sent the invite to, they'll land in your organization with the role you assigned.
The team list shows them as invited until they sign up, then flips to active.
Invitations are tied to email. If the invitee signs up with a different address than the one you sent the invite to, they'll end up in a brand-new (separate) organization instead of yours. Tell invitees to use the exact address on the invite.
What an invited user sees on first sign-in
- They click the link in the invite email, set a password, and verify their address.
- They're matched to your invite automatically and their status flips from invited to active.
- They land on the dashboard with the role-appropriate sidebar and a Welcome modal explaining where their work lives. (Owners get the full product tour.)
- Their pay rate, if set, is already populated under their profile.
Invites don't expire — if a teammate takes more than 30 days to sign up, the invite is still valid and waiting for them.
Disable a teammate
When someone leaves, click their row and pick Disable user from the actions menu. Disabled users:
- Can't sign in.
- Stop receiving any notifications.
- Disappear from the bookable-technicians list and the assignee dropdown on new jobs.
- Stay attached to historical work orders, time entries, and invoices for the audit trail.
If they come back later, you can re-enable from the same menu — they pick up exactly where they left off.
Disabling is reversible. Deleting a teammate is not — once deleted, historical work orders show "Unknown user" as the assignee and the change can't be undone. Most operators should disable rather than delete, unless they're cleaning up test accounts.
Custom permissions
The four built-in roles cover most cases. For edge cases (a Technician you trust to write invoices, an Office Manager you don't want seeing payroll), the per-user permissions field on the user detail page lets you tune the role's defaults up or down.
The User detail page surfaces every permission the role grants and lets you toggle individual ones. Per-user overrides survive role changes — if you later swap a Tech to Office Manager, the custom permissions you'd added stay applied on top of the new role's defaults.
Touching this is rare and worth a moment of consideration; for most operators the four-role defaults are right.