Every Branch, Its Own Data. Every Login, Tracked.
Role-based permissions, per-branch data isolation and audit trails, so every team member sees exactly what they should, and nothing they shouldn't.
One Login, Access to Everything.
Without per-branch controls, a single login can see every branch's bookings, rates and financials, so there's no way to give a branch manager visibility into their own operation without handing them the whole business.
Permissions and Branches, Built Into Every Record.
Roles control what a user can see and do, while branch-level data isolation controls whose bookings, rates and financials they can see at all, with every login and change recorded in an audit trail.
What You Get.
Role-Based Permissions
Control exactly what each role can view, edit or approve across the platform.
Per-Branch Data Isolation
Each branch's bookings, rates and financials stay separate unless explicitly shared.
Audit Trails
Every login and record change is logged, so you can see who did what, and when.
Two-Factor Login
Add a second layer of verification to sensitive accounts and roles.
From Role Assigned to Action Logged.
- Role Assigned
- Branch Scoped
- Access Granted
- Action Taken
- Change Logged
Security & Branches FAQs
Can a branch manager see other branches' data?
Only if you grant it. By default, branch-level data isolation keeps each branch's records separate.
How granular are role permissions?
Permissions can be set down to individual actions, like who can approve an expense or edit a supplier rate.
Is there an audit trail of changes?
Yes. Logins and record changes are logged, so you can trace who did what across the platform.
Can we enforce two-factor login for certain roles?
Yes. Two-factor login can be required for sensitive roles like finance or admin.