MODULE 05 · STAFF← CAPABILITY MATRIX
05.
Module · Staff

Staff the shop. Gate the access.

Who's on the team, what they can touch, when they work. A real role-based access model scoped to your shop, not a spreadsheet at the back of the office.

Capability Sheet

Inside the module.

Each capability below is a real, shipping piece of the product — with the reason it matters in a working shop, not just what it does.

05.A
Capability

Staff roster

Add staff with name, email, and role. Invite by email; they set their own password.

Why it matters

Onboarding a new tech takes a minute, not an afternoon.

05.B
Capability

Role-based access

Owner, Admin, Manager, Technician. Each role has a permission matrix per module: view, create, edit, delete.

Why it matters

The technician sees their own jobs. The owner sees everything. No accidental exposure of the books.

05.C
Capability

Shifts per tech

Weekly working hours for each staff member. Defines when they're schedulable.

Why it matters

The part-timer's Tuesday-off doesn't become the Saturday emergency.

05.D
Capability

Hour tracking

Hours worked roll up per staff, per period. Compare to defined shifts.

Why it matters

Overtime and under-staffing become numbers, not feelings.

05.E
Capability

Permissions matrix per module

Toggle view / create / edit / delete — for any role, any module.

Why it matters

The new manager can edit orders but not pricing until they've earned it.

05.F
Capability

2FA per staff

TOTP two-factor authentication for every staff member. Any authenticator app works.

Why it matters

The shop with access to payment data gets the security posture it deserves.

05.G
Capability

Role-based visibility

Owners see the whole shop. Managers see their shift. Techs see their own schedule.

Why it matters

Privacy and simplicity at the same time.

END OF MODULE 05 · STAFFSTART HERE

Ready to run
a shop?