Ways of entry
| Method | What is | Where is | configured |---|---|---| | Login and Password | Main Login Method | Settings → Accounts | | Two-factor authentication (TOTP) | One-time code from the application on top of the password | Settings → Accounts | | Telegram | Log in with Telegram, no password | Provider— Settings → Authentication, binding— Settings → Accounts | Each account should have at least one login method: the panel will not allow you to remove the last one.Recommended setting
- Set up a separate account for each person who works with the panel – shared accounts make the audit log meaningless.
- Use a unique password that does not apply to other services.
- Enable two-factor authentication for at least full-access accounts.
- Grant only the necessary rights: for support staff, access to the support module is sufficient.
- Disable or delete accounts that no longer need access.
Entrance from 2FA
Once you enter your username and password, the panel will show you a separate field for the six-digit code: Open the authenticator app, find Axottle, and enter the current code.Entrance via Telegram
Telegram is connected by the administrator once for the entire installation, after which a button appears on the entrance screens. Log in via Telegram. What protects this entrance:- the exchange of code for a token is on the server side, the code does not get into the browser;
- Telegram’s response is verified by signature, publisher, recipient, expiration date and one-time value;
- service values of the request are one-time and live for a limited time;
- Application secret is stored in a secure storage and is not returned through the API.
Protected superuser
The account created during the initial installation is protected at the service, API and database level, and cannot be deleted, disabled or denied full access in any way — an attempt returns a failure. The superuser itself can change its password, manage 2FA, and link Telegram; such actions require re-entering the password even in an already open session.This is protection against blocking the installation: without it, incorrect setting of rights could leave the panel without a single administrator.
Sessions
Sign in the browser gives a session in the form of aHttpOnly cookie - the token is not available from JavaScript. For CLI and integrations, the token is still logged in in the Authorization header, see Authentication API.
The exit ends the session; the change of password additionally completes all other sessions of the account.
Access management
User creation, password change, 2FA and Telegram binding are located in Settings → accounts. Detailed instructions: Accounts and login. Distribution of rights: Access rights.Verification
Each administrator has their own account, and for 2FA records, a code is requested after the password, and a non-linked Telegram account cannot be logged in.
