> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/getting-started/roles-and-permissions.md).

# See what each role can do

See which permissions each role has, and which role you have on the production you're working on.

The Roles & Permissions page lists every role and the permissions it has, with your own role marked. Everyone can open it from **Help > Roles & Permissions** in the sidebar.

## Open the page

1. Open the sidebar. On a phone, select the menu button (three lines) in the header.
2. Select **Help**, then **Roles & Permissions**.

You can also open it from:

* **Settings**: on the **Profile** tab, select **View guide** in the **Roles & permissions** card. See [Manage your account settings](/getting-started/settings.md).
* **Project > Team**, for Owners, Super Admins, Managers and Department Heads: select the **Roles & Permissions** card at the top.
* The **Welcome to RollCredits!** window that opens once when you finish [setting up your account](/getting-started/set-up-your-account.md): select **View My Permissions**.

## Read the page on a phone

The page shows one card for each role, from Owner to Payroll Agent. Each card has a short description of the role and lists all its permissions. Your role's card is outlined and has a **Your role** tag next to its name.

## Read the page on a computer or tablet

At the top, a card for each role shows its description and how many permissions it has. Your role's card is outlined.

Below the cards, a table lists every permission, grouped under **Company**, **Production**, **Transactions & Cards**, **Payments & Vendors**, **Approvals & Compliance**, **Team & Departments**, **Expenses** and **Payroll**. Each role has a column. A check means the role has that permission, and a dash means it doesn't. Your role's column is outlined, and its checks are in your role's color.

## How to read your role

* **The Owner has every permission.** Each company has one Owner, the person its RollCredits account was set up for. The Owner has every permission on every production.
* **Your role is for the current production.** You can have a different role on each production. The page marks your role on the production you have open. To see your role on another one, switch to it first. See [Switch projects and companies](/getting-started/switch-projects.md).
* **Some access depends on who you work with.** A Department Head manages only the people in their own department, and a Payroll Agent works only with the employees they represent.

{% hint style="info" %}
Having a permission doesn't mean you see every page for it. Some pages and tabs show only when your company or production uses that feature, such as cards, payroll or departments.
{% endhint %}

## Change someone's role

You can't change roles on this page. To change a teammate's role, see [Manage your team](/project/team.md). If your own role looks wrong, ask whoever manages your production's team.


---

# 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://knowledge.rollcredits.io/getting-started/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.