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

# Managing User Roles

## Managing Roles

The Aisera Platform offers several built-in roles, but you can also create and manage custom permissions to suit your specific needs.

{% hint style="warning" %}
When you create roles and permissions, it is a best practice to document the reasons with examples of each role and permission you created. Although you can see the permissions in the UI, it may be difficult for you to determine where a specific restriction is coming from.
{% endhint %}

### Creating a Custom Role

1. Open **Settings > User Accounts** from the left navigation menu
2. Select the **Roles** tab at the top of the **User Accounts** window

   <div align="left"><figure><img src="/files/ugmWVl9upcwM4stl4IZL" alt=""><figcaption></figcaption></figure></div>
3. Choose **+ Create Role**<br>

   <div align="left"><figure><img src="/files/SvIUKjLzib9JnWle0iAI" alt=""><figcaption></figcaption></figure></div>
4. Enter a **Name** and **Description** for the role.&#x20;
5. &#x20;Select an appropriate level of privilege

   <div align="left"><figure><img src="/files/X90x64ZXekE3aV1VzMmi" alt=""><figcaption></figcaption></figure></div>

### Editing a Custom Role

{% hint style="info" %}
System and default roles are not editable. You can only modify custom roles.
{% endhint %}

1. Open **Settings > User Accounts** from the left navigation menu
2. Select the **Roles** tab at the top of the **User Accounts** window
3. Select the role you want to modify
4. Click on the **pencil icon** in the top right to see the **Edit Role** window<br>

   <div align="left"><figure><img src="/files/WzXc3SSt5cwTBttCqFuC" alt=""><figcaption></figcaption></figure></div>
5. Change the **Name**, **Description** or **Privileges** for the role
6. Click **Ok** to save changes

### Deleting a Custom Role

{% hint style="info" %}
System and default roles cannot be deleted. Only custom roles can be removed.
{% endhint %}

1. Open **Settings > User Accounts** from the left navigation menu
2. Select the **Roles** tab at the top of the **User Accounts** window
3. Select the role you want to delete
4. Click on the **trash icon** in the top right to see the **Delete Role** window<br>

   <div align="left"><figure><img src="/files/DReJ2CJvHcfVj31Im6YC" alt=""><figcaption></figcaption></figure></div>
5. Click **Ok** to confirm deletion of the role

**Assign Application Access for PII by Role**

You can give member of a custom role access to Personal Identifiable Information (PII), by choosing the **piis** checkbox for your new role.

<div align="left"><figure><img src="https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FANMpscRlZ8WA4lJv7VTZ%252Funknown.png%3Falt%3Dmedia%26token%3Deb9d3960-1461-4715-8afd-9c32a76f3e33&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=1c1f3a88&#x26;sv=2" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions/managing-user-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
