Skip to main content

Team member roles

Every team member has one of four roles in a project. Each role includes everything the role below it can do.
  • Viewer: Read-only. Viewers can view and preview all content, settings and analytics, but can’t create, edit or publish anything.
  • Editor: The builders. Editors can create and edit everything: content, themes, attributes, events, segments, environments, integrations and webhooks. They can publish only to the environments you allow when you invite them (see Limiting where an Editor can publish). No access to team management or billing.
  • Admin: Everything an Editor can do, plus publishing to any environment, managing team members, SSO and project settings, and viewing the audit log and the billing plan.
  • Owner: The main owner and contact of the project. The only role that can change the plan or transfer ownership. Every project has exactly one Owner.
Roles are per project. Someone can be an Admin in one project and a Viewer in another.

Add a team member

Owners and Admins can add team members. Here’s how:
  1. Go to Settings -> Team
  2. Click Invite team member
  3. Enter the name, email and role of the team member you want to add
  4. If the role is Editor, check the environments they’re allowed to publish to
  5. Click Send invite
The team member will receive an email with a button they need to click to accept the invite. This applies even if the team member already has a Usertour account. Invite a team member and, for an Editor, choose where they can publish
Each plan includes a number of team seats. Pending invites count towards the limit. When the project is full, the invite dialog asks you to upgrade before you can send another invite.

Limiting where an Editor can publish

Editors can build anything, but they only ship to the environments checked under Can publish to these environments. This lets a contractor or a new teammate prepare flows on staging without being able to touch production. Leave every environment unchecked for an Editor who prepares content but never publishes it. When an Editor opens the Publish dialog on a flow, only their allowed environments are listed. Publishing to any other environment is refused by the server, even through the API. A couple of details worth knowing:
  • Admins and Owners always publish everywhere. The checkboxes only appear for the Editor role.
  • New environments are not added to an Editor’s list automatically. When you create an environment, edit the role of any Editor who should be able to publish there.
  • Deleting an environment removes it from every Editor’s list.
To change an Editor’s environments later, use Change role on that member and update the checkboxes.

Remove a team member

Owners and Admins can remove team members. Here’s how:
  1. Go to Settings -> Team
  2. Click on the 3-dot menu next to the team member
  3. Click Remove member
The member loses access to the project immediately. You can re-invite them later. The Owner can’t be removed; transfer ownership first. Remove a team member

Change a team member’s role

Owners and Admins can change the role of team members. Here’s how:
  1. Go to Settings -> Team
  2. Click on the 3-dot menu next to the team member
  3. Click Change role and select the role. For an Editor, also update the environments they can publish to
Change a team member's role

Make another team member the Owner

Only the Owner can transfer ownership. Here’s how:
  1. Go to Settings -> Team
  2. Click on the 3-dot menu next to the team member
  3. Click Transfer ownership
The other member becomes the Owner and you become an Admin. This can’t be undone from your side: only the new Owner can transfer it back. Make another team member the Owner