Server selection, roles, and permissions
How to choose the right SCUM server, understand roles and find out why some function or data is not displayed.
On this page
Most SCUM management pages work with the server currently selected in the top administration bar. This selection determines which players, map, logs, settings, and commands you see. Therefore, before each change, first check the server name in the header.
Why choosing a server is important
One Nodera administration can manage multiple SCUM servers. Each of them has its own online players, telemetry, restart schedule, AutoChat and other settings. Community bans and strikes, on the other hand, are common to the community, but their delivery is checked separately for each server.
- Server pages display the data of the selected server - for example LIVE monitor, map, console or logs.
- Community decisions can apply across servers - typically a ban or strike.
- Global settings are an exception and the page marks them as such.
How to change the active server
- Open any SCUM page in the administration.
- In the common top bar, find the server selection.
- Choose the desired server and wait for the page to refresh.
- Check the server name in the header again before saving or sending the command.
It is safe to change the server in the top bar. It does not change settings or restart the game by itself; it just switches the context you're working in.
Roles in administration and player roles
The administrator role determines which parts of Nodera you can open and what you can do in them. The player role—player, VIP, or admin—is a separate property of the SCUM profile. Granting VIP will therefore not automatically grant the player access to the administration and vice versa.
| Situation | What decides |
|---|---|
| Page visibility in admin | Your admin role, enabled module and server authorization |
| Console access or sensitive action | Elevated authority and current server readiness |
| VIP player benefits | Player role and fulfilled account linking conditions |
| Displayed data | Server selected in common top bar |
Why you might not see a menu item
A missing menu item does not necessarily mean an error. Most often, it is one of the following reasons:
- the module is not available for the given installation or license,
- your role does not have permission for the page,
- you do not have access to the selected server,
- feature requires a fresh connection to NODERAgent or NODERA-RCON,
- the customer server administrator sees a deliberately narrower scope than the internal platform owner.
Example from Main
As of 1 September 2026, Main was active and online, all 12 monitored operational roles were healthy, and the NODERA-RCON connection was responding. This meant that an authorized administrator could work with both LIVE data and commands. This status does not say anything about your personal authorization - that is assessed separately.
What to check in the event of a problem
- Verify the selected server in the top bar.
- Try to refresh the page and check the data up-to-date warning.
- If the page is missing, ask the owner to check your admin role and assigned server.
- If you can see the page but the action is blocked, check the status of NODERAgent and NODERA-RCON on the dashboard.
When reporting a problem, all you have to do is state the name of the page, the selected server, the time and the displayed message. Do not send passwords, access tokens or webhook URL.