Webflow User Management Guide

• Model type: role-based
• Description: Webflow uses predefined workspace-level roles (Owner, Admin, Member) combined with seat types (Full, Limited) that control Designer vs Editor access. Site-level permissions can be toggled (e.g., publish rights for Limited seats) but there are no fully custom role definitions. Enterprise adds SSO and SCIM for automated provisioning.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse: role determines Designer vs Editor access; site-level publish toggle is the only per-site permission adjustment available for Limited seats

1. Log in to Webflow and open the target workspace.
2. Click the workspace name or avatar in the top-left, then select 'Workspace Settings'.
3. Navigate to the 'Members' tab.
4. Click 'Invite members'.
5. Enter the invitee's email address.
6. Select the seat type: Full seat or Limited seat.
7. Click 'Send invite'.
8. Invitee receives an email and must accept to join the workspace.
9. After joining, an Owner or Admin can grant the member access to specific sites via each site's 'Share' or 'Members' settings.

Required fields: Email address of invitee, Seat type selection (Full or Limited)

Watch out for:

• Invitations expire; if the invitee does not accept, the seat is not consumed but the invite must be resent.
• Adding a member beyond the plan's included seat count immediately increases the monthly/annual bill.
• Site-level access must be granted separately after the member joins the workspace; joining the workspace alone does not grant access to any site.
• Limited seat (Editor) access requires Growth or Enterprise plan; inviting as Limited seat on Core plan is not available.
• Legacy Editor Seats are being retired end of 2025; new invitations should use Limited seat type.

• Can delete users: Yes
• Delete/deactivate behavior: Webflow does not have a separate 'deactivate' state for workspace members. Removing a member revokes their workspace access immediately. There is no soft-disable; the action is a removal. The member's Webflow account itself is not deleted-only their membership in that workspace is terminated.

1. Log in to Webflow and open the target workspace.
2. Go to Workspace Settings → Members tab.
3. Locate the member to remove.
4. Click the three-dot (⋯) menu next to their name.
5. Select 'Remove from workspace'.
6. Confirm the removal in the dialog.

Watch out for:

• The Owner cannot be removed by Admins; ownership must be transferred first.
• Removing a member does not delete their Webflow account; they retain access to any other workspaces they belong to.
• CMS content and design work created by the removed member is not reassigned automatically; manual reassignment or documentation is needed.
• For Enterprise with SCIM, deprovisioning via the IdP (Okta/Entra) is the recommended method and will remove the member from the workspace automatically.
• Seat billing reduction timing depends on plan type; verify with Webflow billing for exact proration on annual plans.

• Where to check usage: Workspace Settings → Members tab (shows all current members and seat types); Workspace Settings → Billing tab (shows seat count and cost breakdown)
• How to identify unused seats: No built-in 'last active' or login-date column is displayed in the Members tab as of early 2025. Admins must cross-reference member list with site activity logs or ask members directly. Enterprise customers can use IdP activity reports when SCIM/SSO is configured.
• Billing notes: Workspace plans (Core $19/mo, Growth $49/mo) include a set number of seats; additional seats are billed at per-seat rates. Enterprise is custom-priced annually. Legacy Editor Seats are being retired at end of 2025 and replaced by Limited seats-existing Editor Seat holders will be migrated. Site plans (Basic, CMS, Business, E-commerce) are separate from workspace seat billing and cover hosting/publishing capabilities per site.

Every app added to a workspace requires a separate site-level access grant after the workspace invite is accepted - a two-step process that is easy to skip and has no automated reminder.

Admins have no built-in last-login or activity timestamp in the Members tab, so identifying unused seats means cross-referencing member lists with site activity logs or asking members directly.

Seat overages are billed immediately when the plan's included seat count is exceeded. Limited seats ($15/user/month) require a Growth or Enterprise plan; Core plan customers cannot add content-only collaborators at the lower seat rate. Legacy Editor Seats are being retired at end of 2025, requiring migration of existing holders to the Limited seat type.

The most consistent friction reported by Webflow admins centers on three areas: pricing opacity, seat visibility, and onboarding gaps.

• Enterprise-only SSO/SCIM locks automated provisioning behind custom, non-transparent pricing with no self-serve signup path.
• No built-in activity timestamp in the Members tab makes seat audits dependent on external tooling or manual outreach.
• Site-level access must be granted separately after workspace invite, creating an onboarding gap that results in members joining the workspace but having no site access.
• Limited seat availability is plan-gated; Core plan customers cannot use the lower-cost seat type for content editors.

Common complaints:

• Enterprise-only SSO/SCIM locks automated provisioning behind the highest-cost tier with custom (non-transparent) pricing.
• Must contact Webflow sales for Enterprise pricing; no self-serve Enterprise signup.
• No monthly billing option for Enterprise; annual commitment required.
• No built-in 'last login' or activity timestamp in the Members tab, making it difficult to identify unused seats without external tooling.
• Site-level access must be granted separately after workspace invite, creating a two-step onboarding process that is easy to miss.
• Limited seat (Editor) access requires Growth plan minimum, meaning Core plan customers cannot add content-only collaborators at the lower seat price.
• Legacy Editor Seat migration to Limited seats at end of 2025 has caused confusion about pricing and access continuity.
• No custom roles or granular permission sets; role options are limited to Owner/Admin/Member distinctions.
• Removing a member does not reassign their CMS content or design assets, requiring manual cleanup.

Choose manual management if your team is small, turnover is low, and you are on a Core or Growth workspace plan. The two-step invite-then-grant workflow is manageable at low scale but becomes error-prone as headcount grows.

Escalate to Enterprise if you need SCIM-driven provisioning from Okta or Microsoft Entra ID, or if SSO is a compliance requirement. Be prepared for annual billing commitment and a sales-led pricing conversation - there is no self-serve Enterprise tier.

If seat cost visibility is a priority, note that the Members tab shows current seat types but no activity data. Teams managing more than a handful of seats should plan for a periodic manual audit or use IdP activity reports if on Enterprise with SSO configured.

Bottom line

Webflow's manual member management is straightforward for small teams but accumulates operational overhead quickly as workspace size grows.

Every app access grant is a two-step action, there is no native seat activity reporting below Enterprise, and the Limited seat type - useful for content-only collaborators - is unavailable on the Core plan.

Automated provisioning via SCIM is available but locked to Enterprise Workspace with annual billing and active SSO, making it inaccessible without a sales engagement.

Teams that need audit-grade access control or high-volume onboarding should factor the Enterprise gate into their planning before committing to Webflow's workspace model.