Raven AnticheatRavenAnticheat
Raven AnticheatDocs

Admins and moderators

Every dashboard permission and what it unlocks, what stays with the owner, and how in-game moderator tags work.

Two different lists, often confused. Admins are people who can open your server in the Raven dashboard. Moderators are in-game identifiers you tag so the anticheat treats those players differently. Neither one grants the other.

Adding an admin

Open Admins

Pick your server in the sidebar, then Admins under Management.

Find the person

Search by Discord username or Discord user ID. To copy a user ID, turn on Developer Mode in Discord, right-click the user and choose Copy User ID. They must have signed in to the Raven dashboard with Discord at least once, otherwise there is no account to attach.

Choose permissions

The editor lists every area with its own tick. Select all, Read only and Clear all are shortcuts. Read only gives the view of each area plus dashboard access and nothing that changes anything.

A new admin added without choosing anything gets the default set: dashboard, players, bans and map, with every action inside those. Take a moment on this screen rather than accepting the default, because players and bans include kicking, banning and unbanning.

The permissions

Areas that carry more than one action expand into individual ticks. Ticking the area heading turns the whole area on.

Dashboard

No sub-actions. It is the key to the door: without it the server does not open at all. It also covers the server home counters, the online player count, the server status, and the activity log. Anyone who can open the server can read the audit trail, which is deliberate.

Players List

  • View. The Players List and the live roster feed the map and Multi Stream also read.
  • Actions. Kick, ban and take a screenshot of a connected player.
  • Live Stream. Watch a player screen, and the Multi Stream page. Watching also needs View.

Map Interaction

  • View. The map page and the position heatmap. The players plotted on it are the Players List roster, so a useful map needs Players List View as well.

Bans List

  • View. The Bans List and the three ban counters on the server home. Without it those numbers are never sent to the browser at all.
  • Create. Ban Offline, and Restore ban from an unban row in the activity log.
  • Remove. Unban, Wipe All, and deleting stored captures.

Admins

  • View. See the admin list and search for users.
  • Edit. Add, change and remove admins, within the limits below.

Moderators

  • View. See the moderator list.
  • Edit. Add, change and remove moderators, and the txAdmin auto-whitelist toggle.

Settings

  • View. Open Main Settings and Protection Rules and read them.
  • Edit. Save either page. This is also what is required to switch global bans on or off, edit the global ban whitelist, and apply a Raven Mind fix, since all three change how the server treats players.

Resources

  • View. The resource list and each resource state.
  • Start and Stop. The matching buttons. Restart needs both, because it is a stop followed by a start.
  • Refresh. Run the server refresh command.

Entities

  • Peds, Vehicles, Objects. One tick each, and each one is a bulk delete of that entity type across the whole world.

Download

  • View. Download the resource files for this server.

What stays with the owner

The owner is the account the license was redeemed on. A few things are theirs regardless of what an admin is granted:

  • The license key. The key is only ever sent to the owner, so the License Key row on the server home simply is not there for anyone else.
  • IP reset requests. Rebinding a license decides where the product runs, so no admin permission unlocks it. The sidebar entry is hidden for admin-only accounts. See IP reset requests.
  • Deleting the server.
  • The reason a license was suspended, when one is suspended.

Limits on a delegated admin manager

Giving an admin the Admins Edit tick does not make them a second owner. Every path is clamped to what that person already holds:

  • They cannot grant a permission they do not have themselves. The editor only offers what they hold, and a request that reaches past it is refused.
  • They cannot edit or remove an admin whose access already exceeds theirs.
  • They cannot change or remove the owner, and they cannot change or remove themselves.
  • Adding the owner as an admin is refused, and a person can only be an admin of a server once.

Every add, change and removal writes a row to the activity log. An add and a change carry the resulting permission set, so a permission change can be reconstructed later; a removal names the person only.

Moderators

A different list entirely. Here you tag a FiveM identifier, for example a license:, discord: or steam: value, with one or both of two kinds of access. It needs resource 1.7.4.5 or newer, and the tab is hidden below that.

  • Admin. A synced status badge. The player shows as an admin in the Players List and on the map. It grants no dashboard access and no in-game powers of its own.
  • Whitelist. The player is skipped by a fixed set of detections, the ones a staff member legitimately trips while doing their job, for example godmode, noclip, teleport and infinite ammo. The card lists the exact detections your resource version honours, because the list grew between versions.

Changes sync to a connected server live. Adding an identifier that is already on the list updates its access rather than erroring, so flipping someone from whitelist to admin is one action.

txAdmin auto-whitelist

One toggle on the same page, on by default. While it is on, anyone signed in as a txAdmin admin is treated as whitelisted for that session. It is a resource-side session bypass and it does not add anyone to the moderator list. Turn it off if your txAdmin logins are shared or handed out more widely than your trust in them.

Managing moderators needs the Moderators Edit tick. An older admin who held Admins Edit before moderators had their own permission keeps access, so nothing broke when the two were split.