Sharing a service with others and transferring it to another account

You can manage a service together with other people without giving them the password to your account. Everyone gets their own access to just what they need. If you want to give the service to someone else for good, use a transfer.

Sharing or transfer?#

Inviting a collaborator#

1. In the customer area, open My services, click the service and go to the Access tab.

2. In the Share with other accounts section, enter the address of the person you're inviting in the Email field.

3. Under Permissions, tick only what they really need. The table below explains what each permission allows.

4. Click Invite.

   You'll see Invitation sent. and the invited person appears in the list with the status waiting for acceptance.

What the invited person does:

1. Signs in to the customer area with an account using the same email address the invitation was sent to. If they don't have an account, they sign up with that address and verify their email.

2. Opens the Invitations section.

3. Clicks Accept on the Invitation to manage a service.

   The service appears in their My services with the shared tag. On your side, the status changes to active.

Permissions explained#

The available permissions differ by service type. Always give only the minimum needed: someone who doesn't need to change the firewall shouldn't have access to it.

Changing and removing access#

In the Access tab you see each member's permissions and status.

• Changing permissions: tick or untick permissions and click Save permissions. At least one has to remain.
• Removing: click Remove and confirm. The member stops seeing the service immediately.

A member can end the sharing themselves: in the service detail they see the bar This service is shared with you — owner … with a Leave button.

Transferring a service to another account#

1. Open My services, click the service and go to the Transfer tab.

2. In the New owner's email field, enter the address of their account with us.

3. In the Your account password field, enter your password. We use it to confirm that it's really you starting the transfer.

4. Tick the box agreeing that once the transfer is accepted, the new owner gets the service and all rights to it.

5. Click Start transfer and confirm.

   You'll see The transfer has started. and the line Transfer to … is waiting for confirmation (valid until …).

The recipient has 7 days to confirm:

1. They sign in with the account whose email the transfer is addressed to.
2. In the Invitations section they find Service transfer to your account.
3. They click Accept and confirm Take over the service into your account? You'll become its owner.

Until the recipient confirms, you can stop the transfer by clicking Cancel transfer. If they don't confirm within 7 days, the transfer lapses and the service stays with you.

You can't start a transfer when:

• an upgrade or a started payment is being completed for the service (An upgrade or payment is being completed for this service — start the transfer once it's done.),
• another transfer of the same service is already pending,
• you enter your own email.

In addition, a game server has to be active when the transfer is confirmed.

What happens automatically during a transfer#

• All sharing of the service is cancelled. The members you invited lose access.
• Unpaid upgrade orders for this service are cancelled.
• VPS: the stored root password and the Files tab login details disappear from the customer area. The new owner won't see them there, because the previous owner knows them too.
• Game server and bot: additional server access is removed and the passwords of all the server's databases are changed. The new owner finds the new passwords in the Database tab. Plugins and scripts that use the database need to be reconfigured.
• Minecraft: the address from the Domain tab stays, and players keep connecting the same way.

Invoices that have already been paid stay in the account that paid them.

After a transfer: securing things for the new owner#

The previous owner and their collaborators may have known passwords or kept some access. So go through these steps right after taking over the service.

VPS#

1. Ask the previous owner for the root password through a secure channel (not a public chat). If you don't have it, contact support.

2. Connect to the VPS (guide) and change the root password:

   passwd

   • passwd – changes the password of the signed-in user (here root). You enter the new password twice; nothing is shown as you type.

   More detail in Securing a new VPS.

3. List the SSH keys that have access to root:

   cat /root/.ssh/authorized_keys

   • cat – prints the contents of a file.
   • /root/.ssh/authorized_keys – the list of public keys that can sign in as root. Each line is one key, usually with a label at the end.

   Delete the lines with keys you don't recognize (in the editor nano /root/.ssh/authorized_keys; save with Ctrl+O, exit with Ctrl+X).

4. List the users who can sign in:

   awk -F: '$7 !~ /(nologin|false)$/ {print $1, $7}' /etc/passwd

   • awk -F: – reads the file line by line, splitting columns at colons.
   • $7 !~ /(nologin|false)$/ – selects only users whose login shell (column 7) isn't nologin or false, that is, those who can sign in.
   • {print $1, $7} – prints the user name and its shell.
   • /etc/passwd – the list of system users.

   The output always includes root and usually also sync with the shell /bin/sync. That one is a system user, don't delete it. Users of installed programs are system users too, for example postgres for the PostgreSQL database; if you delete them, the program stops working. Delete every other user you don't recognize, together with their home directory (and so their SSH keys):

   userdel -r <USER>

   • userdel – deletes a user from the system (works on both Ubuntu 24.04 and Debian 13).
   • -r – also deletes their home directory, including ~/.ssh/authorized_keys.
   • <USER> – replace this with the name from the first column of the output, without the angle brackets, for example userdel -r jan.

   If userdel replies user jan is currently used by process …, the user is currently signed in. End their processes with pkill -KILL -u jan (-u selects the user's processes, -KILL ends them immediately) and run userdel again.

   Don't delete a user you know and want to keep, but go through their /home/<USER>/.ssh/authorized_keys file the same way as for root.

5. Check who is allowed to use sudo (administrator rights):

   getent group sudo

   • getent group sudo – prints the sudo group. After the last colon are the users who can run commands as root. Delete unknown users as in the previous step.

6. In the Files tab, click Change credentials, enter the new root password and click Verify and save.

7. Change the passwords of the databases and applications running on the VPS.

Game server and Discord bot#

• Minecraft: in the Server properties tab, change the RCON password and go through the operators and permission groups (LuckPerms).
• FiveM: in txAdmin, remove administrators you don't know and change the passwords.
• Discord bot: generate a new token in the Discord Developer Portal and save it in the file with your variables (bot token).
• All servers: in the Database tab, check the new passwords and update them in your plugin or script configuration.

Verification#

• Sharing: the member sees the service in My services with the shared tag, and on your side their status is active.
• Transfer: the service has disappeared from your list and the new owner sees it without the shared tag.

Troubleshooting#

The invited person sees Invitation not found#

They signed in with an account using a different email address than the one you sent the invitation to, or you removed the invitation in the meantime. Send a new invitation to the address of their account.

A service can be shared with at most 10 accounts.#

At most 10 other accounts can have access to one service. Remove someone who no longer needs access.

The account password doesn't match. during a transfer#

You entered the wrong password for your account. After five failed attempts within an hour, you temporarily can't start a transfer (Too many attempts, please try again later.).

The recipient doesn't see the transfer#

Check the new owner's email for typos, and that they signed in with an account using that address and have verified their email. A transfer is valid for 7 days; if it lapsed, start it again.

After a transfer, plugins or scripts using the database don't work#

When a game server is transferred, its database passwords change. Copy the new password from the Database tab into the plugin or script configuration and restart the server.