> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/rekor-command-r/admin-and-settings/users-roles-and-permissions.md).

# Users, Roles and Permissions

The Rekor Command™ software platform utilizes a structured approach to roles and permissions to manage user access effectively.

Permissions define what actions users can perform on specific entities, and these permissions are grouped into roles. Users gain permissions by being assigned roles directly.&#x20;

**Users**&#x20;

* Represent individual system access credentials.&#x20;
* Associated with a single account but can exist in multiple accounts under different roles.&#x20;
* Roles assigned determine the user’s permissions. &#x20;

**Roles**&#x20;

* Defined sets of permissions assigned to users or groups. &#x20;
* Roles are account-specific and include Manager, Viewer, No access permissions.&#x20;

**Permissions**&#x20;

* Manager has Create, Read, Update, and Delete permissions to perform on the assigned entities.&#x20;
* Viewer has read-only permission on the assigned entities.&#x20;
* No access users have no permission on the assigned entities.<br>

### Assigning and Managing Roles

**Assigning Roles to Users**&#x20;

1. Navigate to Settings > Account > Users section.
2. Select an existing user or add a new user. Enter that user's information, assign a role and click Create.<br>

   <img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FEwVE9WtruskJ13MJX2hi%2FNew%20User?alt=media&amp;token=5a777fcd-5c13-4348-8e9f-1d5ebbe994f4" alt="New User" height="616" width="415">
3. Assign one or more roles to the user.<br>

   <img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FuAKo4N6T03ZuIbXgf42K%2FCommand%20TMC%20Manager%20Role?alt=media&amp;token=15cf236c-6016-49ec-907f-bf1416e6c404" alt="Command TMC Manager Role" height="749" width="624">

**Updating Roles**&#x20;

* Modifications to a role (adding/removing permissions) will automatically update permissions for all assigned users and groups.&#x20;

**Removing Roles**&#x20;

* Removing a role from a user or group revokes the associated permissions. Permissions are only fully removed if all roles containing them are removed.&#x20;

**Create Custom Roles**&#x20;

* Add a new role with role name and description.
* Select custom role permissions on each entity.

Tip: It is advisable to create a role title that already exists within your organization (i.e., TMC Operator, TMC Supervisor, etc.) &#x20;

#### Default Roles and Permissions Settings

| Role Name   | Permissions                                                             | Description                               |
| ----------- | ----------------------------------------------------------------------- | ----------------------------------------- |
| Admin       | CRUD on all entities, user and group management, account-level settings | Full administrative access to the account |
| Viewer      | Read-only access to all entities                                        | View data without making changes          |
| Custom Role | Customizable permissions (e.g., specific entities access)               | Flexible role for tailored permissions    |


---

# 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.rekor.ai/rekor-command-r/admin-and-settings/users-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.
