> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Access rights

> Access levels, directory of rights by panel sections and rules for their issuance.

Access to the Axottle panel is configured for each account separately. **full access**either **limited rights** A list of specific sections and actions.

> [!NOTE]
>
> Required rights: **User Management** (`accounts.manage`).

## Two levels of access

| Level | What is |
| - | - |
| **Full access** | All partitions and actions of the panel, including user management. New features of future versions are also available immediately |
| **Limited** | Selected Rights Only. Everything else is hidden in the interface and rejected on the server side of |

Accounts created before the advent of the rights system have full access – when you update the dashboard, nothing changes until the rights are manually limited.

## How to issue rights

**1. Open the section.**

**Settings → Accounts**.

**2. When creating - choose a type**

The user add wizard offers three options:

| Type | What is |
| - | - |
| **Administrator** | Full access |
| **Support Operator** | Support Module Access only, Operator role assigned immediately to |
| **Manually configure** | Selection of rights in sections |

**3. For the finished entry, change the rights**

Click the change button in the user bar. Switch **Full access** is disabled, and opens the selection by partition.

**4. Mark the right rights.**

The rights are grouped into panel sections, and the counter next to the section shows how many rights have been selected, and at one click, marks or removes the entire section.

The changes come into force with the **of the following user request** - you do not need to re-enter the panel.

## Handbook of Rights

| Section | Right | Key key | What gives? | |
| - | - | - | - | - |
| **Nodes** | View | `nodes.view` | List and node cards, metrics, services, transaction log | |
| | Addition | `nodes.create` | Add node | |
| | Modify | `nodes.edit` | Modify node, node group and country parameters | |
| | Delete | `nodes.delete` | Delete | Node |
| | Operations | `nodes.operate` | Installation, preflight, agent tasks, recipes, agent update, | |
| **Configures** | View | `connection_units.view` | Schemes, graph, versions, verification (lint) | |
| | Creation of | `connection_units.create` | Create a | circuit |
| | Schemes Editing | `connection_units.edit` | Change graph and drafts, collect plan | |
| | Remove | `connection_units.delete` | Remove | schema |
| | Application of | `connection_units.apply` | Preflight configuration and application of | node configuration |
| **Remnawave and subscriptions** | View | `remnawave.view` | Connections, users, hosts, subscription contexts, preview | |
| | Control | `remnawave.manage` | Change connections, synchronization, settings | |
| **GeoAssets** | View | `geo_assets.view` | Profile Library and Node Status | |
| | Control | `geo_assets.manage` | Download files, profiles, assignment and synchronization | |
| **Health** | View | `health.view` | Dashboard, tables, samples, diagnostics | |
| | Management and Verification | `health.manage` | Policies, manual checks, actions, external providers | |
| **Anti-abuse** | View | `abuse.view` | Incidents, signals, active deceleration, policy | |
| | Control | `abuse.manage` | Incidents, QoS slowdowns, policy, delivery to Telegram | |
| **Security** | View | `security.view` | Detector Status, subscription leaks, Egress Guard | |
| | Control | `security.manage` | Security profiles, egress policy, reconsilation | |
| **CDN** | View | `cdn.view` | Accounts, resources, operations | |
| | Management | `cdn.manage` | Accounts, DNS connections, domain pools, policies | |
| **SelfSteal** | View | `selfsteal.view` | Templates and deployments, state on nodes | |
| | Control and Deployment | `selfsteal.manage` | Enable, configure, install and verify | |
| **Backups** | View | `backups.view` | Profiles, launches, download archive | |
| | Control and launch | `backups.manage` | Profiles, backup launch, | validation |
| | Recovery from backup | `backups.restore` | Data recovery from | archive |
| **Axosun** | View | `eagent.view` | Reports, sessions, incidents | |
| | | `eagent.operate` | Diagnostic Launch and cancellation of runs, confirmation of actions of | |
| | Profile and Policy Setup | `eagent.manage` | AI Provider Profiles and | Action Policy |
| **Audit Journal** | View | `audit.view` | Audit Journal | |
| **Support** | Access to | `support.access` | Access to | Support Module |
| **Panel settings** | View | `settings.view` | Integrations, Telegram notifications, updates, cloud providers | |
| | Management | `settings.manage` | Change these settings and internal integration tokens | |
| **Accounts** | User Management | `accounts.manage` | User Creation, rights, roles, deletion, login setting via Telegram | |

> [!NOTE]
>
> Right **Access to the support module** It only opens the input to the module, and what the operator can do inside defines the specific support role. [Support operators](https://docs.axottle.com/en/support/operators.md).

## Rules of issuance

**"View" is the basis of the section.** Any action requires visibility, so when you select an action, the right to "View" is automatically marked. If you remove "View", the entire section is removed.

**Dangerous actions were taken separately.** Three rights are intentionally not included in the normal “Management” because they affect the operating configuration and data:

* **Application of configuration** (`connection_units.apply`) - one person can edit the scheme, and roll it out on the nodes of another;
* **Recovery from the backup** (`backups.restore`) - rewrites the current state of the installation;
* **Operations with nodes** (`nodes.operate`) – everything that runs on the server itself.

### What is available without separate rights

Any user logged in to the panel can:

* change the **with** password, enable and disable 2FA, bind and detach your Telegram;
* See a health summary and incidents in 24 hours - these are the counters on the menu and on the main one;
* Open reference directories (performance profiles, list of CDN providers).

## Limitations and protection

> [!WARNING]
>
> You can't limit the **rights of the last** full-access user -- give full access to someone else first.

* **Your rights cannot be changed by**, either in the interface or through the API, which protects against accidental loss of access and from self-extension of authority.
* **The superuser is protected.** An account created during installation cannot be deleted, disabled or restricted. [Accounts and login](https://docs.axottle.com/en/panel/access-and-sessions.md).
* **Verification is performed on the server.** Hidden menu items – convenience, not protection: a direct request to an inaccessible section will return `403`.

## What the restriction looks like for the user

* Only accessible sections remain in the side menu; **Support** only appears when `support.access` is right.
* In the tabs **Settings** only allowed tabs are visible.
* The top bar next to the name indicates "full access" or "limited access."
* When you directly access the closed section, the panel informs that the rights are not enough, and names the right required.

## Audit.

All account changes are entered in the audit log: `auth.account.created`, `auth.account.updated` (including changes to rights - with a list of rights "before" and "after") and `auth.account.deleted`.

The log can be viewed by a user with the right `audit.view`. Read more: [Journal of operations and audit](https://docs.axottle.com/en/panel/journal-and-audit.md).

## Verification

> [!TIP]
>
> Each user has a minimum set of rights, at least two people have full access, and there are no accounts on the list that no longer need access.

## Cancellation

* Full access can be returned by the same switch in the rights dialogue.
* An incorrectly created user can be deleted or disabled in **Settings →** Accounts.
* Restriction of rights does not end the session: the user continues to work, but within new boundaries.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.