Skip to content
RyzenHosting

Game and app servers

Sharing a server with other people

Give someone their own access to your game server, choose exactly what they can do, and understand which permissions actually hold today.

Last reviewed 2026-10-04

You can let other people run your game server with their own account, so you never hand out your own sign in.

Open your server and click Team. Only the owner of the service can change who has access.

Add someone

They need an account here first. Ask them to sign in with Discord once. That is all they have to do.

Then:

  1. Type their Discord name or email in the box. Whatever they signed in with.
  2. Tick what they are allowed to do.
  3. Click Give them access.

We look the person up and nothing is sent to a stranger. If the panel says nobody with that name has signed in yet, they have not done their one sign in.

The server then appears in their own client area, under their own account.

You can share a server with up to 10 people.

What they start with

A sensible starter set is ticked for you: watch the console, start, stop and restart the server, read files and see the backup list. Back to the basics puts it back if you have been clicking around.

Add more only where you need to.

The permissions

They are grouped. Each group header has Select all and Clear.

Console. Read the console, Start, Stop, Restart.

Files. Browse, Open files, Create, Change, Delete, Archive, SFTP.

Backups. See backups, Create, Download, Delete, Restore.

Databases. See databases, Create, Change, Delete, See passwords.

Schedules. See schedules, Create, Change, Delete.

Ports. See ports, Add, Change, Release.

Startup. See settings, Change, Change the runtime.

Server. Rename, Reinstall.

Activity. See activity.

Three of those groups are marked as sensitive, with a warning triangle: Ports, Startup and Server. They change how the server runs or take it offline. Only hand them out to people you trust with the server itself.

Reinstall is the one to think hardest about. It lays the server files down again and can overwrite everything on disk.

At least one permission has to be ticked.

What the owner keeps

Four things cannot be delegated to anyone.

  • Managing the team itself. Only you decide who has access.
  • Billing.
  • The plan.
  • Add-ons.

People you share with see the server, see who else is on it and what each person is allowed to do, but those four tabs are not there for them. They also cannot rename the service in your own list.

Permissions that do not do what they say

Be aware of these before you rely on them. They are the honest position today, not what the labels imply.

Console start, stop and restart are not actually checked. Anyone who can open the console can start, stop, restart and kill the server, whether or not you ticked those boxes. If you do not want someone able to take the server offline, do not give them console access at all.

The Databases tab is owner only. The five database permissions do not open that page for anyone else. If someone needs the database credentials, you have to pass them on yourself.

Uploading a file is owner only. Someone with Files: Create can make folders, edit, rename and delete, but the upload button will not work for them.

Archive does nothing. There is no compress or extract control in the file manager, so that permission has nothing to apply to.

We would rather tell you than leave you to find out. If any of this matters to how you want to run the server, email [email protected].

Changing what someone can do

Click Permissions on their row, tick or untick, then Save permissions. It applies immediately.

Removing someone

Click Remove on their row and confirm. They lose every way into the server, including the console and file access. Nothing on the server itself is deleted and you can add them back later.

If someone's access is not working

Occasionally a person is saved on our side but never finished linking to the game node. You will see a warning saying so on their row, with a Repair the link button. Click it.

If that does not fix it, remove the person and add them again. That rebuilds their access from scratch.

Keeping track

Everything anyone does is written to the activity log with their name, the time and where they did it from. That is the page to open when you want to know who restarted the server at three in the morning.