Teams and permissions
Last updated:Nov 8, 2026
Team members share the team owner's environments and wallet, and each member's team role decides what they can do.
Note
Team invites are not open yet: clicking Invite member on the Team page shows "Sign-up through team invitations is not open right now", so new members can't join a team for now.
Roles
Teams have three preset roles, Admin, Manager and Member, shown in English in every interface language.
| Role | Data they see | Main things they can do |
|---|---|---|
| Admin | All data | Team management, top-ups and purchases, migrating environments, editing environment profiles, and exporting, sharing and importing backups |
| Manager | Assigned groups only | Create, edit and delete environments, manage proxies and groups, restore and delete backups, view billing |
| Member | Assigned groups only | Start, stop and operate environments, view and create backups, use automation and machine tokens |
Preset roles can't be deleted, but you can change their permissions on the Roles & permissions tab, and you can create custom roles. Ticking a permission also ticks the permissions it depends on.
A member never gets more than the team owner has. Someone who isn't the owner can't grant more than they have themselves, and can't change their own role.
Access by group
Managers and Members only see environments in the groups assigned to them. On the Groups and tags page, click Assign on a group's row to choose who can see it. Making someone the group's owner does not by itself let them see it.
Without permission
- Buttons on a page are hidden in the web console, and greyed out in the desktop app with the tooltip "You do not have permission to do this."
- Pages you can't open are greyed out in the sidebar.
- Opening such a page directly shows No access.
Some permissions exist only in the desktop app, such as screen recording, follow mode, desktop automation tasks and node operations; the role editor marks them Desktop only.
Machine tokens for automation are also limited to the issuer's own permissions; see Automation overview.
