Team & permissions
Invite your staff and control exactly what each of them can do and which servers they can touch. Everything is enforced by the backend, not just hidden in the interface.
Inviting a member
In the Team panel, invite someone by email. They receive an invite link and create their own account — they choose their own name at sign-up, and that name is what shows in your team list. Until they finish signing up, they appear with an Invite pending badge, which flips to active automatically once their account is created.
Permissions
Each member gets a set of permissions. Grant only what they need:
| Permission | Lets them |
|---|---|
| Warn players | Give warnings. |
| Kick players | Kick players from a server. |
| Ban players | Ban players (enforced on join). |
| Send alerts | Send on-screen title alerts to players. |
| Retract warns | Remove warnings from a player's history. |
| Unban players | Lift bans. |
| Invite team members | Manage the team: invite, edit and remove members. |
Server access
You can give a member All servers or scope them to specific servers. A gamemode moderator scoped to just Survival only sees Survival's players, flags and map, and can only moderate there. Global moderators keep all servers. This scoping runs on the backend, so a scoped member genuinely can't see or touch anything outside their servers.
Cancelling an invite & removing members
Cancelling a pending invite invalidates its link — the person can no longer use it to join. Removing an existing member revokes their access immediately: the next time they sign in they're no longer part of your network, and if they aren't a member of anything else they simply land on the plan-chooser as a new owner would. You can never remove or edit the owner, and no one can act on their own membership.