Management & Security
Administrator action audit
Traceable administrator events, targets, commands and confirmed outcomes help explain interventions and detect suspicious behaviour.
Administrator action audit records who requested a sensitive operation, on which server, against which target and with what confirmed outcome. It helps resolve mistakes, complaints and suspected abuse without relying on one person memory.
An audit is more than a list of clicks
Its value comes from connecting intent, target, command request and agent result. Nodera therefore distinguishes a requested action from confirmed execution.
Context that remains traceable
Exact detail depends on the module and user permissions.
- administrator, time, server and action type
- player, object or configuration affected by the change
- command-queue state and safely normalised outcome
- related moderation, event or configuration events
Quality control and protection for the team
Audit can reveal a mistake and also prove that the correct procedure was followed.
- review a kick, ban, teleport or grant
- compare requested and actually applied configuration
- investigate a player complaint
- flag unusual administrator activity
No secrets or raw output in the interface
Module services write structured audit points and the command queue attaches execution outcome. Raw RCON response, webhook URLs, tokens and server secrets are never displayed in the user overview.
Audit is separated by server and permission. An audit write cannot block a safety-critical operational outcome, while its failure remains diagnostically visible to the appropriate owner.
Actions that can be defended later
Owners gain better team oversight, administrators work more responsibly and disputes can be resolved from evidence.
Need more information?
We will show you how this feature can work on your server. Contact us or join us on Discord.
