> For the complete documentation index, see [llms.txt](https://bundus.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bundus.gitbook.io/help/team/change-role-permissions.md).

# Add or remove permissions from a custom role

Edit a custom role when its team members need more or less access. Changes apply to everyone assigned to that role.

### Change the permissions

1. Open **Settings**.
2. Under **Workspace**, select **Team**.
3. Select the **Roles** tab.
4. Open the actions menu for the custom role, then select **Edit**.
5. Under **Permissions**:
   * select a permission to add it;
   * clear a selected permission to remove it.
6. Read the explanation beneath each permission before changing it.
7. Check the access summary near the top of the page. It lists the areas the role can access.

![A custom role editor showing grouped permissions and selected access](https://1239150628-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0xEFjtRHcsV7HPwU6C74%2Fuploads%2Fgit-blob-4e62061219eb39abe5d2a17c9b354c9ec78ec9ae%2F01-role-details-and-permissions.jpg?alt=media)

8. Select **Save changes**.

Bundus returns to the roles list. The role's permission count reflects the saved selection.

> **Example:** Adding **View quotes** and removing **View inventory** changes the access summary from Bookings, Clients, Inventory to Bookings, Clients, Quotes.

### Important access checks

* **View** permissions normally allow read access only.
* **Manage**, **Issue**, **Record**, **Correct**, and **Void** permissions allow actions that change business or financial records.
* **All read** selects the read permissions in one area.
* **All write** grants the available change permissions in that area. Review the result before saving.
* Use **Full admin** only when the role should have broad administrative access.

Give each role only the access needed for its work. After a sensitive change, ask a member assigned to the role to sign in again and confirm that the correct pages and actions are available.

### Related guides

* [Create a custom team role](/help/team/create-a-custom-role.md)
* [Invite a team member](/help/team/invite-a-team-member.md)


---

# 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://bundus.gitbook.io/help/team/change-role-permissions.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.