Sub-users share one server with other RestoreCord accounts, without handing over the owner login. Access is scoped per server and per permission, and it never includes sub-user management itself. Find it under Dashboard → Servers → Manage → Sub-Users.
Sub-users require a Premium plan or higher. On Free the tab is visible but locked.
The sub-users card
Each teammate appears with their avatar, username and the permissions they hold. The ⋮ menu on a row opens Edit to change that set, or Remove to revoke access.
Manage Sub-Users
Share server access with other users.
Removing a sub-user cuts their access to this server immediately. It does not touch their RestoreCord account or any other server they belong to.
Inviting someone
Invites go to an email address that already has a RestoreCord account — there is no signup-by-invite. Pick at least one permission, then send; the teammate stays in a pending state until they accept.
Add Sub-User
Invite a RestoreCord user by their email address and assign permissions.
The dashboard refuses the invite when:
- Message
- No RestoreCord account found with this email
- Meaning
- They need to register first, or you have the wrong address
- Message
- This user is already a sub-user
- Meaning
- Edit their existing row instead of re-inviting
- Message
- You cannot add yourself as a sub-user
- Meaning
- You already have owner access
- Message
- Please select at least one permission
- Meaning
- An invite with no permissions would grant nothing
| Message | Meaning |
|---|---|
| No RestoreCord account found with this email | They need to register first, or you have the wrong address |
| This user is already a sub-user | Edit their existing row instead of re-inviting |
| You cannot add yourself as a sub-user | You already have owner access |
| Please select at least one permission | An invite with no permissions would grant nothing |
Permissions
Grant the smallest set that lets the teammate do their job. Two permissions imply another, so you never need to tick both.
- Permission
- Manage Settings
- Grants
- Everything in server settings except sub-user management
- Implies
- —
- Permission
- View Members
- Grants
- Username, avatar, country and verification date
- Implies
- —
- Permission
- View Member Details
- Grants
- IP, email, location and device
- Implies
- View Members
- Permission
- Pull Members
- Grants
- Starting member migrations and recovery pulls
- Implies
- —
- Permission
- Create Backups
- Grants
- Creating and viewing backups, but not restoring or deleting them
- Implies
- —
- Permission
- Manage Backups
- Grants
- Viewing, editing, deleting and restoring backups
- Implies
- Create Backups
- Permission
- Manage Firewall
- Grants
- Firewall rules and passwords
- Implies
- —
| Permission | Grants | Implies |
|---|---|---|
| Manage Settings | Everything in server settings except sub-user management | — |
| View Members | Username, avatar, country and verification date | — |
| View Member Details | IP, email, location and device | View Members |
| Pull Members | Starting member migrations and recovery pulls | — |
| Create Backups | Creating and viewing backups, but not restoring or deleting them | — |
| Manage Backups | Viewing, editing, deleting and restoring backups | Create Backups |
| Manage Firewall | Firewall rules and passwords | — |
The chips on a sub-user's row label the two backup permissions Create Snapshots and Manage Snapshots, while the picker calls them Create Backups and Manage Backups. They are the same two permissions.
View Member Details exposes IP addresses and emails, and Manage Backups can restore over a live server. Treat both as trusted-staff permissions.