How teams work on Schokr and how to create one
Teams on Schokr share a resource pool, servers and credits. Learn how to create a team and what belongs to the team versus you.
Updated · 2 min read
A team is the place your servers, resources and credits live on Schokr. Each team has its own free package and its own members, roles and permissions. You can be in up to 2 teams.
What belongs to a team
| Belongs to the team | Belongs to you |
|---|---|
| Servers | Your login and password |
| The resource pool (6 GB memory, 150% CPU, 10 GB disk, 4 slots on the free package) | Your linked Discord account |
| Store upgrades bought for the team | Your profile |
| Credits | Your membership in up to 2 teams |
| Roles and members |
Because credits and upgrades belong to the team, everything the team buys benefits all of its servers. Credits can be transferred between teams.
Why use a team?
- Share management with friends or co-admins without giving out your password.
- Control access precisely with roles, for example letting a moderator use the console but not delete files.
- Separate projects. Use one team for a Minecraft community and another for your personal bots, each with its own pool.
Create a team
- Sign in at console.schokr.gg.
- Open the team switcher or team settings.
- Create a new team and give it a name.
- Switch to the new team. New servers you create go into the team you currently have selected.
If you are already in 2 teams, you need to leave one before you can create or join another. See being in two teams.
Next steps
- Create roles for the kinds of helpers you have. See team roles and permissions.
- Invite members by email. See inviting people to your team.
- Create servers in the team. See creating your first server.
The team owner
The person who creates the team is its owner. The owner has full control, including inviting people, managing roles and billing. Ownership can be handed to another member later, see transferring team ownership.
Good practices
- Give each person their own account. Never share one login between several people.
- Use the least access needed. Start new members with a limited role and add permissions when they need them.
- Review members now and then. Remove people who no longer help out.
- Check the activity log if something changes unexpectedly. See the activity log.