> 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/how-to-guides/manage/change-remove-colleague-access.md).

# Change or remove a colleague's access

Change a member's role or remove their access to a matter.

Only the matter **Owner** can manage members.

1. Go to **Matters** in the sidebar and click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-de0790895ab944dba7f0cd16dc6149ae8eb32ac7%2Ficon-share.svg?alt=media" alt="Share" data-size="line"> Share icon on the matter you own.
2. In the **Share Matter** dialog, find the person under **Currently Shared With**.
3. To change their role, use the role dropdown next to their name. To remove them, click the **✕** next to their name.

See [Matter roles and permissions](/reference/matter-roles-and-permissions.md).

{% hint style="info" %}
**Only one role may be available:** In the standard setup the role dropdown offers only one role — **Can edit** — so removing access is the reliable way to manage a colleague's access. A **Can view** (view-only) option appears only when view-only sharing has been switched on for your user, or when someone already on the matter holds that role.
{% endhint %}

{% hint style="warning" %}
**Heads up:** Clicking the **✕** removes access straight away — there is no confirmation prompt, and BriefTech does not notify the colleague.

* If they have the matter open, the page keeps showing what had already loaded but stops updating, and their next action fails.
* The matter disappears from their list after a reload.
* Any corrections they already made stay in the matter.
* You can share the matter with them again to restore access.
  {% endhint %}

## 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>Matter roles and permissions</strong></td><td>The matter roles you can assign and what each can do.</td><td><a href="/reference/matter-roles-and-permissions.md">Matter roles and permissions</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.brieftech.ai/how-to-guides/manage/change-remove-colleague-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.