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 two halves: an Invite a teammate form and a Current team list.
Membership is per store
storeIdin 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 teammateto add them to the workspace. On success the form confirms “Team member added to this workspace.”
The roles
When inviting or editing a member, you choose from five roles. The labels describe the kind of collaborator each is meant for:
- admin— broad management access, including sensitive settings. Use sparingly.
- marketer— for the people running recovery, journeys, and campaigns.
- support— for agents working the inbox and conversations. This is the default for new invites.
- analyst— for people who live in analytics and reporting.
- developer— for engineering collaborators working on integrations and the API.
Owners, admins, and credentials
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.
- Remove them — click Remove to revoke their access to this store. They keep no residual access here afterward.
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.
Related
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.