Invite subusers through Pterodactyl and grant only the server permissions each teammate needs.
Plan permissions first
Pterodactyl separates console, power, files, SFTP, backups, schedules, databases, allocations, startup, settings, and user permissions. Start with no permissions and add only those required for the teammate’s role. Avoid granting user.create, settings.reinstall, startup.update, or destructive file and backup permissions unless essential.
Send an invitation
- Open the intended server, then select Users.
- Choose New User and enter the email address associated with their panel account.
- Select the exact read, create, update, and delete permissions required.
- Send the invitation and ask the user to sign in with their own account.
Test and audit access
Ask the subuser to confirm they can perform the intended task without seeing unrelated controls. Review server Activity after important changes and remove the subuser immediately when access is no longer required. Never share your own password or two-factor authentication codes.
Your feedback helps us improve our guides.
