Roles and permissions in a shared matter
How access is shared and what each role can do.
A matter is rarely worked alone. BriefTech lets you share a matter with colleagues and decide what each of them can do, through a small set of roles. Understanding the model helps you share confidently — giving people the access they need without handing over control of the whole matter.
Sharing gives access to the whole matter
When you share a matter, you are not sharing a single document or folder — you are giving a colleague access to the matter and everything in it: its documents, their metadata, the facts, the Document Index, and the exports.
That is usually what you want when colleagues collaborate on a case, but it's worth being clear-eyed about: access is to the matter as a whole.
Sharing access by email
You share a matter by inviting a colleague by their email address and assigning them a role. The role you choose determines what they can do once they have access. Inviting someone, and later changing or removing their access, is something the matter owner controls.
What each role can do
A matter has one owner — the person who created it — and any number of editors. The editor role is shown in the sharing controls as Can edit.
An editor can do the day-to-day work of a matter:
view documents and the Document Index;
upload, edit, and delete documents;
run AI agents;
build the index and generate court bundles.
What an editor cannot do is manage the matter itself — inviting or removing members, changing the matter's name, and archiving or restoring the matter are reserved for the owner. An editor can still change the settings that shape the work itself, such as the Document Index presets and the court bundle configuration.
The effect is a clean division: editors get full working access to the contents of a matter, while control over who can reach the matter, and whether it stays active, stays with the owner.
Why your access is enforced consistently
A role means the same thing wherever you are working. The same permissions apply whether you are clicking through the app or an action runs on your behalf in the background, because access is checked at every point rather than only in the interface. You can rely on a role to behave the same way everywhere, so sharing a matter never quietly grants more than you intended.
For the full action-by-role breakdown, see Matter roles and permissions.
Related
Last updated
Was this helpful?