Invite a teammate to your game server

GiveUse Users to let a teammate theirmanage ownan existing game panelserver. loginUse andSplitter, choosewhere whichyour serverplan actionsincludes theyit, canto use.divide Athe game-panelplan's subuserresources between separate game servers. Each action changes a different part of your setup; inviting someone does not gaincreate ownershipanother ofserver theor transfer your billing account or access to your other servers just because you invite them here.account.

Before you invite anyoneteammate

1. Open the correct server at game.cloudexa-hosting.com. YouCheck needits permission to create users,name and youaddress canbefore grantchanging onlyaccess.
2. Open theUsers permissionsand yourchoose accountNew canUser. manage. UseEnter your teammate's own email address ratherin thanUser sharingEmail.
3. Choose youra login.Role DecidePreset whatas a starting point, then review the personselected needspermission rows. Grant the actions they need for their role.
4. Choose Invite User and confirm that their entry appears in Users.
5. Ask the teammate to do.sign in using their own account and check that they can open the assigned server. A new panel user should check their inbox and spam folder for account-access instructions.

Review the permissions

Console commands can grant in-game privileges;privileges, file access can expose configuration secrets;secrets, and backup downloads can contain the whole server. Give each permission the same attention you would give the files themselves.

Send the invitation

1. Open the server's Users section and choose New User.
2. Enter the teammate's address in User Email. Check the spelling before submitting.
3. Review Role Presets or tick individual permissions. A preset is a starting selection; check the actual permission rows before saving.
4. Choose Invite User. Confirm that the user appears in the server's Users list.
5. Ask your teammateserver tofiles. check their email, including spam, for the account-access instructions if they need a new panel account. Existing panel users should sign in using their own account.

Choose permissions with care

• Full Access (Select All) grantsand the permissions you can assign. Reserve it for someone you trust to administer the server.
• Power User (Control + Files + Backups) includesinclude actions that can change andor delete files.data. ItThe is more than a console-viewing role.
• Moderator (Control + Users)preset includes user management. DoReview notthose selectrows itbefore forgranting someoneaccess. who

  Review shouldthe only moderate chat inside Minecraft.

• Viewer (Read Only) is a convenient starting point for limited access, but review its selected permissionspreset too. In the current panelpanel, preset,its Console accessselection can include sending commands. Remove that permission if the teammateperson mustshould notonly issuewatch commands.

output.

CheckTest andthe changeintended access

Askwith the teammate rather than granting everything to opensolve onlya themissing assignedbutton.

server

To andchange confirm they can complete the intended task. If something is missing,access, edit their entry in Users, adjust the relevant permissionUsers and choose Save. Avoid selecting everything just to fix one missing action.

To endrevoke access,it, use the user's delete control and confirm Yes, remove subuser. ThisRemoving a subuser revokes theirthat person's access to thatthis server.server; it does not remove the game files. Review access when a teammate leaves or changes role.

Understand server splits

A split creates a separate server using resources from its parent plan. It does not eraseduplicate your full RAM, CPU and storage allowance. Resource allocations reserve capacity even while a child server is stopped. For example, a child allocated 4 GB from a 12 GB RAM entitlement leaves 8 GB for the gameparent worldand other children combined.

Leave enough RAM and disk for the parent to run. Check actual disk usage before reducing an allocation: setting a smaller limit does not remove files or cancelmake them fit. A split also needs an available split slot and a usable network allocation. CPU allocations and usage are different measures; the panel's current usage graph alone does not show the resources left to allocate.

Find Splitter in the left-hand server menu, as shown in the Users screenshot above.

Plan a split or resource change

1. Check your service.plan's split allowance and the resources already assigned to children.
2. Record the parent and child server IDs and the RAM, CPU and storage you intend each to use.
3. Open Splitter on the parent and review the controls available to your plan. Ask support if the page or a needed allocation is unavailable.
4. Review teammates'the proposed allocation before confirming a change. Check the resulting limits on both parent and child.
5. Check each child's Users and Backups sections. Do not assume that a parent's teammate access whenor theirbackup roleslots changesgrant the same access or theyallowance leave.on every child.

Before moving existing worlds or configuration between servers, take a backup and preserve both copies until you have checked the result. Do not remove a parent or child server to clear a resource error: server removal can delete files, and removing a parent can also remove its children.

If theaccess invitationor allocation fails

CheckFor invitations, check the email address and whether theexisting user already appears in the list. Record the error and time of the attemptlist before retrying. For a remaining-resource error, compare allocated limits across the parent and children, not just live usage. Send support the serverIDs, IDintended change, time and thefull affected emailerror through a private ticket,ticket. withoutKeep includingpasswords passwords.and AAPI missingkeys Usersout buttonof canscreenshots.

indicate that your own account lacks user-management permissions.