Team & permissions
Three roles. Everyone sees what they should.
Owners run everything, dispatchers run the schedule, technicians see their own work. Invite by email and they set their own password — one is never sent to them.
The difference
What changes when this is in one place.
Without it
Which means no record of who did what, and a password change that locks out the whole shop.
Including margins, other customers' balances and the pipeline — none of which is theirs to see.
Someone leaves and the shared password has to be changed, then redistributed.
With ManePilot
Owner, Dispatcher and Technician, each scoped to what that job actually needs.
They choose their own. No credential is ever emailed to anybody.
The last owner cannot be demoted or removed, you cannot change your own role, and every restriction says why next to the control.
What it does
The specifics.
With the seat limit checked at the point of invite, not after they expect a message.
From a dropdown, with the consequences explained in plain English.
With a confirmation step, and protection for the last remaining owner.
One on Solo. Seats are the only difference between the two plans.
Works with
It is one workflow, not seven products.
Each part of ManePilot assumes the others exist. That is the point of it being one platform.
See it running on your own work.
See this working against your own services, your own pricing and your own week.