- Revenue and marginCan see
- Customer emails and phoneCan see
- OrdersCan see
- Stock and transfersHidden
- Ledger and card spendHidden
- TasksOnly their own
Audit log
- Lena (Owner)Gave Omar access to Campaigns09:12
- Omar (Marketing)Edited the autumn emailYesterday
- Sam (Warehouse)Moved 40 units to the studio shopYesterday
- SystemNightly backup completed02:00
Enforced in the database on every table, not just hidden in the menu. Sample roles.
Access is decided in the database, row by row. Every client on its own database and deployment, backed up nightly.
What you can do.
3 modules. Switch on the ones you need.
01
Permissions and audit log
Control who sees what, with a record of who changed what and when.
02Coming soon
Single sign-on
Your team signs in with the Google or Microsoft account they already use. Access ends when that account does.
03Coming soon
Advanced security
Field-level encryption, retention rules and scheduled access reviews.
A day with it.
- Day one
Everyone gets the role that fits, enforced in the database.
- Every change
Who changed what, and when, is written down.
- Every night
Every table is backed up and kept for 30 days.
What changes.
- Role-based permissions, enforced by row-level security.
- An audit log of who changed what, and when.
- Nightly backups kept 30 days, with a test restore from Settings.
Your data, your rules, in writing.
Talk to us about building yours, or sign in if you already have one.