AltisControl Docs ↗
Documentation › Getting started
Go to panel

First steps and navigation

Sign-in, sections, global search, filters, language, theme, and everyday panel use.

Sign in

The owner signs in with the email and password created during installation plus a six-digit TOTP code. New administrators receive a TOTP secret when created; save it before closing the dialog. The owner has all permissions. Other accounts depend on roles and direct grants.

Routes and sections

Every section keeps its own /admin/{section} URL. You can reload it, share an internal link, and use Back/Forward. The sidebar groups Dashboard, World, Operations, and Access. Sections without read permission are hidden, and the server validates every request again.

GroupSections
DashboardDashboard, Players, Police, Medics, Donors.
WorldVehicles, Properties, Gangs, Wanted.
OperationsServer, Online, Bans, Server allowlist, Logs.
AccessAdministrators, Roles, Settings.

Dashboard

The overview summarizes RCON and server state, maximum slots, registered players, active bans, vehicles, and administrators. It shows recent activity and police, medic, and economy figures when the role can read them. Global message and process-control buttons appear only with the required permissions and provider.

Use global search in the top bar or Ctrl + K to find players, administrators, gangs, vehicles, and sanctions according to your permissions. List search fields span their tables, with sort and filter icons inside. Options vary by section. For example, Players supports name or Steam ID, sorts by money, playtime, and age, and filters by faction, donor status, or active ban.

Theme, language, and dates

The language control next to the theme button switches the panel between Spanish and English. The global default appearance can be Dark, Light, or System. A new user without a local preference receives that default. The timezone selected in Settings controls displayed dates; database timestamps use UTC.

Actions and confirmation

Forms show fields relevant to each action. Button colors and icons distinguish their purpose. Actions are audited. A reason or confirmation word is not required for every edit; inspect the record and values before saving. Delete dialogs describe their scope.

Good practice: create narrow roles before inviting other administrators, and test them with a non-owner account.