# Access Management

The Access Management system provides a more structured, secure, and flexible approach to access. This ensures that the right individuals have appropriate control based on their responsibilities.

***

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FNuOzzRPatSGWhfbj2Ph7%2FRBAC.mp4?alt=media&token=2fdb3fe0-91d7-4f24-b1bf-9c8c89dbb4c2>" %}

### **Access Management Role Hierarchy**

To establish clear permissions and responsibilities, we have introduced **five distinct roles**:

1. **Admin** *(Full access to the entire platform, responsible for managing permissions and settings)*
2. **Executive** *(CXOs level i.e. CTO, CEO and Founders)*
3. **Leader** *(VPs, Director and Department heads)*
4. **Managers** *(Team Leads, Engineering Managers and Project Managers)*
5. **User** *(Individual contributors like developers)*

<figure><img src="/files/EmxD6YkNzGrqdmHF5u7V" alt="" width="563"><figcaption></figcaption></figure>

Each role is assigned specific permissions, ensuring a well-defined access structure and preventing unauthorized modifications.

***

### **AM Screen: Structure & Functionality**

The **RBAC screen** is divided into three dedicated tabs:

#### **1. Role Access (only Admins can access)**

This tab provides **Admins** with full control over roles and permissions. Key functionalities include:

* **Viewing assigned permissions** for each role.
* **Modifying role permissions** as needed.
* **Saving changes** for real-time updates.

<figure><img src="/files/16LPmAG6rGyjF8A1f7Ve" alt="" width="563"><figcaption></figcaption></figure>

This centralized approach ensures permissions are **accurately assigned** while maintaining security and flexibility.

***

#### **2. User Management**

This section allows for efficient user administration by displaying a **list of users** in the system.

**Note:** If multiple users are merged in the **Teams** screen, only the **Primary User** will be displayed in this tab.

**Key functionalities:**

* **Inviting new users:**
  * If a person is not yet a user, they can be invited via the **"Invite"** button in the last column.
  * Clicking this button allows Admins to:
    * **Select the user role**
    * **Assign them to teams, projects, and workspaces** (if enabled)

<figure><img src="/files/VEpLdyjLB81aJ7wavy2w" alt="" width="563"><figcaption></figcaption></figure>

* **Editing existing users:**
  * Modify a user’s **role, team, projects, and workspaces** (if enabled).
  * Users **cannot** modify their own details or the role of anyone **above them** in the hierarchy.
  * Users **can only edit roles at their level or below**, ensuring secure delegation.<br>

<figure><img src="/files/JVcprQrIOUuXX9oAQWN1" alt="" width="563"><figcaption><p><em>Adjust roles</em></p></figcaption></figure>

<figure><img src="/files/QW1sZ6bjaPNrRJbQLeU9" alt="" width="563"><figcaption><p><em>Select teams which can be accessed</em></p></figcaption></figure>

<figure><img src="/files/6ftp5RKCH1xmX8XNOz2n" alt="" width="563"><figcaption><p><em>Select projects which can be accesed</em></p></figcaption></figure>

***

#### **3. Pending Access Requests (Admin-Only)**

For organizations that require **Admin approval** for new user sign-ups, this tab acts as a **centralized approval hub**.

**How it works:**

* When a new user requests access, the **Admin receives an email notification**.
* All **pending access requests** appear in this section.
* The Admin can then **approve or deny** requests, ensuring controlled onboarding.<br>

  <figure><img src="/files/AXmVm66qXG32cdidxFVD" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: 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.hivel.ai/set-up/access-management.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.