How to set up team roles and permissions on Schokr
Create custom roles on Schokr with granular permissions for console, power, files, backups, snapshots, startup, billing and more.
Updated · 2 min read
Roles decide what each team member can do. Schokr roles are custom, so you choose exactly which permissions each one gets, then assign roles to members.
Permission areas
Permissions are grouped by area. The main ones:
| Area | What it controls |
|---|---|
| Console | Viewing the console and sending commands |
| Power | Starting, stopping, restarting and killing servers |
| Files | Viewing, uploading, editing and deleting files |
| Backups | Creating, restoring and deleting backups |
| Snapshots | Creating, restoring and deleting snapshots |
| Schedules | Creating and editing scheduled tasks |
| Startup | Changing the startup command and variables |
| Network | Managing port allocations |
| Resources | Changing a server's memory, CPU and disk |
| Settings | Server settings like name, reinstall and deletion |
| Activity | Viewing the activity log |
| Billing | Credits and payments |
| Store | Buying upgrades with the team's credits |
Within an area, permissions can be granular, for example reading files without being able to delete them.
Create a role
- Open your team's settings in the console.
- Go to roles and create a new one.
- Give it a clear name, like "Moderator" or "Bot developer".
- Tick only the permissions that role needs.
- Save, then assign the role to members.
Example roles
Moderator (game server)
- Console: view and send commands
- Power: restart only, if your game needs it
Moderators can kick, ban and broadcast without touching files.
Builder or config helper
- Console
- Files: read and edit, no delete
- Power: restart
Bot developer
- Console, power
- Files
- Startup
Co-admin
Everything except billing, store and settings that delete servers.
Least privilege
Give each person the smallest set of permissions they need. In particular, be careful with:
- Files and Startup: these can expose bot tokens, API keys and passwords stored in config files and variables.
- Backups and Snapshots: restoring overwrites the live server and deleting removes your safety net.
- Settings: can include destructive actions like reinstalling or deleting a server.
- Billing and Store: let someone spend the team's credits.
- Resources: lets someone take memory or CPU from one server to give to another.
Review regularly
- Remove permissions people no longer need.
- Check the activity log to see who did what.
- When someone leaves, remove them and rotate any secrets they had access to.
For inviting members, see inviting people to your team.