Summary and recommendation
Typeform user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Typeform uses a flat, workspace-level role model with three fixed roles: Admin, Editor, and Viewer.
There are no custom roles and no per-form or per-folder permission sets - access is all-or-nothing at the workspace level.
Admins hold full control over members, billing, and content;
Editors can create and manage their own forms;
Viewers can only read.
SCIM provisioning is available, but only on the Enterprise plan and only after SSO is fully configured.
For every app below Enterprise tier, user lifecycle is managed entirely through the Members UI at Account avatar → Workspace Settings → Members.
Quick facts
| Admin console path | Account avatar (top-right) → Workspace Settings → Members |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise/Growth Custom |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full workspace control: invite/remove members, change roles, manage billing, create/edit/delete all forms, view all responses, manage integrations and workspace settings. | Cannot exceed seat limits imposed by the current plan without upgrading. | Available on all paid plans; workspace owner is Admin by default. | Counts as a billable seat on plans with per-seat pricing (e.g., Growth Essentials at $166/user/month). | Only Admins can manage billing and remove other members; there must always be at least one Admin in a workspace. |
| Editor | Create, edit, duplicate, and delete own forms; view and export responses for own forms; collaborate on shared workspaces. | Cannot manage members, change roles, access billing, or edit forms owned by others unless explicitly shared. | Available on Plus plan and above for multiple members; Basic plan is single-user. | Counts as a billable seat on per-seat plans. | On the Business plan, the number of included Editor seats is capped; additional seats may require upgrade. |
| Viewer | View forms and responses within the workspace; cannot create or edit forms. | Cannot create, edit, or delete forms; cannot manage members or billing. | Availability of Viewer role depends on plan; not explicitly documented as available on all tiers - verify against current plan details. | Viewer seat billing treatment is not explicitly documented in current official help docs; confirm with Typeform support before provisioning. |
Permission model
- Model type: role-based
- Description: Typeform uses a fixed set of workspace-level roles (Admin, Editor, Viewer). Permissions are assigned per role and apply across the workspace. There is no object-level or form-level permission granularity beyond workspace membership.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level only; no per-form or per-folder custom permission sets documented.
How to add users
- Navigate to your workspace in Typeform.
- Click your account avatar or workspace name to open Workspace Settings.
- Select the 'Members' tab.
- Click 'Invite members' (or 'Add members').
- Enter the email address(es) of the person(s) to invite.
- Select the role to assign (Admin or Editor).
- Click 'Send invite'. The invitee receives an email invitation and must accept to join the workspace.
Required fields: Email address of invitee, Role selection (Admin or Editor)
Watch out for:
- Invitees must accept the email invitation before they appear as active members.
- The number of members you can invite is capped by your plan's seat limit; inviting beyond the limit requires a plan upgrade.
- Basic plan is single-user and does not support additional members.
- Pending invitations consume a seat on some plans - verify current behavior with Typeform billing documentation.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise (requires SSO as prerequisite; SCIM provisioning supported via Okta and Microsoft Entra ID) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Typeform's official help documentation describes removing (deleting) a member from a workspace. The member loses access to the workspace immediately upon removal. There is no documented 'deactivate' state distinct from removal; removal is the supported offboarding action.
- Navigate to Workspace Settings → Members.
- Locate the member to remove.
- Click the options menu (three dots or similar) next to the member's name.
- Select 'Remove from workspace' (exact label may vary).
- Confirm the removal when prompted.
| Data impact | Behavior |
|---|---|
| Owned records | Forms and responses owned by the removed member remain in the workspace and are accessible to Admins. Typeform's help documentation states that content is not deleted when a member is removed. |
| Shared content | Shared forms and workspace content remain intact and accessible to remaining members. |
| Integrations | Integrations configured by the removed member may require re-authentication or reassignment by an Admin; specific behavior is not fully documented in official help docs. |
| License freed | Removing a member frees the seat, making it available for a new invite within the plan's seat limit. |
Watch out for:
- Removing a member does not delete their forms or response data; an Admin must manually reassign or delete that content if needed.
- If the removed member was the sole Admin, another member must be promoted to Admin first.
- SCIM-provisioned users removed via the IdP are deprovisioned automatically on Enterprise plans; manual removal is separate from IdP-driven deprovisioning.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Core plan seat (Basic/Plus/Business) | Access to form creation, response collection, and workspace collaboration features per plan tier. Basic is single-user; Plus and Business include multiple seats. | Basic ~$25–29/mo, Plus ~$55–59/mo, Business ~$99/mo (billed annually; prices vary by billing cycle) |
| Growth plan seat (Essentials/Pro) | Advanced features including higher response limits, priority support, and additional integrations. Per-user pricing model. | Growth Essentials ~$166/user/month, Growth Pro ~$291/user/month (billed annually) |
| Enterprise seat | SSO, SCIM provisioning, advanced security, dedicated support, custom response limits. | Custom pricing; contact Typeform sales |
- Where to check usage: Account avatar → Workspace Settings → Members (shows current member count and seat usage); billing details under Account → Billing.
- How to identify unused seats: No automated 'last active' or login-date column is documented in the Members UI. Admins must manually review member activity or cross-reference with IdP logs (for SSO/SCIM accounts) to identify inactive seats.
- Billing notes: Seat counts and included members vary significantly by plan. Basic plan is single-user. Upgrading mid-cycle is prorated per Typeform's standard billing terms. Growth plans are per-user and can become expensive at scale. Pending invitations may count against seat limits - confirm with current Typeform billing documentation.
The cost of manual management
Every app on a non-Enterprise plan carries the full weight of manual provisioning: invitations sent one at a time, no automated deprovisioning, and no last-active or login-date column in the Members UI to surface idle seats. Admins must cross-reference IdP logs or conduct periodic manual reviews to identify unused seats.
Pending invitations may count against seat limits depending on plan - a detail Typeform's public documentation does not resolve definitively. The Basic plan is single-user and cannot add teammates at all; multi-member collaboration requires Plus or higher.
Growth plan pricing is per-user and scales steeply. Without a reliable way to audit seat activity from the admin console, unused seats on Growth Essentials ($166/user/month) or Growth Pro ($291/user/month) can accumulate cost silently.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual management is the only path for every app on Basic, Plus, or Business plans. It is workable for small, stable teams where member turnover is low and seat counts are easy to track by eye.
The absence of granular permissions is a harder constraint: if your team needs to share specific forms with contractors or external reviewers without exposing the full workspace, the current role model has no solution short of creating a separate workspace.
Enterprise with SSO is the prerequisite for SCIM. If your organization already runs Okta or Microsoft Entra ID and needs automated provisioning and deprovisioning at scale, the Enterprise tier unlocks that path. Google Workspace and OneLogin are not supported as SCIM IdPs per available documentation.
Bottom line
Typeform's manual user management is straightforward for small teams but shows its limits quickly as headcount or turnover grows. The flat workspace-role model means every app either gets full Editor access or nothing, and there is no admin-facing activity data to help reclaim unused seats.
Teams that need automated lifecycle management must be on Enterprise with SSO already in place - there is no middle-ground option between fully manual and full SCIM.
Automate Typeform workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
