With co-managers, you give other people access to your GSH server through their own account. Choose the permissions they need and set an expiry date for temporary work. A template is the starting point; afterward, check allowed and blocked actions using the invited account.

Where to find the co-managers

Open your server in the customer area and select the Access section. There you will find the tabs Domain, Co-Managers, Public Status Page and Webhooks. Under Co-Managers you can see everyone who co-manages your server, the open invitations, and the Invite Co-Manager button.

Only the owner of the server can invite, change permissions, and remove co-managers. If you are a co-manager yourself, you will see a corresponding notice here.

Invite co-managers in the customer panel

Inviting someone

  1. Click Invite Co-Manager.
  2. Enter the person's email address.
  3. Optionally set an expiry for access: If you enter a date, access ends automatically on that day. If left empty, access is unlimited.
  4. Under Template, choose a starting point for the permissions and adjust the individual checkmarks as needed. With All/None you can set or remove all checkmarks at once.
  5. Click Invite.

What happens next depends on whether the person already has an account with us. If they have an account with a confirmed email address, they get access immediately. Otherwise, the panel sends an invitation by email with a registration link that is valid for 7 days. As long as it has not been accepted, it appears under Open Invitations. There you can Resend it, which invalidates the previous link, or Withdraw it.

After accepting, the invited person will find your server in their own server list, marked as Co-Managed.

The templates

The templates are starting points; you can then set or remove each checkmark individually.

  • View only: Read along in the console, nothing else. Good when you want someone to look over your shoulder while troubleshooting.
  • Moderator: Plus starting, stopping, and restarting the server and moderating players, meaning kicking, banning, unbanning, and sending messages.
  • Technician: Plus managing mods, viewing, opening, creating, and editing files, packing and unpacking archives, and viewing and creating backups.
  • Full operations access: Plus restoring backups, viewing and creating databases, managing schedules, changing the address, and importing worlds.

Some permissions are not included in any template because they irreversibly delete data or open up access: deleting files, SFTP access, deleting backups and databases, deleting schedules, and the settings of the Discord bot. Only set these checkmarks deliberately and only for people you fully trust.

Changing permissions and ending access

In the co-manager list, each row shows how many permissions the person has. Use Edit permissions to change the checkmarks later, and use Remove to revoke someone's access immediately.

If a co-manager is missing a permission, they see a notice with the missing permission and can ask you for it using Ask the owner. Conversely, any co-manager can end their own access via Leave access.

If it does not work

  • The invitation does not arrive: Ask the person to check their spam folder, and use Resend. You can send at most 5 invitations per hour.
  • The panel reports "Server is offline — please start it first.": Start the server and open the tab again.
  • Free servers: The number of co-managers and the choice of permissions are limited there; the panel shows the limit directly in the invitation window.
  • A co-manager cannot schedule restarts: Only the owner can create automatic restarts, see Schedule automatic restarts for your server.

The other panel guides show which areas each permission unlocks, for example Edit server files in the panel and connect via SFTP, Use the server console and Create and restore a server backup.

Checking an invitation against the required task

First decide whether the person should only read logs, moderate, or edit files. Check the selected permissions one by one instead of automatically using "All". After acceptance, use the person's own account to verify one allowed function and one management action that was deliberately not granted. If an invitation is resent, the person uses the new link; an old one may be invalid. For temporary assignments, document the end date and the task. Remove access that is no longer needed once the work is done and check the co-manager list again. Your main account password always stays with the owner.