RBAC(Role-Based Access Control)
TL;DR
A security model where what each user can see or do is determined by their role (e.g. Tech, Front Desk, Owner) rather than per-user toggles.
RBAC (Role-Based Access Control) is the standard pattern for managing permissions in a multi-user system. Instead of granting permissions to individual users, you define roles and grant permissions to the role. Then you assign users to roles.
In a repair shop, common roles include Owner (everything), Manager (almost everything except billing), Technician (tickets + inventory read), and Front Desk (intake + checkout, no margin visibility). A good RBAC model lets each role see exactly what it needs and nothing more.
Get Repair takes RBAC further with module-level scoping (17+ modules including POS, Tickets, Inventory, Reports, Settings, Billing) and PIN-gated sensitive actions like price overrides or refunds.
Quick answers
What's a PIN-gated action?
An action that, even if your role permits it, requires you to re-enter a 4-digit PIN before it executes. Common for refunds, discounts above a threshold, and price overrides. Adds a friction layer for high-trust operations.
Can I create custom roles?
Yes. Get Repair ships with five built-in roles and lets you create unlimited custom roles per org with any combination of module permissions.