> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage server subusers

> Add a subuser to a Purpify server, choose their permissions, and remove their access safely.

Add a subuser when another person needs access to your Purpify server. Each subuser signs in with their own account and receives only the permissions you select.

<Warning>
  A subuser with file, console, database, backup, or settings access may be able to read secrets or make destructive changes. Add only people you trust.
</Warning>

## Add a subuser

<Steps>
  <Step title="Open the owned server">
    Sign in to the [game panel](https://panel.purpify.host), open **Servers**, and manage the server from the **Yours** list.
  </Step>

  <Step title="Open Subusers">
    Select the **Subusers** tab. This tab is available to the server owner and accounts with permission to manage subusers.
  </Step>

  <Step title="Enter their account email">
    Use the email address connected to the subuser's Purpify game-panel account. Do not create a shared account.
  </Step>

  <Step title="Choose the minimum permissions">
    Select only the actions required for their role. Review file, console, power, backup, database, and settings access separately when those choices are shown.
  </Step>

  <Step title="Send or save the invitation">
    Complete the invitation, then ask the subuser to sign in with their own account. Shared servers appear under **Servers** > **Others**.
  </Step>
</Steps>

## Choose permissions

| Responsibility                   | Access normally required                   | Main risk                                                |
| -------------------------------- | ------------------------------------------ | -------------------------------------------------------- |
| Restart the server               | View server and use normal power controls  | Interrupting active players or an update                 |
| Moderate players                 | View and send console commands             | Granting operator access or running destructive commands |
| Manage plugins, mods, or add-ons | View and change files, plus restart access | Reading secrets or breaking startup                      |
| Restore backups                  | View and restore backups                   | Replacing newer world and player data                    |
| Manage integrations              | Files and database details when required   | Exposing passwords, tokens, or saved data                |

Avoid granting subuser-management or destructive settings permissions unless the person is expected to manage other users or reset the server.

## Remove a subuser safely

<Steps>
  <Step title="Remove the user">
    Open the **Subusers** tab and remove the subuser. Confirm that the server no longer appears in their shared-server list.
  </Step>

  <Step title="Rotate exposed secrets">
    Change database passwords, plugin tokens, webhook URLs, API keys, or other secrets the former subuser could read. Do not change unrelated credentials without a reason.
  </Step>

  <Step title="Review recent changes">
    Check the console, files, server settings, and other subusers for unexpected changes. Restore a known-good backup if server data was altered without approval.
  </Step>
</Steps>

<Note>
  Removing shared access does not undo console commands, file changes, downloads, or secrets the user previously viewed.
</Note>