Admins and moderators
The two dashboard access levels, every permission id and what it unlocks, what stays with the owner, and the fourteen abilities an in-game staff member is granted one at a time.
Two different lists, and one word that appears on both. The Admins page is who can open your server in the Raven dashboard, at one of two levels, Admin or Moderator, with the owner above both. The In-Game Moderators page is identifiers you tag so the anticheat treats those players differently in game, and from resource 1.8.9 what they get there is a level plus a list of abilities you tick one at a time. A dashboard Moderator has no in-game status and an in-game moderator has no dashboard access. Neither list grants the other.
The two access levels
Under the owner there are two levels, and the only difference between them is whether the person can manage somebody else's access.
| Level | Can manage | What it is |
|---|---|---|
| Owner | Anyone | The account the license was redeemed on. Full access, and the only one who can make somebody an admin. |
| Admin | Moderators only | Can add, remove and re-permission moderators. Never another admin, and never past their own access. |
| Moderator | Nobody | Holds the permissions they were given and cannot change anybody’s access, including their own. |
The level is not a separate field you can get out of step with the permissions. It is the Admins Edit tick, stored as admins:edit: holding it makes somebody an admin, not holding it makes them a moderator, so the badge on the row and the ticks in the editor can never disagree. Choosing Admin in the picker turns on Admins View as well, because managing a list you cannot read is not a working permission.
Only the owner hands out that tick, and the dashboard is the only place any of this is decided. Nothing in server.cfg and nothing in game sets a dashboard level, and nothing in server.cfg sets an in-game one either. See Ace permissions for what is left of the ace rights.
Adding an admin
Open Admins
Pick your server in the sidebar, then Admins under Management.
Find the person
The search matches a name, a Discord username, a Discord user ID or a whole email address, and you pick the person from the results. Typed text on its own is only accepted as a Discord user ID: a username is a snapshot taken when they signed in, it is not unique, and Discord hands a dropped handle to somebody else, so a username nobody selected is refused rather than guessed at. 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.
Pick the level
Dashboard access level, Moderator or Admin. A new person joins as a Moderator unless you change it, and only the owner is offered Admin at all. Each option says what it allows, under its name.
Choose permissions
The editor lists every area with its own tick, and the header counts how many of the available ticks you have set. Select all, Read only and Clear all are shortcuts.
| Shortcut | What it sets |
|---|---|
| Select all | Every tick the person adding them is allowed to grant. |
| Read only | Dashboard, plus the View tick of every area that has one, with one deliberate hole: Download is a View tick and it carries the license key, so Read only leaves it out. Tick it by hand if you really mean to hand that over. |
| Clear all | Nothing at all, which is no access to the server. |
| Accepting the default | A new person added without choosing anything gets Dashboard, Players List, Bans List and Map Interaction, with every action inside those except Direct Messages and Announcements. |
Take a moment on this screen rather than accepting the default, because players and bans include kicking, banning and unbanning. The World area has no View tick at all, only the three delete ticks, so Read only never grants it anything.
The permissions
Areas that carry more than one action expand into individual ticks, and ticking the area heading turns the whole area on. Each row below is one tick, under the id it is actually stored and checked as. Twenty-six ids in all.
| Id | In the editor | What it unlocks | Enforced where |
|---|---|---|---|
dashboard | Dashboard | 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, so anyone who can open the server can read the audit trail. | Server |
players:view | Players List, View | The Players List, and the live roster the map and Multi Stream both read. | Server |
players:kick | Players List, Kick | Kick a connected player, from the player card or from the map. The card menu greys the entry out without it and the endpoint refuses it as well. | Server |
players:ban | Players List, Ban | Ban a connected player, from the player card or from the map. A reason is required either way. | Server |
players:stream | Players List, Live Stream | Watch a player screen, the Multi Stream page, and the one-shot Screenshot on a player card. Watching also needs View. | Server |
players:message | Players List, Direct Messages | Write to one player, or to up to twenty at once, from the player card, the server home or the World page. | Server |
players:announce | Players List, Announcements | Write to every screen on the server at once, from the Players List header, the server home or the World page. | Server |
map:view | Map Interaction, View | The position heatmap, both reading it and recording new samples. The map page itself is hidden from the sidebar without it, and the players plotted on it are the Players List roster, so a useful map needs Players List View as well. | Server, for the heatmap |
bans:view | 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. | Server |
bans:create | Bans List, Create | Ban Offline, Restore ban from an unban row in the activity log, and keeping a ban from the Players List or the map that the game server did not carry out. | Server |
bans:remove | Bans List, Remove | Unban, Wipe All, and permanently deleting a stored capture. | Server |
admins:view | Admins, View | See the admin list and search for users to add. | Server |
admins:edit | Admins, Edit | The admin level itself. Add, change and remove moderators, within the limits below. Only the owner can grant this tick, and it is never included in a whole-area grant. | Server |
moderators:view | In-Game Moderators, View | See the in-game moderators list, each row’s level and the abilities it holds. | Server |
moderators:edit | In-Game Moderators, Edit | Add, re-permission and remove in-game staff. This grants in-game status, never dashboard access, and on its own it does not cover the whitelist. | Server |
moderators:whitelist | In-Game Moderators, Grant Whitelist | Give or take a whitelist exemption, and the txAdmin auto-whitelist toggle. A whitelisted player is skipped by detections, which is a different power from managing staff, so it is its own tick and is never included in a whole-area grant. | Server |
settings:view | Settings, View | Open Main Settings and Protection Rules and read them. Without it the configuration is left out of the server payload entirely. | Server |
settings:edit | Settings, Edit | Save either page. It is also what is required to switch global bans on or off, edit the global ban whitelist, and apply or revert a Raven Mind fix, since all three change how the server treats players. | Server |
resources:view | Resources, View | The resource list and each resource state. | Server |
resources:start | Resources, Start | The Start button. Restart needs this and Stop, because it is a stop followed by a start. | Server |
resources:stop | Resources, Stop | The Stop button, and the other half of Restart. | Server |
resources:refresh | Resources, Refresh | Run the server refresh command. | Server |
resources:install | Resources, Install | The Install and Uninstall buttons (resource 1.9.3+), which also edit the Resources Installation whitelist. Never included by an older blanket Resources grant. | Server |
entities:peds | World, Peds | Delete every non-player ped in the world, including mission and shop NPCs. | Server |
entities:vehicles | World, Vehicles | Delete every vehicle in the world, players’ vehicles included. | Server |
entities:objects | World, Objects | Delete every spawned object and prop in the world. | Server |
control:view | Download, View | Download the resource files for this server. The download carries the server’s license key, because the resource cannot start without it, so this tick hands that admin the key the dashboard otherwise shows to the owner only. The permission editor says so beside the tick. | Server |
The World page also sends announcements and direct messages, but those two are ticks under Players List rather than under World, because they act on players and not on the world. The in-game rac clear command is checked twice over: the player has to hold the matching World ability on their in-game row, and they also have to resolve to a dashboard account that holds the tick for every entity type they asked for.
Where the panel is looser than the endpoint
Three places offer a button on the area rather than on the exact tick, and let the endpoint do the refusing. None of them leak anything, but it is worth knowing why a click can come back as an error.
| Where | Offered on | Enforced on |
|---|---|---|
| Screenshot on a Players List card, and Kick, Ban and Screenshot on the map player panel | Nothing, they are always shown | players:stream, players:kick, players:ban |
| Unban and Raven Mind in the Bans List detail panel | Nothing, they are always shown | bans:remove |
| Unban, Restore ban and Raven Mind in the activity log details modal | Any Bans List tick; Raven Mind on any Settings tick, and on a ban row both | bans:remove, bans:create, settings:edit |
What stays with the owner
| Owner only | Why |
|---|---|
| The license key | The License Key row on the server home is only there for the owner, because the key is never sent to anyone else. The one way an admin gets it is the Download tick above, since the resource files carry it. |
| IP reset requests | Rebinding a license decides where the product runs, so no admin permission unlocks it and the sidebar entry is hidden for admin-only accounts. |
| The paid setup page | It buys a service for a server, which is an ownership call. |
| Renewing the license | The renewal panel and its endpoint are owner-only; anyone else gets a 404. |
| Deleting the server | There is no permission that grants it. |
| The reason a license was suspended | Shown only to the owner, when one is suspended. |
| Making anybody an in-game Admin | The Admin level on an in-game row is the only level that may manage other staff from in game, so the picker offers it to the owner alone and the endpoint refuses it from anyone else. |
See IP reset requests for the one of those an owner actually has to go and do.
Limits on an admin who manages others
Giving somebody the Admins Edit tick makes them an admin, not a second owner. Every path is clamped to what that person already holds, and every clamp is checked on the server rather than only in the editor.
| They cannot | What happens instead |
|---|---|
| Touch another admin, even one holding exactly the same permissions | Refused: another admin is the owner’s to change |
| Make anybody an admin | The tick is not offered in the editor, and the endpoint refuses it if asked anyway |
| Grant a permission they do not hold themselves | The editor only offers what they hold, and a request past it is refused and names the permissions that were outside their access |
| Edit or remove somebody whose access already exceeds theirs | Refused |
| Change or remove the owner | Refused |
| Change or remove themselves | Refused, including their own permissions |
| Add the owner as an admin, or add the same person twice | Refused: one person is on a server’s admin list 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.
In-Game Moderators
A different list entirely, and the one the sidebar calls In-Game Moderators to keep it apart from the dashboard Moderator level above. Here you tag a FiveM identifier with in-game staff access, a whitelist exemption, or both. It needs resource 1.7.4.5 or newer, and the page is hidden below that.
| Access | What the player gets |
|---|---|
| In-game staff | A level, Admin or Moderator, and a list of abilities you tick. The player shows as an admin in the Players List and on the map, and in game they hold exactly what is ticked and nothing else. It grants no dashboard access at all. |
| 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. |
A level and a list of abilities
Up to resource 1.8.8 the Admin tag was one switch: holding it gave a player everything the resource would let an admin do, and there was nothing inside it to narrow. From 1.8.9 the same row carries a level and a list of abilities, and the list is the whole of it. Anything left unticked is refused in the admin menu and on the rac commands, whatever your server.cfg says.
| In-game level | What the level itself decides | Who sets it |
|---|---|---|
| Admin | Two things, and only two. They may act on a Moderator, where a Moderator may not. And they are the only level that may hold the two managing abilities, Edit and Grant Whitelist, so a Moderator-level row never keeps either even if you tick it. An Admin with nothing else ticked still cannot do anything else. | The owner only |
| Moderator | Holds the abilities ticked on the row. They can act on a player who is not staff and never on another staff member, their own row included. | The owner, or an admin with In-Game Moderators Edit |
The fourteen abilities
Fourteen of the twenty-six permission ids above are also what an in-game row is built from. The id is the same word in both places, which is deliberate, but the grant is not: a dashboard admin's ticks never reach the game, and an in-game row's ticks never open the dashboard.
| Ability | In the editor | What it unlocks | Works in |
|---|---|---|---|
players:view | Players List, View | On the dashboard, the Players List and the live roster. In game it is what opens the menu at all, and what draws the players in it, and rac with nothing after it needs it. Every other ability here is dead without it, which is why ticking any of them ticks this one and holds it ticked. | Both |
players:kick | Players List, Kick | Kick from the player card on the dashboard, where a reason is required. In game, Kick on the player panel and rac kick, where the reason is optional and falls back to a standard line. | Both |
players:ban | Players List, Ban | Ban from the player card on the dashboard, where a reason is required. In game, Ban on the player panel and rac ban, and the reason is required there too: a ban with nothing written is refused and nothing is recorded. | Both |
players:stream | Players List, Live Stream | Watch a player screen and open Multi Stream. On the dashboard it is also what the one-shot Screenshot checks. In game, up to six screens at once. | Both |
players:message | Players List, Direct Messages | The message composer in Direct message mode, one to twenty players you pick, 240 characters in game. | Both |
players:announce | Players List, Announcements | The same composer in Announcement mode, every connected screen at once, 200 characters in game. | Both |
bans:view | Bans List, View | The Bans List, and one ban’s evidence. In game it is what opens a ban to read its evidence, and what keeps the list refreshing after a ban changes; the summary list itself arrives with the menu either way. | Both |
bans:remove | Bans List, Remove | Unban, Wipe All and deleting a stored capture on the dashboard. In game, lifting a ban from the Bans List page and rac unban. | Both |
entities:peds | World, Peds | Delete every non-player ped. In game, Clear peds and rac clear peds, and the cloud checks the asking player against a dashboard account as well. | Both |
entities:vehicles | World, Vehicles | The same for vehicles, players’ vehicles included. | Both |
entities:objects | World, Objects | The same for spawned objects and props. Everything in the menu, and rac clear all, need all three. | Both |
moderators:view | In-Game Moderators, View | Read the In-Game Moderators list on the dashboard. In game, the Staff panel on a player: their level, whether they are whitelisted, and which of these fourteen they hold. | Both |
moderators:edit | In-Game Moderators, Edit | Add, re-permission and remove in-game staff on the dashboard. In game it draws Make moderator, Edit abilities and Remove moderator on the Staff panel. Admin level only. | Both, nothing saved in game yet |
moderators:whitelist | In-Game Moderators, Grant Whitelist | Give or take a whitelist exemption on the dashboard, and it is the tick the txAdmin auto-whitelist toggle needs. In game it draws Give whitelist and Take whitelist on the Staff panel. Admin level only. | Both, nothing saved in game yet |
An in-game staff row has to hold at least one ability. Saving one with nothing ticked is refused, with the message that says to take their staff access off instead if that is what you meant. And because every ability needs View, and because nobody hands out what they do not hold, an admin without the Players List View tick cannot build a working in-game grant at all: the save comes back naming players:view as outside their access.
Who may change an in-game row
| To change | You need |
|---|---|
| Anything on the list at all | A dashboard level of Admin or owner. A dashboard Moderator is refused whatever else they hold, because the list is managed from the Admins tier up. |
| Staff access and the abilities on it | In-Game Moderators Edit. The old Admins Edit tick is still accepted here, which is what kept the admins who held it working when the two were split. |
| A whitelist exemption, or the txAdmin toggle | In-Game Moderators Grant Whitelist, on its own. Admins Edit does not cover it and neither does In-Game Moderators Edit, so an admin who had the whole area before the split needs the owner to tick this one. |
| Set somebody to the Admin level | The owner. The picker does not offer it to anybody else, and the endpoint refuses it with a line saying making somebody an admin is the owner’s to do, from the dashboard only. |
| Somebody who already holds more than you | Nothing will do it. An existing row holding an ability you lack is refused before the write, and so is a row at the Admin level. |
What an in-game admin can change from the game
The Staff panel sits on a player in the menu's Players List, beside Kick and Ban. What it draws depends on the abilities above, and every button is checked again on the game server before anything happens.
| On the Staff panel | It needs | What happens today |
|---|---|---|
| Reading a level, a whitelist and an ability list | moderators:view | Works. The panel lists all fourteen abilities and ticks the ones that player holds. |
| Make moderator, Edit abilities | moderators:edit | Gated, then not saved. Every rule below runs first, and a change that passes them all is still answered with nothing changed. |
| Remove moderator | moderators:edit | Gated, then not saved. |
| Give whitelist, Take whitelist | moderators:whitelist | Gated, then not saved. |
The rules the panel does enforce are worth knowing, because they are the refusals you will actually read.
| Refused when | What it says |
|---|---|
| The actor is not at the Admin level in game | Only admins can change staff from in game |
| The actor picked their own row | You cannot change your own staff row |
| The target is staff at the actor’s level or above | That player is staff at your level or above. Change their row on the dashboard first |
| The level asked for is anything but Moderator | Only moderators can be set up in game. Admins are made on the dashboard |
| An ability was ticked that the actor does not hold | You cannot hand out "players:ban" because you do not have it yourself |
| Nothing was ticked | A moderator needs at least one ability. Tick what they can do |
| The license has expired | Your Raven licence has expired, so staff changes are off until it is renewed |
| The same button is pressed too often | Three of each write in 30 seconds, and six roster reads in 15 seconds |
What happens when you upgrade
Everybody already tagged for in-game staff is moved onto the new model once, and nobody loses their row. Each of them becomes a Moderator holding two abilities, players:view and bans:view: they can open the menu, read the players list and read the bans list. No kick, no ban, no stream, no unban, no clear.
| On the row | Before the update | After it |
|---|---|---|
| Level | There was no level, only the tag | Moderator. Only the owner can put anybody back to Admin. |
| Abilities | Not a field: the tag was all or nothing | players:view and bans:view, and nothing else. |
| Pre-ticked to re-grant | Nothing to keep | players:view, players:kick, players:ban, players:stream, bans:view and bans:remove, the six the old tag was worth. |
| A whitelist-only row | A tag of its own | Untouched. It is not part of this at all and keeps working exactly as it did. |
What each of them could do before is written down beside their row rather than thrown away. The Moderators tab counts them in a banner at the top, puts a NOT GRANTED YET pill on each row and prints Could do before the permissions update with the old set spelled out. Grant previous abilities on the row writes that set back in one click. Opening the row instead gives you the same set pre-ticked in the editor, so you can trim it before saving. Nothing in that list is in effect until you do one or the other.
What the tag is worth on each build
The ability list is read by resource 1.8.9 and newer. The description under the option on the Moderators page says which of these you are getting.
| Resource | In-game staff access gives |
|---|---|
1.8.9 and newer | The admin badge, and exactly the abilities ticked on the row. The menu, each thing inside it, every rac subcommand and the Staff panel are gated one ability at a time. The tag on its own carries nothing but the badge and rac help. |
1.8.8 | The admin badge and the rac ban, kick, unban and clear commands. No menu, and no ability list to narrow them with. |
1.7.5 to 1.7.8 | The admin badge, and on those builds it also exempted that player from some detections. |
anything else | The admin badge and nothing else. |
A change to a connected server lands in that session. The live push carries the level and the ability list per player, so taking an ability off somebody who is online takes effect at once and an open menu redraws within a couple of seconds. A server that is offline, or a player the cloud has not seen verify since it last restarted, picks the change up from their own next connect instead. An ip: or token: value is never taggable, because neither names a person.
Tagging a player who is online
For someone who is connected you do not have to copy an identifier by hand. Moderator Access on their Players List card, or beside their name in the map's player list, opens the same screen for that player: the two accesses, the level picker and the fourteen abilities. It works from the account identifiers the resource sends with the player list, never the IP address or the FiveM token. An older resource sends none of them, and when nothing taggable arrives the dialog says to update the resource, or to tag the identifier on the page itself instead.
A player can be tagged under several identifiers, and saving in the dialog gives all of them the same access, so the rules above are read against the strongest row they already hold. A save is refused outright when somebody else changed that player's access, or the player's own identifiers changed, while the window was open, so nothing is written over blind. A whitelist that reaches them through a shared ip: or token: row is shown as inherited and is not written from here: clear that row on the page itself.
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. Nobody is added to the moderator list and no player is recorded in the cloud because of it. The toggle is a Connection Filters value stored with the rest of your configuration, so a connected server is sent it at once and an offline one reads it on its next connect. Turn it off if your txAdmin logins are shared or handed out more widely than your trust in them.
It is a whitelist, so it needs the In-Game Moderators Grant Whitelist tick, the same as any other whitelist change. It grants no abilities and never makes anybody staff.
Where to go next
- Commands, for the ability each rac subcommand and each menu page checks
- Ace permissions, for why an ace right no longer grants anything in game
- Activity log, for the rows every change on this page writes
- Dashboard overview, for which page each permission puts in the sidebar