Español
English
Français
Português
👥 What a subuser is
A subuser is another person with access to your server in ZentexGame, our game panel. They log in with their own account and can only do what you tick, so you never have to share your password. Payments, renewal and cancellation stay in your ZentexNode account: subusers don't see them.➕ 1. How to add a subuser
- Open your server in ZentexGame. In the server menu, under Tools, click Users.
- Click New user. The Create new subuser window opens.
- In User Email, type the email of their ZentexNode account.
- Tick the permissions (step 2 explains them). The box in the header of each group ticks or unticks the whole group.
- Click Invite User.
If that person doesn't have an account yet, the panel creates one with that email and sends them a welcome email with a Choose my password button. That button opens Forgot your password? on zentexnode.com: they enter their email there, get a link, set their password and can then log in to ZentexGame with that email. The same password also works on the website and over SFTP.
Use the right email: if your friend already has an account and you type a different email, the panel creates a new account, and when they log in with their own they won't see your server. Ask them for the email they use to log in to ZentexNode.
🔐 2. What each permission does
Every subuser can see the console, the server status and its address. Everything else comes in groups:| Group | What it allows |
|---|---|
| Control | Console: type commands. Start, Stop and Restart: the power buttons. With Restart they can also start the server when it's off, but not leave it off. |
| User | Create, Read, Update and Delete other subusers. They can only hand out permissions they have themselves. |
| File | Read: browse folders. Read Content: open and download files. Create: create, upload, save changes and unzip. Update: rename and move. Delete, Archive (compress) and SFTP: connect over SFTP with their own username. |
| Backup | Backups: Create, Read (see them), Delete, Download and Restore. |
| Allocation | The server's ports, in the Network tab. |
| Startup | Read and Update the variables in the Startup tab. Docker Image: change the image the server runs on. |
| Database | Create, Read, Update (change the password) and Delete databases. View Password shows it. |
| Schedule | Scheduled tasks, such as automatic restarts. |
| Settings | Rename the server and Reinstall it. |
| Activity | Read: see the log of what's done on the server. |
| Support | Tickets: lets them ask us for help on Discord (step 4). |
🧩 Three common setups
- A friend who only starts and stops it: under Control, tick Start, Stop and Restart. They'll see the console but can't type commands or touch files. If you want them to use commands, add Console.
- A trusted admin: the whole Control, File and Schedule groups; under Backup, Create, Read and Restore (restoring can wipe the current files); Activity → Read and Support → Tickets. Leave out User if you don't want them adding anyone else. Before giving them Startup, read step 3.
- Someone who uploads mods and files: the whole File group (with SFTP, uploading a lot is easier: how to connect over SFTP), Control → Restart to apply changes and, under Backup, Create and Read, so they can make a backup before touching anything. On Minecraft, that's enough to install and remove plugins and mods from the Plugins or Mods tab.
⚠️ 3. Careful: passwords are visible
Anyone with Startup → Read sees the variables in the Startup tab as they are, passwords included: the Steam account used by DayZ, Arma 3 or Assetto Corsa, and the RCON or admin password of games like Rust, ARK or Project Zomboid. With Startup → Update they can also change them. Other permissions that expose passwords too:- File → Read Content: opens the config files, which often store passwords.
- Backup → Download: the backup contains every file on the server.
- Database → View Password.
💬 4. Support for your subusers
If you tick Support → Tickets, that person can also open tickets about your server on our Discord. For that:- They have to be on our Discord and have their Discord linked to their ZentexNode account: in their client area on zentexnode.com, go to Account, section Linked accounts, and click Link next to Discord.
- Our bot gives them the SUB CLIENTE role when they link it, when they join the Discord or, at most, about 10 minutes after you tick the box. If you untick it, the role is removed the same way.
🖥️ 5. On VPS they're called guests
In ZentexCloud, the VPS panel, the same thing is done with guests: open your VPS and, in the Users section, click Invite someone, type the email, pick the permissions and click Give access. What's different:- The other person must already have a ZentexNode account: here it isn't created for them.
- You can have up to 5 guests per VPS.
- There are one-click templates: View only, Console only (KVM), Power and Full control. If you change a single box, it becomes Custom.
- The Firewall box only comes ticked in Full control. With it, the guest can change the firewall rules for that VPS's IPs and so can also cut it off from the network (the console keeps working).
- With Open tickets for this VPS, they also get the SUB CLIENTE role.
- Seeing the status, graphs, resources, IPs and expiry date is always included. They can never delete the VPS, change its plan or invite others.