Team & Permissions

Give other people access to the dashboard: named members, Discord role mappings, and how often roles are re-checked.

Two ways to grant access

Admin

The Discord server owner always has full access. Everyone else gets it from the Team page, in one of two ways: added as a named member, or by holding a Discord role you have mapped to a Madsi role. Both resolve to the same permission set; a member who qualifies through several routes gets the union. A named member who leaves or is banned from the Discord server is suspended until they rejoin.

FreeBasicPro
Named team members03Unlimited
Discord role mappingsNoYesYes
Real-time role syncNoNoYes

A mapped role admits everyone who holds it, so mappings carry the same paid requirement that named members do. On a free plan the mappings you created are kept, but they stop granting access. Mapping a Discord role that a saved config already gives out (a flow button, an application form's role automation, a stat role rule, or rank sync) lists those configs and asks you to confirm first, since everyone they give the role to gets the team role's permissions. Adding permissions to a mapped role, on this page or by reverting a change in the Audit Log, asks the same.

Permissions

Admin

Everyone on the team can view the dashboard. What else a role can do is ticked per area on the Team page; each group has an All switch. You can only grant permissions you hold yourself, and only a set below your own, so two people with the same access can't change each other's roles.

AreaPermissionCovers
ServerServer settingsName, gameplay toggles, parked server swap, setup wizard, deleting the server
ServerRestartsRestart now, and edit schedules (a backup task also needs Backups; a command task, or a restart with its own stop command, also needs Run commands)
BridgeChat bridgeChat channel, rendering, whispers, content filter
BridgeFeedsEvent, status, health and moderation log channels, counters
ModerationBansBan sync settings, and the Discord moderation commands when the server allows it
ModerationAlertsStat alert rules, anticheat alerts and alert history; look up and dismiss alerts
MembersLinking settingsNickname format, onboarding, how accounts link
MembersUnlink playersUnlink a player's account
MembersIn-game rolesRank tags and teams
MembersStats and stat rolesTracked stats, stat role rules, resets, bundles, stats timezone
WhitelistWhitelistWhitelist rules and players
ApplicationsReviewAccept, deny, request info, reset cooldowns
ApplicationsFormsCreate and edit application forms
ApplicationsDeleteDelete forms and their responses
BotMessagesMessage templates, authored messages, panels, button flows
BotCommandsCustom commands, prefixes, command settings
BotBrandingCustom bot name, avatar and footer
Mods and configModsInstall, update, disable, delete mods
Mods and configConfig filesEdit server config files, except guarded keys
Mods and configGuarded configRCON, online mode, proxy and forwarding keys, config reload
ConsoleRun commandsRun console commands
ConsoleRead consoleRaw server log, command text in the audit log and pending restarts
ConsoleConfigure consoleConsole channel (with Read console), allow and deny lists, presets, alerts
Team commandsRunSee and run team commands
Team commandsOwnAdd, edit, delete your own team commands
Team commandsAllManage every team command
WorldBackupsBack up and download the world, rename and pin backups, keep count, backup schedules (with Restarts)
WorldWorldsRestore and delete backups, regenerate the map, create, upload and switch worlds, modpacks
WorkspaceBillingStart a plan, buy Lifetime, take over paying
WorkspaceTeamRoles and members
WorkspaceAudit logThe dashboard activity log
WorkspaceImportImport settings from DiscordSRV

Minting or rotating a server token, importing DiscordSRV linked accounts and choosing whether moderators may use the Discord moderation commands are the server owner's alone; no permission grants them.

Presets

Admin

A preset ticks a starting set of boxes when you create or edit a role. The role keeps the ticks, not the preset, so changing one box later makes it Custom.

PresetTicks
ViewerNothing beyond viewing
HelperReview, Whitelist, Run
ModeratorReview, Whitelist, Run, Unlink players, Bans, Audit log
TechnicianMods, Config files, Backups, Restarts, Read console, Own
AdminServer settings, Restarts, Chat bridge, Feeds, Bans, Alerts, Linking settings, Unlink players, In-game roles, Stats and stat roles, Whitelist, Review, Forms, Delete, Messages, Commands, Branding, Mods, Config files, Run commands, Read console, Configure console, Run, Own, All, Backups, Worlds, Audit log, Import

Roles from before the split

Admin

Roles made before permissions were split by area keep exactly the access they had, read as the new permissions until you next change their permissions (renaming one keeps it as it is):

Old permissionNow
ServerServer settings, Restarts, Chat bridge, Feeds, Bans, In-game roles, Stats and stat roles, Branding, Import
LinkingLinking settings, Messages, Commands
PlayersUnlink players
ConsoleRun commands, Read console, Configure console, Team commands: All
ModsMods, Config files
Mods and Console (on one role or across your roles)Guarded config as well
WorldBackups, Worlds
Commands: View, Own, AllTeam commands: Run, Own, All
Applications: Review, Manage, DeleteApplications: Review, Forms, Delete
Billing, Team, Audit LogBilling, Team, Audit log

Because an old Mods role and an old Console role add up to Guarded config, adding a member to either one, or connecting a Discord role to it, needs Guarded config yourself.

Real-time role sync

Pro Admin

The toggle on the Team page decides how often a member's Discord roles are re-read:

  • Off (login): roles are re-read at most once every 10 minutes, so removing a Discord role revokes access within that window.
  • On (real-time, Pro): roles are re-read on every dashboard page load, so removing a role revokes access at once.

Real-time sync fails closed: if Discord can't be reached, access granted by a role mapping is withheld for that request rather than falling back to what the roles used to be. Named team members are unaffected either way.

Changing someone's Madsi role, or adding and removing mappings, always takes effect immediately on both settings, only the member's Discord role list is cached.