Summary and recommendation
Whimsical 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.
Whimsical provides workspace-level role-based access control with four fixed roles: Owner, Admin, Member, and Viewer.
There are no custom roles available on any plan.
Viewer seats are free and unlimited across all plans;
every app that bills per editor seat benefits from this distinction, since read-only stakeholders never consume a paid license.
Quick facts
| Admin console path | Workspace Settings → Members |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Organization |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full workspace control: manage billing, delete workspace, manage all members and settings, edit all content. | Cannot be removed by Admins; only one Owner per workspace. | All plans | Counts as a paid editor seat on Pro and Organization plans. | Ownership transfer must be initiated by the current Owner. |
| Admin | Invite and remove members, manage roles up to Admin level, access workspace settings, edit all content. | Cannot manage billing or delete the workspace; cannot change Owner role. | All plans | Counts as a paid editor seat on Pro and Organization plans. | |
| Member | Create, edit, and share files within the workspace; collaborate on shared content. | Cannot manage other members or access workspace billing/settings. | All plans | Counts as a paid editor seat on Pro and Organization plans. | |
| Viewer | View and comment on files shared with them; cannot edit content. | Cannot create or edit files; cannot access workspace settings. | All plans | Free on all plans; unlimited viewers allowed. | Viewers do not consume a paid seat, but they must be explicitly invited or have access granted per file/folder. |
Permission model
- Model type: role-based
- Description: Whimsical uses fixed workspace-level roles (Owner, Admin, Member, Viewer). File and folder sharing can be set to specific people, anyone with the link, or workspace members. No custom roles are available.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level roles with per-file/folder sharing controls (view or edit access per item).
How to add users
- Navigate to Workspace Settings → Members.
- Click 'Invite members'.
- Enter the email address(es) of the person(s) to invite.
- Select the role to assign (Admin, Member, or Viewer).
- Click 'Send invite'. The invitee receives an email to accept and join the workspace.
Required fields: Email address, Role selection
Watch out for:
- Inviting a new editor on a paid plan immediately increases the seat count and billing.
- Pending invitations that are not accepted still occupy a seat on some plan tiers until revoked.
- Viewers do not require a paid seat but must be explicitly invited.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Organization (Enterprise) |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Whimsical's help documentation describes removing a member from a workspace (revoking access), not permanently deleting the user account. Removed members lose workspace access; their Whimsical account itself is not deleted. SCIM deprovisioning suspends workspace access when triggered via an IdP.
- Navigate to Workspace Settings → Members.
- Locate the member to remove.
- Click the options menu (⋯) next to their name.
- Select 'Remove from workspace'.
- Confirm the action.
| Data impact | Behavior |
|---|---|
| Owned records | Files created by the removed member remain in the workspace and are accessible to Admins and Owners. |
| Shared content | Shared files and folders the member had access to remain intact for other collaborators. |
| Integrations | Not documented |
| License freed | Removing an editor frees the paid seat; billing adjusts at the next billing cycle. |
Watch out for:
- Content owned by a removed member is not automatically reassigned; Admins should manually transfer ownership of critical files before removal.
- SCIM-deprovisioned users are suspended from workspace access but their content is retained.
- Removing a member does not delete their personal Whimsical account.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Editor seat | Full create/edit access; roles Owner, Admin, Member all consume one editor seat. | $10/editor/month on Pro; approximately $18–20/editor/month (monthly) or ~$150/editor/year on Organization plan. |
| Viewer seat | View and comment access only; unlimited viewers. | Free on all plans. |
- Where to check usage: Workspace Settings → Members (shows current member list and roles); Workspace Settings → Billing (shows seat count and billing details).
- How to identify unused seats: Review the Members list for last-active dates or members who have never accepted their invitation; revoke pending invites for users who have not joined.
- Billing notes: Billing is per editor seat. Viewers are always free and unlimited. Students and teachers may qualify for free access. Annual Organization billing offers approximately 4 months free compared to monthly billing.
The cost of manual management
Manual provisioning is handled entirely through Workspace Settings → Members. Inviting a new editor immediately increases the billable seat count, and pending invitations that go unaccepted can still occupy a seat until manually revoked.
There is no bulk CSV import path for adding users at scale without an IdP and SCIM setup, making large onboarding events operationally expensive to manage by hand.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual administration is viable for small teams with low member churn. For any workspace where every app in the employee lifecycle needs to stay in sync - onboarding, role changes, offboarding - the absence of bulk tooling and the pending-invite seat leak make manual management progressively harder to sustain.
Teams on the Organization plan with an existing Okta or Azure AD deployment should evaluate SCIM provisioning before headcount grows.
Bottom line
Whimsical's manual user management is straightforward for small, stable teams: invite via email, assign a role, remove through the Members settings page.
The model breaks down at scale due to no bulk import, no custom roles, and a billing quirk where unaccepted invitations hold paid seats. Viewer seats remain free and unlimited, which is a meaningful cost lever for organizations with large numbers of read-only collaborators.
Teams expecting frequent onboarding or offboarding cycles should treat SCIM provisioning as the intended path rather than an optional upgrade.
Automate Whimsical 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.
