Brick Admin Configuration

Manage roles, permissions, and staff assignments in Staff Management. Use the configuration files for server-wide settings, then restart brick_admin after saving file changes.

Menu and reports

These settings are in config.lua.

Setting	Default	Purpose
Config.Brand	Brick Admin	Menu title.
Config.Command	admin	Staff command, without the slash.
Config.Key	F10	Default key binding; players can rebind it in FiveM.
Config.ReportCommand	report	Player report command; change it if another resource uses the same command.
Config.ReportCategories	Included category list	Choices offered when creating a report.
Config.ReportCooldown	30	Seconds between new reports per account; 0 disables the cooldown.
Config.Locale	en	Lua message locale. The browser menu is in English.

Staff permissions

Open Staff Management to create reusable roles, edit their management rank, and choose individual tools. You can assign a role to a connected player or give that player an individual permission set.

Include the viewing permission for each workspace a role needs. For example, player tools need View player list, and report tools need View reports. Viewing a workspace does not grant its editing tools.

Use the permission search to find a tool, or expand a group to select its options. Ordinary roles do not automatically receive newly added tools, so review their permissions after an update. Custom roles must have no assigned members before you delete them.

In server_config.lua, Config.FrameworkAdmins controls whether existing framework or command-ACE administrators receive the Admin role. Config.Roles supplies the initial roles; use the menu for role changes after first startup. Owner ACE grants continue to apply even if an in-menu assignment is removed.

Record retention

Set Config.RetentionDays in server_config.lua to choose how long old resolved reports, messages, and history are kept. The default is 30 days; set it to 0 to retain records indefinitely. Open reports and active bans are preserved.