Teams & permissions

Give a teammate exactly the access they need on a shared server — not your whole account.

How teams work

A team has an owner (whoever created it — billing is always against the owner's plan, never split) and members, invited by email. Servers can be added directly under the team rather than a personal account, so they're shared from the moment they're created.

Roles

RoleAccess
OwnerFull control — billing, membership, all server access, can't be removed
AdminCan manage members and permissions, same server access as owner
MemberNo access to anything by default — each capability must be explicitly granted

Per-action permissions

A plain member starts with nothing and is granted individual capabilities as needed — for example terminal access, files (SFTP) access, or backups management can each be turned on independently per server. This means you can give someone SSH terminal access to debug an incident without also handing them the ability to reconfigure that server's backup destination.

SSH credentials themselves are the one thing that stays owner/admin-only regardless of granted permissions — the same trust tier as full terminal access, deliberately not delegable to a plain member.