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

# Accounts and login

> Panel users, login methods, password, two-factor authentication and Telegram.

**Settings →** accounts are designed to control access to the Axottle panel.

> [!NOTE]
>
> To work with the section, you need an account with the right **User Management**.

## One user - one record

In Axottle, a person has one account, password, two-factor authentication, and Telegram are theirs. **entryway**A support role is an additional profile of the same record.

Therefore, the support operator added from **Support** appears here: it is the same user, not a copy of it.

## List of users

For each user, you can see:

| What is shown by | value of | |
| - | - | - |
| Display name | Human name; login is only used to log in to the | password |
| Sign-in methods | Password, Telegram, 2FA – what exactly is configured | |
| Access Level | Full access or limited set of rights | |
| Role in support of | Role within the support module if assigned to | |
| Last login to | When a user logs into the | panel |

> [!NOTE]
>
> User rights vary. An account may have full access or a limited set of rights — see [Access Rights](https://docs.axottle.com/en/security/authorization.md).

## Protected superuser

The account created during the initial installation is marked with the **Superuser** badge. It is protected: it cannot be deleted, disabled or shortened to its rights - either through the panel or through the API. Delete and change rights buttons for it are turned off.

The superuser itself can change its password, turn on and off 2FA, bind and detach Telegram, and actions with login methods require re-entering the password.

> [!WARNING]
>
> Security is needed so that the installation can't be left unadministered or intentionally left without an administrator, so if the superuser is no longer needed as a human, hand over the access, not try to delete the record.

## Creating a user

**1. Open the master.**

Go to **Settings → Accounts** and click **Add user**.

**2. Select the type**

* **Administrator** - full access to the panel.
* **Support Operator** - Access only to the support module, the role of "Operator" is assigned immediately.
* **Configure manually** - select the rights yourself.

**3. Fill out the profile and login method**

Specify the displayed name. Next, specify at least one way of entering:

* **login** - normal entrance;
* **Telegram User ID** – login via Telegram
* You can specify both.

**4. Create.**

Click **Create**. The user will appear in the list and will be able to log in in the selected method.

> [!NOTE]
>
> You can not set a password if the Telegram User ID is specified - then the user only logs in via Telegram.

## Modification and deletion

* **Rights** is an edit button in the user's bar.
* **Role in support** - ibid., in the user card.
* **Delete** - Delete button in the line. You can not delete yourself or the superuser.

Disabling the account (Disabled status) closes the login and ends active sessions, but saves the history of actions.

## Change of password

**1. Open the password change form**

In the block. **Password.** press **Change the password**.

**2. Enter the passwords.**

Enter the current password, a new password, and repeat the new password.

**3. Save it.**

Press **Save password**. Use the new password the next time you log in.

After changing the password, the remaining active sessions are completed, the current one is saved.

## Two-factor authentication

Two-factor authentication adds a one-time code from an authenticator application to your password. Google Authenticator, 1Password, Authy and other TOTP-enabled apps will do.

### Inclusion of 2FA

**1. Start setting up**

In **Two-factor authentication** press **Set up 2FA**.

**2. Add Axottle to the app**

Scan the QR code. If scanning is not available, enter the key shown manually.

**3. Confirm the connection**

Enter the current six-digit code from the app and click **Confirm and enable**.

After enabling 2FA, the panel will request a one-time code after entering the login and password.

> [!TIP]
>
> If the code is not accepted, wait for the next code to appear in the application and repeat the input. Also check that the time on the phone is set automatically.

### Disconnecting 2FA

Click **Disable 2FA**, enter the current password and code from the application, then confirm the disconnection.

## Entrance via Telegram

If the administrator has configured the provider, in the **block, you can connect your Telegram via Telegram** and log in without a password. The full instruction is [Login via Telegram](https://docs.axottle.com/en/panel/telegram-login.md).

## If you can't get in

* Check the keyboard layout and the symbol register in the password.
* When 2FA is turned on, wait for the new code and try again.
* When logging in via Telegram, the panel shows the reason for the refusal directly on the login screen - see the table in [Entry via Telegram](https://docs.axottle.com/en/panel/telegram-login.md).
* If the password or access to the authenticator application is lost, contact the specialist who handles the Axottle installation.

## Verification

> [!TIP]
>
> The new user is displayed in the list with expected login methods and rights and can log into the panel.The superuser is tagged with a badge, its deletion buttons and rights changes are inactive.

## Cancellation

* The user can be removed from the list or deactivated, saving the history.
* The password can be replaced again through the **password**.
* 2FA is disabled in the same section using the current password and code from the app.
* Telegram is untied in the block **Entrance via Telegram**, if the user has a password.


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