> ## 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.

# The model of rights

> Axosun modes of conduct, mandatory confirmations, access to Remnawave and users, permission cards and approval leases.

> [!WARNING]
>
> Axosun is currently unavailable, and its return to service is not planned in the near future.

Axosun's rights are described by a single installation policy. The policy is edited in the panel (section **Axosun** → tab **Policy**); for any unfilled field, the conservative default value applies.

> [!NOTE]
>
> Administrator: Required rights: Access to the Axosun section of the panel with the right to change the policy.

## Regimes of conduct

| Mode | Effect |
| - | - |
| `report_only` | No action, only reports. Destructive model sentences are discarded in code. |
| `suggest_actions` | Actions are shown, but never performed without confirmation. |
| `ask_before_actions` (default) | Every action requires operator confirmation. |
| `auto_safe_actions` | Automatically executes only the canonical set of read-only actions; everything else is confirmed. |
| `custom` | Clear list of permitted; anything not listed is prohibited. |

Rules of priority:

* the list of prohibited actions is stronger than the list of permitted actions;
* The confirmation requirement is stronger than both lists.
* Unknown names of actions are silently discarded while maintaining policy.

## Actions that always require confirmation

Changing the firewall (`change_firewall`), restarting the server (`restart_server`), mass restarting servers (`bulk_restart_server`), and running a command on the server (`run_shell_command`) always require confirmation. These cannot be translated into automatic execution: each time you download and save the policy, the panel returns them to a set of confirmed actions.

> [!WARNING]
>
> Two actions are completely prohibited and are not enabled even in `custom` mode: changing the settings of `sysctl` (`change_sysctl`) and installing packets (`install_packages`).

## Configuration experiments

Actions on the Flow configuration are further limited to a separate setup:

| Value | Effect |
| - | - |
| `disabled` | No configuration action. |
| `draft_only` (default) | Creating and testing drafts - yes; production - no. |
| `staging_only` | Drafts and staging. |
| `production_with_confirmation` | Allowed and production actions (application of draft, application of generated configuration, change of production routing) - each with confirmation. |

## Access to Remnawave

Assistant access to Remnawave is controlled by a master switch and a cascade of sub-switches:

| Setting up | by Default |
| - | - |
| `enabled` - Master switch. | **Off.** |
| `allow_read_only` - reading | on (not valid until the wizard is turned off) |
| `allow_sensitive_read` - Sensitive reading of | OFF |
| `allow_write_actions` notes | Off. |
| `allow_destructive_actions` Destructive Operations | Exposes |
| `users_access_enabled` Access to users | **Off.** |
| `subscription_access_enabled` Access to subscriptions | Off. |
| `analytics_access_enabled` — Analytics | Includes |
| `events_access_enabled` - Events of | Including |
| `redact_secrets` - cleaning up the secrets of | Including |
| `redact_user_personal_data` – Hiding Personal Data of | Includes |
| `audit_enabled` - | call audit included |
| `max_users_returned` - maximum users in the | 100 sample (range 1-1000) |
| `timeout_seconds` – | 20 (range 1–60) |
| `max_recursive_depth` – depth of circumvention of the graph | 4 (range 1–8) |

The shutdown cascade is applied when validating a policy:

* Turning off the master switch forcibly turns off sensitive reading, writing, destructive operations, access to users and subscriptions;
* Turning off reading turns off sensitive reading and access to users/subscriptions
* Turning off records turns off destructive operations.

**Access to users** is a separate switch, turned off by default. Even when it is turned on, the assistant receives only meters and limited, impersonal samples - see [Data and privacy](https://docs.axottle.com/en/axosun/privacy.md).

> [!NOTE]
>
> Permits are rechecked at execution. Each Remnawave tool reads the current settings before calling, and destructive records recheck the permission to write even when the permission card is already issued: outdated resolution can not bypass the setting that is turned off.

## Confirmation cards

The action requiring confirmation is shown to the operator as a card.

* **Celi** – which nodes/resources are affected and the scope of the operation;
* **risk** - the level of risk of action;
* **validation plan** – which read-only validation will be performed after the action.
* **kickback tip** - how to undo the effect of the action.

Where the card appears:

* in the classical mode - in the report, actions are confirmed or rejected after receiving it;
* in agent mode - right in the chat: the launch is paused until the operator decides.

Card behaviour:

* **Confirmation** performs an action on the audited path, then automatically starts the read-only check of the result.
* **Deviation** is returned to the assistant, and he correctly terminates the work without this action.
* **Timeout** – If the operator does not respond for 15 minutes, the action is marked as missed, and the assistant receives a timeout notification and continues without it.
* Confirmation of an action prohibited by the policy, the panel rejects with denial of access.

## Approval Leases – Approval of Mass Operations

In order not to confirm each node with a separate card, for families of mass operations (agent update, WARP restart, massive firewall change, massive server restart, node withdrawal from rotation), you can issue **approval lease** - one approval for a limited amount and time:

* The lease is valid only within a single launch.
* no more than 200 targets;
* expires in 10 minutes;
* While the lease is valid, the same type of calls for the covered objectives are performed on the usual confirmed path - validation and audit are performed for each action.

> [!WARNING]
>
> Leases does not survive the panel restart: after the restart, the assistant will return to piece-by-piece confirmations.

## How to change behaviors

**1. Open the policy**

Panel → **Axosun** → tab **Policy**.

**2. Select a mode.**

Set the desired behavior mode (for example, `report_only` for a fully passive assistant).

**3. Save it.**

The dashboard validates and normalizes the policy: unknown actions are discarded, mandatory confirmations and the audit channel are restored automatically.

## Verification

**1. Convert politics**

Panel → **Axosun** → tab **Policy**: check the mode, state of the Remnawave master switch and sub-switches.

**2. Check the behavior**

Ask the assistant to perform a confirmation action (for example, restart the service on the test node) – a confirmation card should appear, not an immediate execution.

**3. Check the audit.**

The policy change should appear in the [Operations Journal of](https://docs.axottle.com/en/panel/journal-and-audit.md).

> [!TIP]
>
> Action is not performed without a confirmation card, and the change of policy is recorded in the audit.

## Rollback

To return the safe default values:

1. Mode of behavior - `ask_before_actions`.
2. Configuration experiments with `draft_only`.
3. Remnawave Master Switch → OFF (cascadingly turns off sensitive reading, writing, destructive operations and access to users/subscriptions).
4. Clear user lists of permitted/prohibited actions if you set them in `custom` mode.

The `audit_log` notification channel cannot be removed – the panel automatically returns it to the policy.

## Limitations and risks

* `auto_safe_actions` automatically performs only the canonical read-only set – everything else will still ask for confirmation.
* In the `custom` mode, the principle of “anything that is not expressly permitted is prohibited”.
* An expired card is not executed retroactively - the action will have to be requested again.

## Typical errors

> [accordion] Confirmation returns denial of access
>
> The action is prohibited by the current policy (for example, turned off entries in Remnawave). Check the tab **Policy** - rights are rechecked at the time of execution, not at the time of issuance of the card.

> [accordion] The card is gone, the action marked as missed.
>
> Waiting timeout has expired (15 minutes), request the action from the assistant again.

> [accordion] Mass operation asks for confirmation on each node
>
> Approval lease expired (10 minutes), has been exhausted or the panel has been restarted.

## Related pages

* [Data and privacy](https://docs.axottle.com/en/axosun/privacy.md)
* [Fuses ](https://docs.axottle.com/en/axosun/safety.md)
* [Journal of Operations and Audit](https://docs.axottle.com/en/panel/journal-and-audit.md)


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