Team & roles
Bring the whole team in — safely. Invite teammates as Admin, Editor, or Viewer so everyone has the right access, with guardrails that stop you from locking yourself out.
Three roles
Admin, Editor, and Viewer for the right level of access.
Invite by email
Send a secure invite link in seconds.
Sensible guardrails
You can't remove the last admin or lock yourself out.
Live in three steps.
Invite teammates
Send invites by email.
Set their role
Admin, Editor, or Viewer.
Build together
Everyone works in one workspace.
Rolling out access for a six-person team.
Marketing writes, product approves, support reads: most teams are three roles wearing different job titles. Here is the mapping for a real six-person rollout, and the reasoning behind each assignment.
Admins: two, not one
The workspace owner plus one deputy get Admin — full control including billing, team, and destructive settings. Two, so a vacation never locks the workspace; not five, so "who changed this" stays answerable.
Editors do the daily work
The PM and both marketers get Editor: create, edit, publish, and analyze guides — everything except team, billing, and workspace-level danger zones.
Viewers read the numbers
Support and the analyst get Viewer: full read access to guides, Reports, and Responses, no edit surface. Perfect for "can I see what shipped" without "oops, I unpublished it".
Invite and forget
Invites go by email from Settings; each lands directly in the right role. The guardrails handle the rest — including refusing to demote or remove the last Admin.
What to expect: Everyone can do their job and nobody can do everyone's. The last-admin guardrail means no workspace ever strands itself — the lockout story ends before it starts, which is exactly the kind of edge case a roles system exists to delete.
When not to use team & roles.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
One shared login for the team
Sharing an account voids the model: no audit trail, shared don't-show-again state, one password for everything. Seats exist so access can be granted — and revoked — per person.
Everyone as Admin "to keep it simple"
Five Admins is not simple; it is five people who can delete end-user data. Default new teammates to Editor and promote deliberately — upgrading later is one click.
Access control inside guides
Roles govern your team's dashboard access, not which end-users see which guides. That job belongs to audiences and segments.
What can each role do?
Admins: everything, including team, billing, integrations, and data management. Editors: build, edit, publish, and analyze guides. Viewers: read-only across guides, Reports, and Responses. The split maps to "runs the workspace / does the work / reads the results".
Can I lock myself out?
No — the guardrails refuse to remove or demote the last Admin. Workspaces cannot orphan themselves, which is exactly the failure mode role systems usually discover the hard way.
How do invites work?
By email from Settings: pick the role, send, and the teammate lands in the workspace with that access. Roles can be changed later; departures are one removal, not a password rotation.
Do Viewers see user responses?
Yes — Viewer is full read access, including Responses. If someone should not see user-submitted data, they should not be in the workspace; there is no half-Viewer, deliberately.
Is there an audit trail of who changed what?
Team activity is visible in your workspace notifications — guide published, teammate joined, settings changed — with per-category email and in-app toggles so admins hear about the events they care about. Combined with per-person seats, "who shipped that banner" has an answer.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.