Product
Roles and access
Your team works freely. The figures stay with you.
Everyone in the practice can use the everyday workflows. Sensitive functions sit behind named permissions, given through a role or to one person.
Book a demoEnforced on the server
A restricted function is refused by the server, not merely hidden in the interface.
Simple by design.
There is no matrix to maintain. Grant what someone needs and leave the rest.
1
Start with an Owner
Each practice has an Owner, who holds every permission, including any added later.
- The role cannot be edited or renamed
- A practice always keeps one active Owner
2
Give people a role
Roles collect the permissions a part of the team needs.
- Each member holds one role
- New members start with no extra permissions
3
Grant an exception
Give one person a permission without changing their role.
- Grants only add
- No confusing denials to untangle
What it protects today.
- Accounts figures
- Overview, Analytics, Reports, and the summary export are visible only to people with the permission.
- Everyday accounts work
- Staff keep invoices, insurance, reconciliation, and activity, so the front desk keeps moving.
- Team permissions
- Managing roles and grants is itself a permission, so it stays with the people you choose.