Workspaces, team members and permissions
Know what each role can do and why a feature may be missing from your navigation.
2 min read
Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.
A workspace is the data boundary
Use the workspace switcher before working on a campaign or report. Membership in one workspace does not automatically give access to another. A person’s role can also differ between workspaces. Keep client data in its intended workspace rather than sharing one workspace to avoid a limit.
The available roles
- Owner: manages workspace settings and, for a direct platform-billed workspace, billing. Owners can invite team members and manage campaigns.
- Admin: manages campaigns and team operations and can manage supported branding. Admin does not mean platform administrator or an automatic right to change owner-only settings/billing.
- Member: manages campaigns but does not receive owner-only workspace configuration controls.
- Analyst: has analytics access but is not a campaign-browsing or campaign-editing role.
- Viewer: can view campaigns and analytics without campaign-management permissions.
Invite a teammate
- 1The workspace owner opens Team and invites the person with the intended role.
- 2Use the person’s correct account email. The invitee opens the invitation and signs in with the intended account.
- 3They verify their email if required and accept the invitation before it expires.
- 4The invitee selects the new workspace and checks the expected access. If it is wrong, the owner reviews the membership role rather than sharing login credentials.
Permissions and plans both matter
A role permits an action, while the plan permits a capability. You need both. For example, a campaign manager may still be unable to use an offer-card composition when the plan disables it. A platform administrator is a separate identity, not a workspace role or a blanket subscription bypass.