> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/account-settings/team-management.md).

# Team Management

The Team Management page allows you to view, add, or update team members and their roles. You can invite new users and assign specific roles.

**Steps**

1. Go to **Account > Team**.
2. View the list of existing members with details like email, role, and last activity.
3. To add a new member, click **Invite people** and enter the email address.
4. Select a role (Admin, Editor, Viewer) from the dropdown.
5. Submit the invitation to add the member.

### Permissions

**Description**

Permissions management ensures that users have the correct level of access to different parts of the platform. Permissions can be set at the time of adding new users or updated later.

**Steps**

1. Navigate to **Account > Team**.
2. Click on the ellipsis (three dots) next to a member’s name and select **Edit Permissions**.
3. Adjust permissions for various features such as:
   * **Catalog & Asset Management**
   * **Supply Chain & Distribution**
   * **Financial Reporting & Revenue Analytics**
   * **Daily Trends Analytics**
   * **Royalty Accounting**
4. Click **Submit** to save changes.


---

# 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://docs.revelator.com/pro/getting-started/account-settings/team-management.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.