Collaboration
Access and permission are two different questions, and conflating them is what makes a permission model dangerous. Scope says which books someone can reach. Role says what they can do there. Every change anyone makes is an audit entry in plain language, and a restore is itself an entry.
How it works
- 01
Invite by email
No account needed to accept. The invitation carries the scope and the role you chose, and both are shown again to the person accepting it.
- 02
Two axes, stated together
Scope is global or a named set of dashboards. Role is Viewer, Contributor or Editor. The effective permission is the narrower of the two, and the interface states both together, never a role alone.
- 03
Everything is on the record
Every change anyone makes is already an audit entry in plain language, with who made it and when. Recorded states are restorable, and a restore is itself an entry.
Who can reach what
Each row states scope and role together. A row reading Editor with no scope beside it would be the failure this design exists to prevent.
- Invite collaborators
- Viewer seats
- Contributor and Editor seats
What each plan gets
| Capability | Basic | Premium |
|---|---|---|
| Invite collaborators | Not included | Included |
| Viewer seats | Not included | Free |
| Contributor and Editor seats | Not included | Included |
| Per-dashboard scope | Not included | Included |
| Audit trail with restore | Included | Included |
The rest of the book
AI Powered
Hand it a receipt or an invoice and it fills itself in, ready for you to confirm.
Read more about AI PoweredSmart Insights
Alerts and summaries that reach you where you already are, on a schedule you set once.
Read more about Smart InsightsSmart Widgets
Arrange the page the way you read, by dragging the panels that answer your questions.
Read more about Smart Widgets
Your books, kept privately.
No bank connection, ever. Premium is free for seven days when you want it.