Teams

Let a customer invite colleagues into its account with a role (Owner, Member, Billing, Read-only, Notifications only), and how staff manage teams.

A customer account (level User) can have a team: other people who sign in with their own login and work inside the account with a role. One login can be a member of several accounts, also of accounts under different resellers. Resellers and administrators do not have teams; they act on customers through their own level and signing in as an account.

Invitations are sent by mail, so mail must be set up under System › Settings › Mail first.

Roles#

May Owner Member Billing Read-only Notifications only
Open the account in the panel yes yes yes yes no
See servers, their tabs, usage, tasks and networking yes yes yes yes –
Act on servers (power, consoles, reinstall, rescue, ISOs, backups, snapshots, firewall, reverse DNS, disks, settings, port forwards…), names, notes yes yes no no –
Read root and rescue passwords yes yes no no –
Create and delete servers (when the account may) yes yes no no –
Change the account's SSH keys and recipes yes yes no no –
Own API keys for the account every scope the account has every scope the account has read scopes read scopes –
The account's webhooks yes no no no –
The team (invite, change roles, remove) yes no no no –

Inside the account the account's own rules still apply: its plan's customer switches, its limits and its reseller's suspension. The account's own login is always the Owner; it is not listed as a removable member.

A role that only reads sees greyed controls with "Your role on this account (Read-only) does not allow this." Usage charts stay readable for Billing and Read-only.

Members get copies of the account's mails by role: server, backup and snapshot mails to Owner, Member and Notifications only; usage (traffic) and account suspension mails to Owner, Billing and Notifications only; maintenance notices to everyone. A copy never contains a secret such as a root password.

Inviting a member#

As the customer (or a member with the Owner role):

  1. Go to Team in the sidebar.
  2. Press Invite, type the Email address and choose the Role.
  3. Press Send invitation.

The invitee gets a one-time link valid 7 days. Opening it shows the invitation:

  • A person who already has a login signs in with that address and accepts.
  • A new person types a name and a password; this creates a plain user login (no reseller, no right to create servers) and joins the team at once.

Pending invitations are listed under Invitations waiting with Withdraw. A new invitation to the same address replaces the old one. At most 20 invitations wait per account, and one person sends at most 5 a minute.

An address that belongs to an administrator or reseller cannot be invited ("This address cannot be invited."). The account's own address and existing members are refused too.

Working in another account#

A login that is a member of any account gets an account switcher at the top of the sidebar: the current account and role, Your own account, and every team account. Choosing one opens it.

Inside a team account the member's own settings (profile, appearance, security, sign-ins, notifications, two-factor, passkeys) are closed: "Switch to your own account to change your settings." API keys are open by role: the member sees and revokes only its own keys for that account. Password confirmations ask the member's own password.

Settings › Accounts lists the accounts a login is a member of, with Open and Leave.

Changing roles and removing members#

On Team, change a member's role with the select or press Remove. Removing a member:

  • deletes the membership,
  • revokes the API keys the member made for the account,
  • sends the member's open sessions in the account back to their own account on their next request.

A member never changes its own role, but can always leave.

What staff see#

On a customer's page (Customers › Users, the account) administrators and the account's reseller see a Team panel with the same controls, and for a login a Member of list. A reseller sees only memberships of accounts it manages. Staff with a role need users.edit to change another account's team.

Security rules#

  • The member's own two-factor requirement, suspension, allowed addresses, timeouts and sessions apply. The account's panel allowlist must also match: "Acme may be used only from the addresses it allows, and yours is not one of them."
  • A suspended account, a removed membership, a role changed to Notifications only, or a new email address of the member sends the member back to their own account.
  • Signing in as another account is not possible from inside a team account, and switching accounts is not possible while signed in as another account.
  • Billing-system sign-in links always open the account's own login (the owner), never a member.
  • Audit entries made inside the account are the account's and name the member ("MEMBER for ACCOUNT").

API#

Managed accounts: GET /users/{id}/members, GET|POST /users/{id}/invitations, PATCH|DELETE /users/{id}/members/{member} (scopes users:read, users:write). The key's own account: /team/members and /team/invitations with the scopes team:read and team:write. See the API reference.

Not available#

Custom roles with chosen permissions, per-account notification switches for a member, teams for resellers, and a list of a member's sessions per account.