Team management
Reference for Settings > Team: members, roles and their permissions, and auto-join by email domain.
Settings > Team (/settings/team) is where you invite colleagues to a project and decide what each of them can do. Roles are sets of permissions: give each person the role that matches what they build, publish or configure.
Members
The Members tab lists everyone in the project with their status and role. To invite a new member, type their email in the invite field, pick their initial role next to it, and click Invite: the invitation arrives by email. From the list, change a member's role with their role picker, or remove their access.
There is no limit on the number of team members: invite as many people as you need, on every plan.

Auto-join
With Auto-Join on, anyone with an email on your company domain can join the project on their own, with the Viewer role. Convenient for visibility. It is also why a colleague may "already have an account" but no rights: an Admin changes their role in the Members tab.
Roles and permissions
The Roles tab lists the roles of the project and the permissions of each one.


Default roles
Admin, Contributor, Editor and Viewer come with every project, and they cannot be edited. Admin has full access over every area of the project, including members, roles and billing. Contributor has access to everything except the project settings. Editor is limited to editing experiences. Viewer is limited to experience analytics, without changing anything.
Custom roles
Click New role to create a role with exactly the permissions a group needs, for example a role that builds experiences but cannot publish them. Custom roles are listed under the default ones.
Publishing is a permission
Building an experience and publishing it are two separate permissions, and not every editing role has the second one. If someone can build but cannot publish, check their role in the Roles tab. See Roles and permissions.
Permissions beyond experiences
Some settings need their own permission: reading the snippet in Installation, seeing billing, or connecting an AI assistant through MCP, which requires the same permission as the Integrations settings. An assistant connected with your account can never do more than your role allows.
Multi-factor authentication for the team
In Settings > Security, an Admin can turn on Enforce multi-factor authentication (MFA) for all members. Each member sets up their own MFA in My account.
Who can change this
Inviting members, changing roles and editing permissions need Admin.
Verify
Ask the new member to log in: they see the project, and the actions they need (build, publish, open Installation) are available to them.
Go further
Next page: Troubleshooting
Last updated

