Skip to content
CatalystCatalyst Docs

Users & Subusers

The Users tab (titled Users & Access) adds subusers: extra accounts with limited access to your server. Your friend signs in with their own account and sees only what you allow.

Prerequisites

Section titled “Prerequisites”
  • A server you own or administer — plain subusers cannot invite others.
  • The permissions you intend to grant: you cannot grant a permission you do not hold yourself.
  • For invites by email, a panel with email delivery configured. Without it, the panel shows a copyable invite link instead.

Invite a subuser

Section titled “Invite a subuser”
  1. Open the server’s Users tab and find Invite user.
  2. Enter their panel account email.
  3. Pick a preset:
    • Read-only — view the server, console, files, databases and alerts.
    • Power user — read-only plus power actions, console commands, file editing, backups and database management.
    • Full access — the full preset: also startup changes, ports, tasks, cloning, mods and plugins, transfer, and deleting the server. It does not include backup.pin (pinning a backup is reserved for explicit grants).
    • Custom — tick exactly the permissions you want; they are grouped by area (console, file, server, …).
  4. Select Send invite.

When email delivery is available the panel emails the invite; otherwise — or if delivery fails — an Invite link dialog appears. Select Copy and send the link yourself. The invite is bound to the email you entered: the invitee accepts it by signing in with that address, or by creating an account for it on the invite page. Someone signed in as a different account is asked to sign out first. Keep the link private — it grants the assigned permissions to whoever opens it with that account.

Invites expire after 7 days. A pending invite has Copy link to share it again, Regenerate (the old link stops working), and Cancel. Once accepted, the server appears in the subuser’s list.

Adjust or remove access

Section titled “Adjust or remove access”

Active access lists everyone with access and their permissions. For a subuser, toggle the permission chips and select Save permissions, or select Remove to revoke access. Removal is immediate. The owner is marked Owner and cannot be removed here.

Least privilege, always

Section titled “Least privilege, always”
  • Every permission is a way to break something: console access can run destructive commands, file access can delete worlds, power access can stop the server mid-event.
  • Remove subusers who no longer play. Stale access is the most common source of “someone griefed my server files” stories.
  • Never share your own login instead — then nobody can tell who did what in Activity, and you cannot revoke access without changing your password.
Section titled “Related”