Who this is for: Anyone trying to figure out who can do what in AnswerPath, or deciding what role to assign a new teammate.
Time: 2 minutes.
Explains the three roles in AnswerPath — Owner, Admin, and Member — and what each one can do.
The person who created the organization, plus anyone they've promoted. Every organization has at least one Owner.
Owners can do everything:
Manage billing (upgrade, downgrade, cancel, change payment method)
Invite and remove teammates
Change anyone's role, including promoting another Owner
Approve or reject pending members
Change organization settings, branding, and auto-approved domains
Delete the organization entirely
A trusted teammate who helps manage the team but isn't responsible for billing.
Admins can:
Invite teammates (as Member or Admin)
Revoke pending invitations
Approve or reject pending members
Manage organization branding and auto-approved domains
Use every day-to-day feature (Context Hub, Answer Bank, Projects, QuickTurn)
Admins cannot:
Change billing or the plan
Delete the organization
Remove an Owner
The default role for most teammates. Members can use AnswerPath to do work.
Members can:
Upload and manage documents in the Context Hub
Ask questions and save answers
Create and work inside Projects
Use QuickTurn — upload questionnaires, review drafts, assign questions
Edit their own profile and password
Members cannot:
Invite or remove teammates
Approve pending members
Change organization or billing settings
Change other people's roles
Situation | Assign |
|---|---|
New hire on the response team | Member |
Team lead who will help onboard others | Admin |
The person who signs the AnswerPath invoice | Owner |
A rotating contractor or short-term collaborator | Member |
Someone who will manage your custom domain allowlist | Admin |
When in doubt, pick Member. It's easy to promote later, and the smaller the group of people who can change org-wide settings, the fewer surprises you'll have.
When you invite a teammate, you pick Member or Admin on the invitation form (see Invite teammates).
Ownership transfer and role changes for existing teammates are handled by Owners on the Organization settings page.
Have at least two Owners. If the only Owner loses access to their email, the organization can get stuck. A second Owner is cheap insurance.
Don't make everyone an Admin. Admins can remove your invitations and approve strangers. Reserve the role for people who actually manage the team.
Never share logins. If you want to give someone else access, invite them with their own account. Shared credentials make audits, offboarding, and role changes messy.
