Team Collaboration

Rust Server Admin Roles and Team Access

Stop sharing RCON passwords.

Invite your admin team with proper roles and permissions. Everyone gets their own login. Every action is attributed. No more shared credentials.

5 Built-in Roles

Owner, Admin, Operator, Moderator and Viewer. Moderators can kick, ban, write notes, handle F7 reports and broadcast without server control. Viewers are read-only.

Email Invitations

Invite team members by email. They create their account, accept the invitation, and join your team with the role you assigned. Manage pending invites and resend if needed.

Activity Log

A team-wide activity log records who did what: server actions, setting changes, bans and player actions, each with the admin's name and the time.

1

Permissions that make sense

An Operator can start and stop servers, execute RCON commands, and manage players, but can't change server settings, modify team membership, or delete instances. A Moderator handles players (kick, ban, notes, F7 reports, broadcasts) without touching server controls. A Viewer can see dashboards and metrics but can't take any actions. Only Owners and Admins can invite members, change server settings or wipe.

2

Audit and activity log

Every team has an activity log that answers the question every admin team eventually asks: who did that? Server actions (start, stop, restart, wipe), setting changes, bans and other player actions are recorded with the admin who did them and when. RCON commands run from the web console are attributed to the admin who sent them. When something breaks at 3 AM, you can see what changed and who changed it instead of asking around in Discord.

3

Shared server templates

Save a server's complete configuration (settings, framework, plugins, permission groups, extensions and backup schedules) as a template that any team member can use to spin up new servers. Standardize your server setup across your community without manual configuration.

4

Cross-server coordination

All servers in a team share the same ban lists, player notes, and automation history. When an admin bans a player on one server, the ban is enforced when they join any server in the team. Player notes written by one admin are visible to everyone.

5

Multi-team support

Users can belong to multiple teams. Run different communities or game server networks under separate team workspaces, each with their own members, servers, and configuration, all from one account.

Ready to get started?

Free during open beta. No credit card required.