> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and permissions

> Control what users and teams can see and do in Cortex with default and custom roles.

Roles control what each person can see and do in Cortex, from viewing catalogs to editing Scorecards, configuring integrations, and creating API keys. Every user has at least one role, and you can also assign roles to teams. If a user doesn't have permission to do something, Cortex hides that option from them.

Cortex comes with four [default roles](#default-roles). When you need something more specific, such as a role that can manage Scorecards but not settings, you can [create a custom role](https://docs.cortex.io/configure/settings/managing-users/permissioning/custom-roles.md).

## How roles work

* **Every user has at least one role.** New users get your workspace's [default role](https://docs.cortex.io/configure/settings/managing-users/permissioning/assigning-roles.md#setting-the-default-role-for-new-users) when they first log in.
* **Roles can come from a user or a team.** When you assign a role to a team, every member of that team gets that role's permissions, including people who join the team later.
* **Permissions combine across roles.** When someone has more than one role, they get every permission from all of their roles. For example, a user with the Manager role who belongs to a team with the Admin role has Admin permissions everywhere in Cortex.
* **Roles also apply to API keys.** You can assign a default or custom role to an [API key](https://docs.cortex.io/configure/settings/api-keys) to limit what it can do. [Personal access tokens](https://docs.cortex.io/configure/settings/api-keys/personal-tokens.md) always have the same permissions as the user who created them.

## Default roles

Every workspace includes the four roles below. Each role includes everything in the role before it, plus more. You can't edit the default roles, but you can [create a custom role](https://docs.cortex.io/configure/settings/managing-users/permissioning/custom-roles.md) with any combination of permissions.

| Role | Name in Cortex | What it's for |
| - | - | - |
| **Viewer** | Viewer (read only) | Read-only access. Viewers can browse catalogs, Scorecards, Initiatives, and CQL reports, but can't create or edit anything. |
| **User** | User (edit catalog entities) | Everything a Viewer can do, plus creating and editing entities, entity types, and CQL reports, running Workflows and the Scaffolder, and using the Query builder. |
| **Manager** | Manager (edit Scorecards) | Everything a User can do, plus creating and editing Scorecards, catalogs, and Workflows, and using Eng Intelligence and OpEx Review. Managers can't change workspace settings or permissions. |
| **Admin** | Admin (full access) | Full access to everything in the workspace, including settings, integrations, API keys, plugins, and roles. |

For the full list of permissions and which default role includes each one, see the [Permissions reference](https://docs.cortex.io/configure/settings/managing-users/permissioning/permissions-reference.md).

## Custom roles

Custom roles let you grant exactly the permissions a group of people needs. For example, you might create a role for Scorecard owners that adds **Edit Scorecards** without giving full Manager access, or a temporary role that you remove once someone finishes a task. Learn more in [Custom roles](https://docs.cortex.io/configure/settings/managing-users/permissioning/custom-roles.md).

## Where to manage roles

Users with the **View Roles** permission can view the Permissions page. To make changes, users need the **Configure Roles** permission. Both are included in the Admin role by default.

**To access the Permissions page**:

1. From the main sidebar, click your avatar in the bottom-left corner.
2. Select **Settings**.
3. From the **Settings** menu, locate the **Security and access** section, then click **Permissions**.

   ![The Permissions page in Cortex.](https://mintcdn.com/cortex-290c0c42/7v_vtI6fNuuxUc7R/images/settings-permissions.png?fit=max\&auto=format\&n=7v_vtI6fNuuxUc7R\&q=85\&s=25d4f35302b92ac41f4044451672a9e7)

The page has two tabs:

* **Permissions** - View users and teams, assign and remove roles, and set the default role for new users.
* **Roles** - View, create, edit, and delete custom roles.

## Other ways to control access

Roles are the main way to control access in Cortex, but a few features add their own controls on top of them:

* **Workflows** - Limit who can run a Workflow to specific users, teams, or roles, or require the user to be an owner or editor of the entity. See [Configuring Workflow settings](https://docs.cortex.io/streamline/workflows/configuring-workflow-settings.md).
* **Team ownership entity editing** - Limit entity editing to the teams that own each entity. See [Team ownership entity editing](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams/team-entity-editing.md).


## Related topics

- [Assigning roles to users and teams](https://docs.cortex.io/configure/settings/managing-users/permissioning/assigning-roles.md)
- [Managing users and roles](https://docs.cortex.io/configure/settings/managing-users.md)
- [Audit logs](https://docs.cortex.io/configure/settings/audit-logs.md)
