> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/groups/user-management/roles-and-permissions.md).

# Roles and permissions

The table on this page outlines the roles and permissions available within an Overleaf group.

<table data-header-hidden><thead><tr><th width="180"></th><th></th></tr></thead><tbody><tr><td><strong>Role</strong></td><td><strong>Permissions</strong></td></tr><tr><td><strong>Admin</strong></td><td><ul><li>Overall responsibility for the group, including billing.</li><li>Can add and remove members and managers.</li><li>Can view group metrics and audit logs.</li><li>Can set up Group SSO (Pro plans only)</li><li>Can set up Managed Users (Pro plans only)</li><li>Does <strong>not</strong> automatically receive a premium subscription.</li><li>Must add themselves as a group member to access premium features.</li></ul></td></tr><tr><td><strong>Group manager</strong></td><td><ul><li>Can add and remove members and managers.</li><li>Can view group metrics.</li><li>Does <strong>not</strong> automatically receive a premium subscription.</li><li>Must add themselves as a group member to access premium features.</li></ul></td></tr><tr><td><strong>Group member</strong></td><td><ul><li>Automatically receives access to premium features (either Standard or Pro, depending on the group type).</li></ul></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://docs.overleaf.com/groups/user-management/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.
