Roles & permissions
LiveFour seeded roles with per-capability view / add / edit / delete permissions, plus custom roles you define.
- ✓Four seeded roles — Owner, Company Admin, Manager, Member
- ✓Permissions per capability, with view / add / edit / delete verbs
- ✓Custom roles with their own permission matrix
- ✓Per-member feature assignment on top of the role
What it is.
Every organisation starts with four roles — Owner, Company Admin, Manager and Member — each holding permissions expressed per capability rather than per document. A permission is a capability key plus four verbs: view, add, edit and delete. That is what lets you say "this person may read the tax module but not change anything in it".
You can create your own roles and set their permission matrix. Company admins can also grant or withhold individual features per member, which is the finer control most teams actually reach for.
Three steps.
End to end.
On invitation or later. Owner, Company Admin, Manager and Member are seeded; you can add your own.
Per capability, choose view, add, edit and delete. Deciding on an AI review, for example, requires delete on the relevant capability.
A company admin can switch individual features on or off for a specific member, on top of their role.
What you get.
- ✓Four seeded roles — Owner, Company Admin, Manager, Member
- ✓Permissions per capability, with view / add / edit / delete verbs
- ✓Custom roles with their own permission matrix
- ✓Per-member feature assignment on top of the role
- ✓Role and permission changes recorded in the append-only audit log
Quick answers.
Not as a named role. There is an external-counsel marker on a user that filters the member list, but it is not a permission set. For genuinely external recipients, use a share link with view-only permissions rather than an account.
No. Permissions attach to capabilities across the organisation, not to a document set. See Folder permissions for the state of that.
They are on multi-seat plans. Single-seat plans do not need them — one person holds everything.
More in Team & Enterprise.
Not built. The organisation is the isolation boundary; matters are how work is grouped inside it.
Shared editing sessions on a document, and a propose-review-merge flow for changes to it.
Group contracts, research, obligations, meetings and tasks by matter — with a timeline of everything that happened on it.
A searchable, append-only record of state-changing actions across your organisation.