> 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/user-management.md).
# User Management
### Overview
A user is an entity which is allowed to interact with your @Human instance. A user can be an employee who needs to interact with your @Human, or a system user which may be used to identify external integrations or webhook requests.
A user can be assigned to a series of roles[^1] which define the scope of the access for the given user.
{% hint style="danger" %}
For privacy reasons, personal information is masked by default. This can be configured by setting appropriate access control rules for either all users or a specific user.
To change information masking for all users:
1. Click on the permissions button in the top right corner,
2. select the role you wish to change this for,
3. select the appropriate access option for the "show email details for any user" or "show name details for any user".
To change information masking for specific users:
1. Click on the edit icon next to the user you wish to change this for,
2. click on the permissions button in the top right corner,
3. select the role you wish to change this for,
4. select the appropriate access option for the "show email details for (name here)" or "show name details for (name here)".
{% endhint %}
### The User Interface
The user management user interface resides in the Platform Admin Area, under the system :angle-right: users section.
### Listing Users
To list current system users:
1. navigate to system :angle-right: users,
2. optionally insert the filtering parameters.
3. The list refreshes automatically.
### Creating Users
{% hint style="danger" %}
Permissions can only be defined for existing users.
{% endhint %}
To create a new user:
1. navigate to system :angle-right: users,
2. click on the new button in the top right corner,
3. provide the requested data,
4. press the submit button.
### Editing Users
To edit an existing user:
1. navigate to system :angle-right: users,
2. click on the edit icon next to the user you wish to edit,
3. update the parameters you wish to change,
4. press the submit button.
### Suspending Users
To suspend an existing user:
1. Navigate to system :angle-right: users,
2. click on the edit icon next to the user you wish to suspend,
3. press and confirm the suspend button.
### Deleting Users
{% hint style="success" %}
Instead of deleting users, you can temporarily suspend them.
{% endhint %}
To delete an existing user:
1. navigate to system :angle-right: users,
2. click on the edit icon next to the user you wish to suspend,
3. press and confirm the delete button.
### Assigning Roles
{% hint style="warning" %}
In order for the role membership to reflect on the user, they need to re-login.
{% endhint %}
To assign a role to an existing user:
1. navigate to system :angle-right: users,
2. click on the edit icon next to the user you wish to edit,
3. navigate to the "role membership" section and assign appropriate roles,
4. press the submit button.
{% hint style="info" %}
Refer to the [Security Model Introduction](#user-content-fn-1)[^1] for more information regarding roles and access control.
{% endhint %}
[^1]: Add link
---
# 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:
```
GET https://docs.planetcrust.com/platform-administration-console/security-model-rbac/user-management.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.