Agora

Categories

Back to the site

Edit server.cfg and permissions from Agora

The .cfg editor hides secrets, checks before saving and backs up the old version; the permissions configurator manages ACE groups without touching the rest of the file.

Updated on Oct 5, 2026, 9:25 a.m.

On this page
  1. Edit a file
  2. Secrets stay hidden
  3. Backup and restore
  4. Apply the change
  5. Permissions (ACE)

In short. Server → .cfg editor opens server.cfg and every file it includes with exec, right from Agora. It is for administrators only (with staff 2FA) and Pro licenses. A hosting panel must be linked (Pterodactyl or Pelican): the editor reads and writes files through the panel API.

Edit a file #

  1. Open Server → .cfg editor. Each included file has its own tab; an exec to a missing file is tagged "absent": saving it creates it.
  2. Edit the text.
  3. Click Check and save…: you see the added and removed lines, and the file checks.
  4. Click Confirm and save.

Checked: unclosed quote, ensure of a resource that is not in resources/, duplicate ensure, start order (oxmysql and ox_lib before the framework, the agora resource after the framework), an endpoint port the panel did not allocate, different TCP and UDP ports, missing sv_licenseKey. Only serious errors (file over 512 KB, null byte, damaged secret marker) block saving; the rest only warns.

Only .cfg files inside the server folder can be edited here.

Secrets stay hidden #

The license key, API keys, MySQL string, RCON password, webhooks and tokens show as {{secret:NAME}}. Leave the marker as it is to keep the value, or replace it with the new value. The Show button reveals a secret; the action is recorded in the administration log.

Backup and restore #

Before every save, the old version is copied to .agora-backup/ (the last 20 per file). The Backups list offers Restore; the current file is itself backed up first. If the file changed on the server while you were editing (panel, txAdmin, another tab), Agora detects it: Reload (discard my changes) restarts from the server's version, Overwrite anyway keeps yours. Saving and restoring are capped at 20 per minute per administrator; beyond that, a message asks you to wait a minute.

Apply the change #

  • server.cfg and convars: restart the server (under txAdmin, restart from txAdmin, which reads the same file).
  • Another .cfg file: Hot reload (exec ...) runs it without a restart, on the server's next heartbeat (about 30 seconds, agora resource online). Careful: a removed permission is not revoked by exec, and a file containing ensure lines restarts those resources.

Permissions (ACE) #

Switch to Permissions (ACE) mode. Agora reads the permissions file (permissions.cfg if included) and offers four views:

ViewWhat it is for
GroupsEach group's rights (add_ace) and inheritance (add_principal); create, rename, delete a role
PeopleWho is in which group; pick a linked member or type an identifier by hand (license:, discord:, steam:...)
TemplatesThe detected framework's official lines (Qbox, QBCore, ESX or plain FiveM): only missing lines are added
UnmanagedLines the configurator cannot edit, kept as they are

Only the lines you change are rewritten: comments and order stay. A person you add gets a # Agora: nickname comment above their line. An addition takes effect with exec permissions.cfg in the console; a removal needs a restart.

txAdmin does not use ACE for its own administrators: they are managed in its Admin Manager. No Agora template touches it.

Was this article helpful?

Related articles