> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/settings/user-management/index-1/add-role.md).

# Add Role

## Getting Here <a href="#getting-here" id="getting-here"></a>

![](/files/D3IK8mRjHYdSk1sN5QDb)

**Settings > Roles > Add Role** button.

Fusion has built-in system roles identified by the gear icon. However, the **Add Role Form** allows administrators to create and configure new roles with specific permissions and capabilities. This includes enabling key functionalities and fine-grained access controls for various Fustion settings.

## Add Role Form <a href="#add-role-form" id="add-role-form"></a>

### Form Fields <a href="#form-fields" id="form-fields"></a>

1. **Name\***
   * **Description**: Unique name for the role.
   * **Validation**:
     * Characters allowed: `0-9`, `a-z`, `A-Z`, `_`, `-`, `.`
     * Maximum length: **32 characters**.
     * Cannot be edited once created.
   * **Required**: Yes
2. **Description**
   * **Description**: A longer, user-friendly explanation of the role’s purpose.
   * **Required**: No
3. **Masquerading**
   * **Description**: Allows role users to impersonate other users.
   * **Options**:
     * **DISABLED**
     * **ENABLED**
4. **Send NetoFlow**
   * **Description**: Grants the role permission to send NetoFlow data.
   * **Options**:
     * **DISABLED**
     * **ENABLED**
5. **View Audit Logs**
   * **Description**: Provides access to view system audit logs.
   * **Options**:
     * **DISABLED**
     * **ENABLED**

***

### Permissions <a href="#permissions" id="permissions"></a>

Permissions are divided into categories, with options to set access levels as **Read**, **Create**, **Update**, and **Delete** for specific functionalities.

#### ACCOUNT <a href="#account" id="account"></a>

* **Customers**: Manage customer accounts.
* **Overview**: View account details.

#### USER MANAGEMENT <a href="#user-management" id="user-management"></a>

* **API Keys**: Manage API keys.
* **Roles**: Create, update, or delete roles.
* **Users**: Manage user accounts.

#### DATA MANAGEMENT <a href="#data-management" id="data-management"></a>

* **Cloud Providers**: Manage cloud provider integrations.
* **Context Labels**: Manage and label contextual data.
* **Devices**: Manage device data.
* **Flow Tags**: View and manage traffic flow tags.
* **Traffic Classifications**: Manage traffic classifications.

#### DETECT & RESPOND <a href="#detect--respond" id="detect--respond"></a>

* **Allow Lists**: Manage allowed IPs and entities.
* **Block List**: Manage blocked entities.
* **Detection Categories**: Configure detection categories.
* **Detection Models**: Manage detection models.
* **Integrations**: Manage integrations for detecting and responding.
* **Response Policies**: Manage automated response policies.

#### PORTAL <a href="#portal" id="portal"></a>

* **Dashboards**: Manage and access dashboards for monitoring and reporting.

***

### Permissions Matrix <a href="#permissions-matrix" id="permissions-matrix"></a>

Each category/module allows the following access levels:

* **Read**: View data.
* **Create**: Add new entries.
* **Update**: Modify existing entries.
* **Delete**: Remove entries.

***

### Actions <a href="#actions" id="actions"></a>

1. **SAVE**
   * Saves the configured role and its permissions.
2. **CANCEL**
   * Discards changes and closes the form without saving.

***

### Notes <a href="#notes" id="notes"></a>

* Fields marked with an asterisk (\*) are **required**.
* Use caution when enabling **Masquerading**, as it allows impersonation.
* Carefully assign permissions to balance functionality and security for different user roles.
* Roles with **Read**, **Create**, **Update**, and **Delete** permissions provide full access to that specific functionality.


---

# 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.fusion.vectra.ai/settings/user-management/index-1/add-role.md?ask=<question>
```

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.