> For the complete documentation index, see [llms.txt](https://docs.radar.citadel-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radar.citadel-ai.com/en/administrator-guide/manage-permissions/role-permissions.md).

# Role Permissions

Role Permissions are basic permissions granted to user accounts.

They are specified by users with the Admin role when creating user accounts. Role Permissions determine the operation scope related to Citadel Radar as a whole, such as user invitations, application creation, and Evaluation Library management.

Note that access to and control over specific applications are governed not only by Role Permissions, but also by Resource Permissions configured for each application.

### Types of Role Permissions

Citadel Radar lets you configure the following Role Permissions.

<table><thead><tr><th width="107.86328125">Role</th><th>Overview</th><th>Main operations</th></tr></thead><tbody><tr><td>Admin</td><td>A role for administrators. Grant this role to users who perform management operations for Citadel Radar as a whole.</td><td>Create, edit, and delete user accounts; create, edit, and delete applications; create, edit, and delete common resources such as evaluation libraries</td></tr><tr><td>Editor</td><td>A role for operators. Grant this role to users who operate applications and evaluation libraries.</td><td>Create applications; create, edit, and delete common resources such as evaluation libraries</td></tr><tr><td>Standard</td><td>A role for general users. Grant this role mainly to users who review or operate assigned applications.</td><td>The available operation scope is determined according to the granted Resource Permissions.</td></tr></tbody></table>

### How to use Role Permissions

Select Role Permissions according to the scope you want the user to be responsible for.

* Admin: When managing Citadel Radar as a whole, including user management
* Editor: When handling operation of applications, Evaluation Libraries, and similar resources
* Standard: When limiting access to specific applications

When allowing viewing or operations for a specific application, configure Resource Permissions for the target application.
