Roles and inviting your team
Invite people by email under Settings, Members; each member has a role per workspace, which decides what they see and can do.
People join a workspace by invitation. Owners and Admins invite from Settings, Members (the workspace that is active in the header). Each member has one role in each workspace they belong to.
Step by step: invite someone
- Make the right workspace active in the header's switcher.
- Open Settings, Members.
- Under Invite someone, type the Email and pick the Role, then click Invite.
- "We e-mailed the invitation. You can also share this link:" The link is shown too. If the email could not be sent, the page says "We could not send the e-mail, so share this link yourself:".
- The invitation appears under Pending invitations with "{role} · expires {date}". It is valid for 7 days; Resend sends a fresh one ("A new invitation is on its way.").
What the invited person sees is described in Accepting an invitation.
The roles
- Owner: "Full access, including billing and ownership." Only Owners archive or delete a workspace; the founding Owners can delete the whole account.
- Admin: "Full access to every area of this workspace." Settings, accounts, members, approvals, brand.
- Editor: "Creates and publishes content, replies in the Inbox."
- Reviewer: "Approves content and replies in the Inbox."
- Viewer: "Read-only across the workspace."
- Agent (inbox only): "Inbox only: reads, replies, adds notes and blocks spam." An Agent also sees Team, Bookings, Inbox bots, Accounts (to add their own mailbox), Help and Your account.
Owners and Admins can also fine-tune a member's access under Access on the Members page: give an Editor, Reviewer, Viewer or Agent an extra task, or take one of their role's tasks away.
Good to know
- Roles are per workspace: the same person can be an Editor for one brand and a Viewer for another.
- Your plan sets how many members each workspace can have; the Members page shows "{used} of {limit} seats used", and pending invitations count. See /pricing.
- Removing a member asks "Remove {name} from this workspace? Anything assigned to them is handed back to the team."
- API keys belong to the member who created them; if that member stops being an active Owner or Admin of the workspace, their keys stop working.
Related
Checked against the product on Sep 23, 2026