Staff and access

Your moderators should not be sharing your account. Everyone signs in as themselves, and what they can reach is decided by your organisation.

Your organisation

An organisation is your staff, shared across every server you run. You get one automatically — you do not have to create it — and every server you own belongs to it.

The point of it is that you hire someone once. Before, adding a moderator to six servers meant adding them six times; now they join your organisation once and you pick which servers they work on.

Find it under Organisation in the top navigation.

The three roles

Role	Reaches	Can
Owner	Every server in the organisation	Everything, including billing, pricing and payouts
Admin	Every server in the organisation	Everything except money — settings, VIP, and staffing your moderators
Moderator	Only the servers you assign them to	Day-to-day moderation on those servers — read and act, never configure

A ban follows those boundaries exactly: an owner or admin bans across the whole organisation, a moderator bans on the servers they are assigned to. See bans cover your network.

There is also CerebRUST — platform staff, for support and operations.

Your role on each server is shown next to it in My Servers.

Moderators are the exception, deliberately

Owners and admins reach every server in the organisation. A moderator does not: being in your organisation gives them nothing on its own. They only reach a server once you have assigned them to it.

That is so adding a new server to your organisation never quietly hands it to your whole moderation team.

Organisation pages

Organisation in the top navigation has three tabs, each its own page you can bookmark: Members (your staff, below), Plugin defaults and Settings.

Plugin defaults

Organisation → Plugin defaults sets your Plugin behaviour once for every server you run — join and leave messages, periodic messages, the message of the day, your chat prefix, connect-time security and in-game admin access. It is the same set of settings as each server’s own Plugin behaviour page, edited once.

• Every server in the organisation uses them unless it overrides a setting, and a server you add later picks them up automatically — there is nothing to copy.
• A server can still override any one of them. On the server’s Plugin behaviour page an inherited setting is marked From your organisation and locked; press Override to give that server its own value. An overridden one is marked Overrides your organisation’s value, with Use organisation value to follow the organisation again. Like every setting, nothing changes until you press Save.
• Periodic messages add up. Your organisation’s lines go out on every server and can’t be overridden; each server can add its own lines after them, like a “check out our weekly!” on the monthly server.
• Every other setting is replaced whole. A server with its own MOTD or whitelist uses only that — never yours as well.
• Each default says how many of your servers override it, so you know who is ignoring it.
• Start from a server copies one server’s current Plugin behaviour into your defaults. That server then follows the organisation instead of its own overrides, and behaves exactly as it did; other servers’ own overrides are left alone.

Owners and admins can change them — they are the same settings an admin already edits per server. Gameplay mods and the wipe schedule stay per server.

Organisation settings

Under Organisation → Settings — for decisions about the organisation itself rather than about a person in it.

There is one setting today: Share and receive player signals. Turning it on widens the worth-watching network signal on a player’s page to every other CerebRUST organisation that has also turned it on — arithmetic summaries only, never a server name, an organisation name, or anybody’s ban list. See your network signal for what a player sees about themselves.

Owner-only, and off by default. It is a decision about whether your own servers’ telemetry leaves your organisation, so only an owner can flip it — the same tier as your Integrations credentials, where configuring is the owner’s call and using what it unlocks is an admin’s.

It goes both ways, in one switch. There is no version where you only receive without sharing — turning it on means your organisation both contributes to and receives the wider signal, because a one-way opt-in would mean CerebRUST redistributing your telemetry to somebody who gave nothing back.

A setting an admin cannot change is shown to them anyway, disabled, with the reason — never hidden.

In-game admin access

CerebRUST keeps your Rust server’s own admin list in step with your organisation, so you do not have to run ownerid in console and remember to undo it later.

In CerebRUST	In game	What they can do
Owner	ownerid — auth level 2	Everything: spawn any item, god mode, noclip, teleport
Admin	moderatorid — auth level 1	Kick, ban, teleport, the admin UI — but not item spawning
Moderator	nothing	No in-game powers

Admins get moderator access rather than owner access on purpose. Adding someone to help with bans should not also hand them the ability to spawn C4, and Rust happens to offer exactly the two levels your CerebRUST roles map onto.

CerebRUST owns the list while this is on

Anyone with in-game admin who is not in your organisation is removed — including entries you added by hand in console. That is what makes removing someone here actually take their powers away, rather than leaving them with god mode until you remember.

If you would rather manage ownerid and moderatorid yourself, turn off Keep the in-game admin list in step under Plugin behaviour → In-game admin access.

Changes apply within a couple of seconds, and again whenever your server restarts. Bans are never touched — those are mirrored the other way, from your server into CerebRUST.

Adding staff

1. Open Organisation in the top navigation.
2. Under Add someone, enter their SteamID64 and choose a role.
3. For a moderator, then open each server they should work on and go to Moderators in the left-hand menu — tick them, and Save.

They do not need a CerebRUST account first. If they have never signed in, the invitation is waiting for them when they do.

Only an owner can grant admin or owner. An admin can add and assign moderators, but cannot promote anyone — including themselves.

Choosing who works on which server

Each server has a Moderators page listing your organisation’s moderators with a tick box each. Tick the ones who work on that server, then Save. Untick to remove their access.

The page saves the whole list at once, so if two of you are editing it, the last Save wins rather than the two merging into something neither of you chose.

What staff can see

Someone with access to a server can see, for that server:

• The live map — every player’s position, sleepers, tool cupboards
• Chat history, including team chat
• Player list, session history and player profiles
• Raids, signs, bans and the leaderboard

That is a lot of visibility into your players. Grant it to people you would trust with your admin password, and be aware that F7 reports, private team conversations and base locations are all part of the deal.

Settings changes and destructive actions are more tightly held than read access — but the read access alone is the part worth thinking about before you hand it out.

What a moderator cannot do

Everything under Configure is admin or owner. A moderator does not see those pages at all:

Listing & Discord, Plugin behaviour, Gameplay mods	Admin
Chat rules, Scheduled commands, Rust server file, Wipe	Admin
Integrations (your host’s credentials)	Owner only
Billing, pricing, payouts	Owner only

This changed on 29 August 2026

Until then a moderator could open the settings pages and save them — gather rates, your MOTD, your wipe schedule, even your server’s public vanity URL. That was a mistake on our side: it contradicted what the rest of the product does, and nothing in the interface hinted at it.

If you gave somebody moderator access on the understanding that they could not change your settings, that is now true. If you had been relying on a moderator doing your configuration, make them an admin instead.

Removing access

• From one server: untick them on that server’s Moderators page.
• From everything: remove them from the organisation. That takes every server assignment with it, so there is nothing left to tidy up.

An organisation always keeps at least one owner, so the last one cannot be removed or demoted. Add a second owner first if you are handing the network over.

Accountability

Actions taken from the dashboard are recorded. Kicks, bans and broadcasts are issued as commands to your server and logged against the person who issued them, so “who banned this player” always has an answer.

Your own account

Sign in with Steam only — there is no CerebRUST password to leak. If you lose access to the Steam account that owns a server, that is a support conversation, so keep Steam Guard on it.