> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/reference/matter-roles-and-permissions.md).

# Matter roles and permissions

The matter roles you can assign and what each can do.

When you share a matter, each member is given a role. A matter has one owner and any number of editors.

## Roles

| Role                           | Assigned to                            |
| ------------------------------ | -------------------------------------- |
| Owner                          | The person who created the matter.     |
| Editor (shown as **Can edit**) | A colleague you invite to collaborate. |

## Permissions

| Action                                              | Owner | Editor |
| --------------------------------------------------- | :---: | :----: |
| View documents and the Document Index               |   ✓   |    ✓   |
| Upload, edit, and delete documents                  |   ✓   |    ✓   |
| Run an AI agent the owner has set up                |   ✓   |    ✓   |
| Set up or remove an AI agent in the matter          |   ✓   |    —   |
| Build the Document Index and generate court bundles |   ✓   |    ✓   |
| Invite members and change their access              |   ✓   |    —   |
| Change the matter's name                            |   ✓   |    —   |
| Change Document Index and court bundle settings     |   ✓   |    ✓   |
| Create, rename, clone, and delete collections       |   ✓   |    ✓   |
| Archive the matter                                  |   ✓   |    —   |
| Restore an archived matter                          |   ✓   |    —   |

Credits for these matter actions are charged to the **matter owner's** balance, whoever performs the action — so when an editor exports the Document Index or generates a court bundle, it draws on the owner's credits, not the editor's. Building the Document Index itself is free. For which actions consume credits and what they cost, see [Credit costs and pricing](/reference/credit-costs-and-pricing.md). Setting an agent up is a one-off step the matter owner takes; once it is set up, editors can run it like any other agent.

> To understand why sharing gives access to the whole matter, and why a role behaves the same everywhere, see [Roles and permissions in a shared matter](/concepts/roles-in-a-shared-matter.md).

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Roles and permissions in a shared matter</strong></td><td>How access is shared and what each role can do.</td><td><a href="/concepts/roles-in-a-shared-matter.md">Roles and permissions in a shared matter</a></td></tr><tr><td><strong>Share a matter with a colleague</strong></td><td>Invite a colleague to a matter and assign them a role.</td><td><a href="/how-to-guides/manage/share-matter-with-colleague.md">Share a matter with a colleague</a></td></tr><tr><td><strong>Change or remove a colleague's access</strong></td><td>Change a member's role or remove their access to a matter.</td><td><a href="/how-to-guides/manage/change-remove-colleague-access.md">Change or remove a colleague's access</a></td></tr><tr><td><strong>Transfer a matter to another user</strong></td><td>Transfer matter ownership to another user.</td><td><a href="/how-to-guides/manage/transfer-matter-to-another-user.md">Transfer a matter to another user</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.brieftech.ai/reference/matter-roles-and-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.