Skip to content

Members and access

An org is your team: its members, its nodes, and their servers. You can be in several orgs, and switch between them at the top of the sidebar. Billing is per org.

Role Can
Owner Everything, including billing, roles, and deleting the org. An org always has at least one.
Admin Everything on every node and server: create and delete servers, link nodes, invite people, set alerts. Not billing or roles.
Member Only what they’ve been given on each server (below).

Owners change roles on Settings → Members. Each change asks first and says what it means; giving up your own owner role is one you can’t undo yourself, since another owner has to give it back. Anyone can leave an org, except its last owner.

On Settings → Members, under Invite someone, enter their email and a role. They get an email with a link, valid for 7 days, that works only when signed in with that address. Pending invitations are listed there to cancel.

Members see only the servers they’ve been given access to. On a server’s Access tab, admins tick what each member may do there:

Permission Lets them
See the console Watch its console
Send console commands Type commands into it (includes watching)
Start and stop Start, stop, restart, and kill it
See files Browse and download its files
Change files Edit, upload, delete, and install add-ons, and change Workshop items for games that list them in a file
Use SFTP Make temporary SFTP logins
Backups Back it up and restore it
Schedules Make and run schedules
Startup settings Change its game settings and Workshop items (for games that take them in a setting)
Reinstall Reinstall it
See databases See its databases and their connection details, and run read-only queries
Change databases Make, change, and delete its databases, and see and change their passwords
Manage players On a Minecraft server’s Players tab: see who’s online, and whitelist, op, ban, unban, and kick, without the console or the files

Members who could send console commands before Manage players existed were given it too, since they could already do all of it from the console.

Creating and deleting servers, backup destinations, and node settings are for admins and owners.

Some actions are signed with a passkey and checked by the node itself: restoring a backup over a server, wiping it, changing what it runs. An owner’s passkey is trusted by the node from the start. For a member to do one of these on a node, an owner trusts their passkey there too, for just the actions they choose, on the node’s Settings → Trusted passkeys. The node checks every signature itself, so nobody, Raptor included, can add trust without an owner’s passkey. More in How Raptor protects you.

Admins and owners can rename the org and give it a logo on its Settings (PNG, JPEG, GIF, or WebP, cropped square); members see it in the org switcher. Without one, it shows the org’s initials.

Owners can Delete organization from the org’s Settings, once it has no nodes. Its members are removed, and its activity log is kept.

© 2026 Xena Studios. Pterodactyl is a trademark of its owners; Raptor isn't affiliated with it.