Role-based access: what it means
DefinitionRole-based access is a security setup in which each user is assigned a role, such as owner, office manager or technician, and the role decides what they can see and change. A technician might view only today's jobs, while billing stays with the owner.
How it works in a service business
Small businesses often hand everyone full access because it is easy, until a mistake or a departing employee shows why that is risky. Roles limit damage: a new hire cannot delete customers or see revenue reports. The tradeoff is setup time and the occasional need to adjust a role when someone temporarily covers another task. A common mistake is giving the office manager owner-level access because it is faster, which erases the benefit. Start with a few roles that match how work is really divided, and give the least access that lets each person do the job. Pair roles with an audit log, so you can see who changed what, and review the list whenever someone leaves.
Example
A crew lead sees only the day's route and customer notes. She cannot view invoices or edit prices, which stay with the owner and the office manager.
Where Apex touches this
Rolling out
The screen and the rules are built and tested. Saving real customer data is not connected yet. Status as of 2026-10-07; the badge shows the least-built feature involved.
- AD01Roles and permissions(Built)
- AD02Granular permissions per feature(Rolling out)
- SC14Role-limited calendar views(Built)
Apex Flow Scheduler is in early access. See how we label status.