> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/platform-administration-console/security-model-rbac/role-management.md).

# Role Management

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

### Overview

A role is a security group which may or may not have access to specific user interfaces or system resources based on your security model.

A role can have a series of users who are provided with the security model defined by the given role.

### The User Interface <a href="#the_user_interface" id="the_user_interface"></a>

The role management user interface resides in the Platform Admin Area, under system <i class="fa-angle-right">:angle-right:</i> roles.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FC68qxnA5y9cuY8Yoe5ra%2Fimage.png?alt=media&amp;token=becbf1fe-2a7e-431c-824f-396efab16932" alt=""><figcaption></figcaption></figure>

### Listing Roles <a href="#listing_roles" id="listing_roles"></a>

To list current system roles:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. optionally insert the filtering parameters.
3. The list refreshes automatically.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FdEViiPo0pSJDb4OseooN%2Fimage.png?alt=media&amp;token=4f9a462f-b25e-4a58-ab4c-ae43ecab0309" alt=""><figcaption></figcaption></figure>

### Creating Roles

{% hint style="danger" %}
You can only define permissions for existing roles.
{% endhint %}

To create a new role:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. click on the new button,
3. insert the parameters for the new role,
4. press the submit button.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2F4ELv8cNDmCUH8H70v6QU%2Fimage.png?alt=media&amp;token=3a19ee1c-6ddd-4745-93a1-1415f8a72293" alt=""><figcaption></figcaption></figure>

### Editing Roles <a href="#editing_roles" id="editing_roles"></a>

To edit an existing role:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. click on the edit button next to the role you wish to edit,
3. update the parameters for the updated role,
4. press the submit button.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FTC9w8asLrS4tw17K0n16%2Fimage.png?alt=media&amp;token=0c05e09e-f20c-4ee0-a862-31ceec356cec" alt=""><figcaption></figcaption></figure>

### Archiving Roles <a href="#archiving-roles" id="archiving-roles"></a>

To archive an existing role:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. click on the edit button next to the role you wish to archive,
3. click and confirm the archive button.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FIwPaNlNNt9zkJd7uXQ8q%2Fimage.png?alt=media&amp;token=dac965c0-35f5-4989-8f77-f7876ac33830" alt=""><figcaption></figcaption></figure>

### Deleting Roles

{% hint style="success" %}
Instead of deleting roles, you can archive the role
{% endhint %}

To delete an existing role:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. click on the edit button next to the role you wish to delete,
3. click and confirm the delete button.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2F2EzIZsZFi2bUv4cofedR%2Fimage.png?alt=media&amp;token=e573739f-7041-4e90-96f3-9d2548340be4" alt=""><figcaption></figcaption></figure>

### Cloning Role Permissions <a href="#cloning_role_permissions" id="cloning_role_permissions"></a>

To clone the role’s permissions to another role:

1. Navigate to system <i class="fa-angle-right">:angle-right:</i> roles,
2. click on the clone permissions button,
3. select the roles you wish to clone the permissions to,
4. press the clone button.

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FGtCcX7ANm1eRxVhevxYE%2Fimage.png?alt=media&amp;token=925a3b65-20b9-4f61-86f7-0b98bab75dad" alt=""><figcaption></figcaption></figure>

<figure><img src="https://94212224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlymuI7sECbl3qDBorEu%2Fuploads%2FD3yVT9xC80HNmljsNuqV%2Fimage.png?alt=media&amp;token=4919423f-442f-4f21-8d99-259b9fc5ca8a" alt=""><figcaption></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.planetcrust.com/platform-administration-console/security-model-rbac/role-management.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 `build a script that syncs our docs to a CMS` 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.
