01
Personal access
Every person uses a named login so actions, approvals and changes stay attributable.
Security and control
Trust starts with knowing who did what.
Baymate designs identity, branch boundaries, immutable records and offline integrity into the workshop workflow instead of adding them after growth.
02
Role and branch permissions
Access follows the job people perform and the branch context they are allowed to see.
03
Data-layer separation
Branch and business boundaries are enforced where the data is stored, not only where the screen is drawn.
04
Immutable issued records
Issued invoices, closed cash-ups, approvals and key audit events preserve the record that existed at the decision.
05
Durable offline queue
Offline floor changes remain ordered, attributable and reviewable when the connection returns.
06
AI permission boundaries
AI uses the same role, branch and data permissions as the person asking, with source links and human approval.
Safe by role
The technician sees hours, not rands.
The technician workspace carries everything needed to complete the work while money tables remain outside that role’s access.
Give everyone a login without paying for every seat.
Better access control starts with making individual identity practical.