Summary and recommendation
Userflow 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.
Userflow's team management lives entirely in Settings → Team (https://app.userflow.com/settings/team).
The permission model is a fixed two-role system - Admin and Member - applied at the workspace level.
Like every app that lacks automated provisioning, access changes here require manual Admin intervention for each joiner and leaver, with no bulk or CSV import option documented.
Quick facts
| Admin console path | Settings → Team |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all workspace settings, billing, team member management, and all content (flows, checklists, launchers, surveys). Can invite and remove team members and change roles. | At least one Admin must remain in the workspace; the last Admin cannot be removed or downgraded without first promoting another member. | |||
| Member | Can create, edit, and publish flows and other content. Cannot access billing or manage team members. | Cannot manage billing, invite or remove team members, or change workspace-level settings. |
Permission model
- Model type: role-based
- Description: Userflow uses a two-role model (Admin and Member) applied at the workspace level. All members within a workspace share access to the same content; there is no per-project or per-flow permission scoping documented in official sources.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level only; two fixed roles with no documented granular permission customization.
How to add users
- Navigate to Settings → Team in the Userflow dashboard.
- Click 'Invite team member'.
- Enter the invitee's email address.
- Select the role (Admin or Member).
- Click 'Send invite'. The invitee receives an email invitation to join the workspace.
Required fields: Email address, Role (Admin or Member)
Watch out for:
- Invitees must accept the email invitation before they can access the workspace.
- Pending invitations count toward the seat limit on plans that enforce seat caps.
- No documented bulk/CSV invite option for team members.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Userflow allows admins to remove (delete) a team member from the workspace via Settings → Team. Removed members immediately lose access. No separate 'deactivate' state is documented; removal is the only offboarding action described in official sources.
- Navigate to Settings → Team.
- Locate the team member to remove.
- Click the options menu (⋯) next to their name.
- Select 'Remove from team' and confirm.
| Data impact | Behavior |
|---|---|
| Owned records | Content (flows, checklists, etc.) created by the removed member remains in the workspace and is accessible to remaining team members. |
| Shared content | All workspace content remains intact after a member is removed; no content is deleted. |
| Integrations | Not documented |
| License freed | Removing a team member frees up a seat, which can be reassigned to a new invitee. |
Watch out for:
- The last Admin in a workspace cannot be removed; another member must be promoted to Admin first.
- Removal is immediate with no grace period or deactivation state documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Team member seat | One named user (Admin or Member role) with access to the Userflow workspace. | Seat limits and per-seat pricing vary by plan; Startup and Pro plans include a set number of seats with additional seats available. Enterprise pricing is custom. |
- Where to check usage: Settings → Team (shows current members and pending invitations); Settings → Billing (shows plan and seat usage).
- How to identify unused seats: Review the team member list in Settings → Team for members with no recent activity; Userflow does not document an automated last-login or activity report for team members.
- Billing notes: Plans are billed based on Monthly Active Users (end-users of your product) tracked by Userflow, not solely on team member seat count. Team member seat limits are a secondary constraint. Startup plan starts at $240/mo, Pro at $680/mo, Enterprise is custom-quoted.
The cost of manual management
Without an automated provisioning layer, every app your team uses requires a separate, manual invite-and-remove cycle. In Userflow, that means an Admin must navigate to Settings → Team for every joiner and leaver. Pending invitations count against seat limits even before the invitee accepts, which can silently inflate seat usage on capped plans.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Userflow's two-role model covers most small-team scenarios cleanly, but like every app with a flat permission structure, it breaks down when teams need publishing controls or flow-level access scoping. Admins hold full workspace control - billing, team management, and all content - while Members can create and publish flows but cannot touch workspace settings.
The hard constraint worth planning around: the last Admin cannot be removed or downgraded until another member is promoted first.
Bottom line
Userflow's manual provisioning workflow is straightforward for small, stable teams - invite via Settings → Team, assign Admin or Member, remove when done.
The gaps become operational overhead at scale: no bulk invite, no deactivation state (removal is immediate and permanent), no activity report to identify unused seats, and a flat two-role model that cannot be tightened.
Teams that rotate members frequently or need publishing controls will feel those limits quickly.
Automate Userflow 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.
