Team & roles

The Team tab is where you add collaborators to a store and control what they can do. Find it under Settings → Integrations → Team, or go to /app/<storeId>/settings/team. The page has an Invite a teammate form, a Current team list, and - when any invites are outstanding - a Pending invitations card.

Membership is per store

Team membership and roles apply to the storeId in the URL. Inviting someone to one store does not grant them access to your other stores - invite them to each store you want them to work in.

Inviting a teammate

The invite form takes three fields:

Full name - the person’s display name (e.g. “Jordan Lee”). Required.
Email - their work email. Required. This is the identity they’ll sign in with.
Role - the access level to grant. Defaults to support.

Click Add teammate to send the invitation. On success the form confirms “Invitation sent - they’ll get access to this workspace once they accept.” Access is granted only after they accept the invite email; until then they appear in the Pending invitations card, where you can Revoke an outstanding invite to kill its link. Each invite shows the role it was issued with and its expiry date.

Inviting, step by step

Decide the narrowest role that covers the person’s job - it’s easier to widen access later than to claw it back.
Fill in their name and individual work email (not a shared mailbox, so audit-log actions stay attributable), pick the role, and click Add teammate.
Ask them to accept the invite email - nothing works until they do, and the invite expires if they wait too long.
Once they appear in Current team, fine-tune their per-area access checkboxes if the role default doesn’t fit.

The roles

When inviting or editing a member, you choose from five roles. Each role grants a default set of capabilities, which you can then adjust per member with the access checkboxes:

admin - full access to every area, including sensitive settings. Use sparingly.
marketer - recovery and campaigns, growth tools, the widget, analytics, catalog, and training. For the people running recovery, journeys, and broadcasts.
support - the inbox, analytics, catalog, and training. For agents working conversations. This is the default for new invites.
analyst - analytics only. For people who live in reporting.
developer - integrations, catalog, settings, the widget, and recovery. For engineering collaborators working on integrations and the API.

Owners, admins, and credentials

Some actions need elevated access beyond these collaborator roles. Viewing and rotating widget credentials on the Workspace tab is limited to owners and admins; other roles see a placeholder instead of the key. Grant admin only to people who genuinely need it.

Managing the current team

The Current team card lists every member of the workspace with their name, email, and current role. For each person you can:

Update their role - pick a new role from the dropdown next to their name and click Update. The change applies to this store immediately.
Tune their access - under each member (except owners and admins, who always have full access) sits an Access panel of per-area checkboxes seeded from their role’s defaults. Tick or untick areas and click Save access to grant or revoke individual capabilities beyond what the role provides - both the sidebar and the per-page guards honor these overrides.
Remove them - click Remove and confirm to revoke their access to this store. This removes membership-based access. Review separate API and integration credentials during offboarding.

If no one has been invited yet, the list shows “No team members yet. Invite teammates to collaborate on this store.”

Good practices

Assign the narrowest role that lets someone do their job - a support agent rarely needs admin.
Review the member list periodically and remove people who have left or changed teams.
Use real, individual emails rather than a shared mailbox so actions are attributable per person.

Support agents spend most of their time in the inbox and use canned replies. For programmatic access instead of human seats, see API keys. Account-level protections are covered in Security.

Offboard access in separate layers

Remove the member from this store, then review every store they could access. Membership removal does not recover exported files or prove that separately held API and integration credentials were revoked. Rotate shared credentials where needed and use the API key rotation procedure. For suspected account compromise, follow account security and contact support with timestamps rather than secrets.