Managed infrastructure for SMBs
Staff Access and Permissions for a Minecraft or Game Server Network
The short answer
Most game network incidents that start inside the team come down to access: a moderator with full console rights, a shared login that five people know, a developer who left months ago and still has file access, or a new staff member given everything on day one because it was quicker. Giving each person only the access their role needs, tying every login to one named person, and removing access the day someone leaves will prevent most of these problems. This guide covers how to set up roles, what to lock down on the panel, console and file access, and a checklist you can work through with your team this week.
1. Write down your roles before you hand out access
Start with a short list of roles and what each one actually does, not with the permission screens. A typical network has an owner, one or two administrators, developers who work on plugins and configs, moderators who handle players, and support staff who answer tickets. For each role, write one line on what they need to do, such as "restart the lobby and read the console" or "upload plugin builds to the development server". That list becomes the rule you check every permission against. If a request does not fit the role, it needs a conversation, not a quiet grant.
2. Separate owner, admin, developer and moderator access
Owner access should belong to the person who owns the network and pays the bills, and only they should be able to add or remove administrators, change billing or delete servers. Administrators run the day to day infrastructure. Developers need file and console access to development and test servers, and usually read access to production logs, but they should ship changes to production through a reviewed process rather than editing live files. Moderators deal with players: in-game ranks, bans, chat and reports. Moderators rarely need the hosting panel at all, and almost never need file access. Keeping these layers apart means one compromised or careless account cannot take down the whole network.
3. Least privilege on the panel, console and file access
Most game panels let you add sub-users to a server with a chosen set of permissions. Use them instead of sharing the main account. Give each person access only to the servers they work on, and only to the actions they need. Console access is powerful, because the console can usually run any server command, including ones that give operator status or change permissions plugins, so treat it as an admin level permission. File access over SFTP is even more powerful, since it allows uploading plugins and editing configs that run code on the server. Give SFTP to developers on the servers they own, not to moderators, and prefer read access to logs where that is enough.
4. In-game permissions are a separate layer
Your permissions plugin and in-game ranks are a second set of access controls, and they need the same care. Keep operator status for the smallest possible group, give staff ranks only the commands their role uses, and avoid wildcard permissions on staff ranks. Review rank inheritance so that a moderator rank does not quietly pick up admin commands from a parent group. Changes to staff ranks should be made by an administrator and recorded, not by the staff member being promoted.
5. No shared accounts
A shared panel login, a shared SFTP account or a shared database password means you cannot tell who did what, and you cannot remove one person without changing the password for everyone. Give every staff member their own account on the panel, on file access and on any other tool you use, such as the store, the forum or the ticket system. Where a tool only supports one login, keep it with the owner or an administrator and do not hand it out. Service passwords used by plugins should live in config files that staff do not need to read, not in a shared chat channel.
6. Turn on two-factor authentication everywhere
Staff accounts are a common target, because one stolen moderator or admin login can be enough to ruin a network. Require two-factor authentication for every staff member on the hosting panel, on your billing account, on the email accounts used to reset passwords and on Discord or any other chat where staff coordinate. Prefer an authenticator app or a hardware key over text messages. Make two-factor a condition of getting access, not something people are asked to add later.
7. Keep audit logs and actually read them
Panels usually keep an activity log of logins, file changes, power actions and console commands per user. Make sure it is turned on, know where to find it, and check it after any incident and on a regular schedule. Keep in-game staff action logs as well, such as bans, rank changes and commands run by staff. Because every person has their own account, the logs show who did something, which turns most "who broke the lobby" questions into a quick lookup.
8. Take a backup before giving new access
Before you add a new developer or admin, or widen anyone's permissions, take a fresh backup of the servers involved and confirm it finished. If something goes wrong in their first week, by mistake or on purpose, you can roll back to a known good state. Make sure you can actually restore those backups, not just that they exist. Our backup restore test checklist walks through how to prove it.
9. Offboarding staff the same day
When a staff member steps down or is removed, remove their access the same day, in one pass, using a written list. That list should include the hosting panel sub-user, SFTP and any database accounts, in-game ranks and operator status, store and forum admin roles, Discord or chat roles, and any shared tool they were given. Rotate any password or token they may have seen, including service passwords in configs they could read. Then check the audit log for recent activity from their accounts. A clean offboarding is also fairer to the person leaving, because nobody can blame them for something done after they left.
Staff access checklist
- Roles are written down, with one line on what each role needs to do.
- Only the owner can add or remove administrators, change billing or delete servers.
- Every staff member has their own panel, file access and tool accounts, with no shared logins.
- Console and SFTP access are limited to the people and servers that need them.
- Moderators work through in-game ranks, not the hosting panel or file access.
- Operator status is held by the smallest possible group, and staff ranks avoid wildcard permissions.
- Developers work on development servers and ship to production through a reviewed process.
- Two-factor authentication is required for every staff account, including email and chat.
- Panel activity logs and in-game staff logs are turned on and reviewed on a schedule.
- A fresh, tested backup is taken before any new access is granted.
- Offboarding follows a written list and is done the same day, with passwords and tokens rotated.
Next steps
GlassHosting is a managed service and infrastructure provider: we run your servers on our own network, so you can run your business. For commercial game networks that means staff roles, access, two-factor and backups set up with you and kept tidy as your team changes, alongside the servers themselves. If you are running a community server instead, Glass Gaming, powered by GlassHosting, has supported games ready to go. Related reading: proxy and lobby layout for game networks and the backup restore test checklist.
Host with GlassHosting
Order a plan or browse the knowledgebase for deeper how-tos.