Summary and recommendation
Framer 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.
Framer's workspace access model is role-based with three fixed workspace roles - Owner, Admin, and Editor - plus per-project share permissions (edit or view). There are no custom roles or granular permission sets.
Every app in a modern SaaS stack ideally supports automated provisioning, but Framer currently has no documented SCIM support, making every user lifecycle action a manual operation.
SSO via SAML (Okta, Entra ID) is available on Enterprise plans but requires contacting Framer support directly - there is no self-serve configuration in the admin UI. Framer restructured its plans to a simplified Basic/Pro/Scale model as of October 2025; Enterprise pricing is custom and negotiated directly.
Quick facts
| Admin console path | framer.com → Workspace Settings (gear icon) → Members |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full workspace control: billing, plan changes, member management, project creation and deletion, all editor capabilities. | Cannot be removed by other admins; only one Owner per workspace. | Any paid plan (workspace context) | Counts as a paid editor seat on team plans | Ownership transfer requires the current Owner to initiate it manually from Workspace Settings. |
| Admin | Manage members (invite, remove, change roles), access all projects, edit all projects, manage workspace settings except billing. | Cannot change billing or transfer ownership. | Pro, Scale, or Enterprise team plan | Counts as a paid editor seat | Admin role is only available on team/workspace plans, not on individual plans. |
| Editor | Create, edit, and publish projects they have been granted access to. Can invite collaborators to individual projects if permitted. | Cannot manage workspace members, change billing, or access projects they have not been invited to. | Any paid plan | $15/person/month on personal plans; seat cost varies by team plan tier | Each Editor consumes a paid seat. Adding editors beyond the plan's included count triggers additional per-seat charges. |
| Viewer | View and comment on published projects or shared preview links. No editing capability. | Cannot edit projects, manage workspace, or publish changes. | Free or any paid plan (viewers do not consume editor seats) | Free; does not count against editor seat quota | Viewer access is granted per project via share link or direct invite; there is no workspace-wide viewer role assignment in the same way as Editor/Admin. |
Permission model
- Model type: role-based
- Description: Framer uses a fixed set of workspace-level roles (Owner, Admin, Editor) combined with project-level sharing permissions (can edit, can view). There are no custom roles or granular permission sets. Roles are assigned per workspace member; project-level access can be further restricted by sharing settings.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level role assignment (Owner/Admin/Editor) plus per-project share permissions (edit or view). No field-level or feature-level granularity.
How to add users
- Navigate to framer.com and open the target workspace.
- Click the gear icon or go to Workspace Settings.
- Select the 'Members' tab.
- Click 'Invite Members' or 'Invite People'.
- Enter the invitee's email address.
- Select the role to assign (Admin or Editor).
- Click 'Send Invite'. The invitee receives an email invitation and must accept to join the workspace.
- Alternatively, share a project directly by opening the project, clicking 'Share', entering the email, and selecting 'Can Edit' or 'Can View'.
Required fields: Email address of invitee, Role selection (Admin or Editor)
Watch out for:
- Inviting an Editor on a plan that has reached its included seat count will immediately increase the billing amount.
- Invitees must accept the email invitation before they appear as active members; pending invites still consume a seat slot on some plan tiers.
- SSO-enabled workspaces (Enterprise) may require users to authenticate via the configured IdP before accessing the workspace.
- There is no domain-based auto-join; every member must be individually invited.
| 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: Framer allows workspace Owners and Admins to remove (delete) members from the workspace entirely. There is no 'deactivate' or 'suspend' state; removal is permanent from the workspace. The removed user's Framer account itself is not deleted.
- Navigate to Workspace Settings → Members.
- Locate the member to remove.
- Click the three-dot menu (⋯) or 'Options' next to the member's name.
- Select 'Remove from Workspace' (or equivalent label).
- Confirm the removal in the dialog prompt.
| Data impact | Behavior |
|---|---|
| Owned records | Projects created by the removed member remain in the workspace and are accessible to Admins and the Owner. Ownership of those projects does not automatically transfer. |
| Shared content | Shared project links created by the removed member may remain active depending on link settings; workspace Admins can revoke or manage these. |
| Integrations | Any personal API tokens or integrations set up by the removed member under their account are not automatically revoked from the workspace side; these must be audited manually. |
| License freed | Removing an Editor frees the paid seat, which is reflected in the next billing cycle or immediately depending on plan billing terms. |
Watch out for:
- Framer does not have a 'deactivate' or 'suspend' option; removal is the only way to revoke workspace access.
- Projects owned by the removed user stay in the workspace but may lack a clear owner, requiring manual reassignment.
- Seat credit for mid-cycle removals depends on Framer's billing terms; prorated refunds are not explicitly documented for all plan types.
- Removing a member does not automatically revoke any public share links they created for projects.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Editor seat | Full project creation, editing, and publishing access within the workspace. | $15/person/month on individual plans; varies by team plan (Pro, Scale, Enterprise) |
| Viewer (no seat charge) | View and comment access to shared projects via invite or link. | Free; does not consume a paid seat |
- Where to check usage: Workspace Settings → Members (shows current member count and roles); Workspace Settings → Billing (shows seat count and current charges)
- How to identify unused seats: No built-in 'last active' or usage analytics dashboard is documented for workspace admins. Seat usage must be audited manually by reviewing the Members list and cross-referencing project activity.
- Billing notes: As of late 2025, Framer moved to a simplified three-tier structure (Basic, Pro, Scale) for site/workspace plans. Editor seats beyond the plan's included count are billed at the per-seat rate. Enterprise pricing is custom and negotiated directly with Framer. Annual billing provides a discount over monthly billing. SAML SSO requires contacting Framer support for activation and is associated with Enterprise-tier agreements.
The cost of manual management
Every Editor added to a workspace consumes a paid seat. On individual plans, that is $15/person/month; team plan rates vary by tier. Viewers do not consume paid seats and access projects via share link or direct invite.
There is no built-in last-login or usage analytics dashboard. Identifying inactive editors requires manually reviewing the Members list and cross-referencing project activity - there is no automated signal to surface unused seats.
Removing a member is permanent; Framer has no deactivate or suspend state. Projects owned by a removed member remain in the workspace but may require manual ownership reassignment.
What IT admins are saying
Recurring friction points reported by Framer workspace admins center on provisioning gaps and audit limitations:
- No SCIM provisioning means automated user lifecycle management is unavailable.
- SAML SSO requires a support ticket to activate - no self-serve toggle exists in the UI.
- No bulk or CSV import for adding multiple members at once.
- No domain whitelisting or auto-join for verified company domains.
- No deactivate/suspend state - removal is the only way to revoke access.
- No last-login or seat usage analytics to identify editors consuming paid seats without active use.
Common complaints:
- Manual SAML activation required via support - no self-serve SSO configuration in the UI.
- No CSV or bulk import for adding multiple workspace members at once.
- No domain whitelisting or auto-join for users from a verified company domain.
- No SCIM provisioning documented, making automated user lifecycle management unavailable.
- No 'deactivate' or 'suspend' state for members - only full removal is possible.
- No built-in last-login or seat usage analytics to identify inactive editors consuming paid seats.
- Pending invitations reportedly consuming seat quota before the invitee accepts, leading to unexpected billing.
- Project ownership does not automatically transfer when a member is removed, leaving orphaned projects.
The decision
Framer is a strong fit for design-led teams that manage a small, stable roster of editors and do not require automated provisioning. The role model is straightforward, and project-level sharing provides a secondary layer of access control.
For organizations that need SCIM-based onboarding and offboarding, Framer is not a viable option today. Every app in an enterprise stack that lacks SCIM creates a manual gap in the joiner-mover-leaver process - Framer is one such gap.
Teams evaluating Enterprise should factor in the support-gated SSO activation and the absence of a self-serve admin experience before committing to a plan.
Bottom line
Framer's access management works for small teams comfortable with manual workflows, but it carries real operational cost at scale. No SCIM, no bulk import, no usage analytics, and a support-gated SSO setup mean that every provisioning and deprovisioning action requires direct admin intervention.
Organizations with compliance requirements or high employee turnover should weigh these gaps carefully before standardizing on Framer as a workspace tool.
Automate Framer 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.
