Roles and access
People see the part of the business they run
Access should be a decision you make, not a side effect of who was set up first. Roles are built from permissions, and each person is scoped to their branch.
What you get
- Roles assembled from individual permissions
- Roles defined per store, not globally
- Branch scoping on top of the role
- Invitations for new team members
- Separate platform administration tier
- Isolated database per store
01
Build the role you need
Rather than three fixed levels, roles are assembled from the permissions that exist. A stock controller who should not see payroll simply does not get that permission.
- Permission-level control
- Roles created per store
- Changed without a support ticket
02
Separated at the database
Access control inside your store sits on top of a harder boundary. Every store is provisioned with its own database, so your records are not filtered out of a shared table, they are somewhere else entirely.
- One database per store
- Platform administration kept separate
- Branch scoping within the store
Works closely with
Try roles and access on your own stock
Create an organization on the free plan, load some of your data, and see how it fits before you pay anything.
- Free plan, forever
- No card required
- Set up in about a minute