Skip to main content

3.1 Remote Admin Permissions Guide

This page lists all of the Remote Admin Permissions, and what Permission Nodes grant each individual permission. To put it more simply, each role in the Remote Admin is assigned a set of “permission nodes” that outline what each role has the power to do. Each node has a set of grouped “permissions” under it, which outline exactly what each node allows for.

“Nodes” are what you put into your Remote Admin configuration files. A list of them can be found below:

Code Name in configuration file Grants remote admin access
(*) Anyone can use (N/A) N/A
BN1 KickingAndShortTermBanning YES
BN2 BanningUpToDay YES
BN3 LongTermBanning YES
FSE ForceclassSelf YES
FSP ForceclassToSpectator YES
FWR ForceclassWithoutRestrictions YES
GIV GivingItems YES
EWA WarheadEvents YES
ERE RespawnEvents YES
ERO RoundEvents YES
SGR SetGroup YES
GMD GameplayData YES
OVR Overwatch NO
FCM FacilityManagement YES
PLM PlayersManagement YES
PRM PermissionsManagement YES
SCC ServerConsoleCommands YES
VHB ViewHiddenBadges NO
CFG ServerConfigs YES
BRC Broadcasting YES
CDA PlayerSensitiveDataAccess YES
NCP Noclip NO
AFK AFKImmunity NO
ATC AdminChat YES
GHB ViewHiddenGlobalBadges NO
ANN Announcer YES
EFF Effects YES
FFI FriendlyFireDetectorImmunity NO
FFT FriendlyFireDetectorTempDisable YES

In the case of “BN2” (BanningUpToADay) for instance, this node allows you to do a specific set of things. Firstly, any role with this permission node added to it will gain access to the Remote Admin panel, as well as any of the things listed in the “BN2” column below. BN2 gets access to things like muting and unmuting, which BN1 does not. BN2 does not get access to the “unban” text-based RA (Remote Admin) command however, which is exclusive to BN3.

If you have any questions or need further assistance, please open a Technical Support Ticket on our Discord.