Summary and recommendation
Squarespace 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.
Squarespace uses a fixed, role-based contributor model with six predefined roles: Owner, Admin, Content Editor, Billing, Comment Moderator, and Store Manager.
Permissions are bundled per role - there are no granular toggles or custom roles available on any self-serve plan.
Every app in your stack that relies on scoped access will hit this ceiling;
what you see in the role list is the full extent of what Squarespace exposes.
Quick facts
| Admin console path | Home Menu → Settings → Permissions |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full access to all site settings, billing, content, and contributor management. Can transfer ownership. | Cannot be removed as a contributor by other contributors; only one Owner per site. | All plans | Included in site subscription | Ownership transfer requires the current owner to initiate it; it cannot be forced by other contributors. |
| Admin | Full access to site content and settings except billing and ownership transfer. Can invite and remove other contributors. | Cannot access billing, change the site plan, or transfer ownership. | All plans | No additional seat cost documented | Admins can remove other contributors including other Admins, but cannot remove the Owner. |
| Content Editor | Can edit pages, blog posts, and other content. Cannot access site settings or contributor management. | Cannot change site design, access settings, manage contributors, or access billing. | All plans | No additional seat cost documented | Content Editors do not have access to the Pages panel for structural changes, only content within existing pages. |
| Billing | Can view and manage billing information and invoices only. | Cannot edit site content, settings, or manage contributors. | All plans | No additional seat cost documented | Billing role is narrowly scoped; the user cannot make any content or design changes. |
| Comment Moderator | Can approve, delete, and manage blog comments. | Cannot edit content, access settings, or manage contributors. | All plans | No additional seat cost documented | Scoped exclusively to comment moderation; no other site access. |
| Store Manager | Can manage orders, inventory, products, and customers in the Squarespace Commerce panel. | Cannot edit non-commerce site content, access general settings, or manage contributors. | Plans with Commerce features (Core and above based on 2025 plans) | No additional seat cost documented | Only available on plans that include Commerce functionality. |
| Trusted Commenter | Can post blog comments without moderation approval. | Cannot access the backend, edit content, or manage any site settings. | All plans | No additional seat cost documented | This is a front-end commenter privilege, not a backend contributor role. |
Permission model
- Model type: role-based
- Description: Squarespace uses a fixed set of predefined contributor roles. Each role grants a specific, non-customizable scope of access. There are no custom roles or granular permission toggles available to site owners.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse - permissions are bundled per role with no individual permission toggles.
How to add users
- Log in to Squarespace and open the site you want to manage.
- In the Home Menu, go to Settings.
- Click Permissions.
- Click Invite Contributor.
- Enter the invitee's email address.
- Select the desired role from the available options.
- Click Send Invite.
- The invitee receives an email and must accept the invitation to gain access.
Required fields: Email address of the invitee, Role selection
Watch out for:
- The invitee must have or create a Squarespace account to accept the invitation.
- Invitations expire if not accepted; a new invite must be sent if the link expires.
- Each contributor is tied to their Squarespace account email; role is per-site, not per-account globally.
- A contributor can have different roles on different Squarespace sites.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise (via Okta or Microsoft Entra ID) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Squarespace allows site owners and admins to remove (delete) a contributor's access to a site. This removes their permissions from that specific site. The contributor's Squarespace account itself is not deleted.
- Log in to Squarespace and open the relevant site.
- In the Home Menu, go to Settings.
- Click Permissions.
- Locate the contributor you want to remove.
- Click the contributor's name or the options icon next to their entry.
- Select Remove Contributor (or equivalent removal option).
- Confirm the removal.
| Data impact | Behavior |
|---|---|
| Owned records | Content created by the contributor (blog posts, pages, etc.) remains on the site after removal. |
| Shared content | Shared site content is unaffected; the contributor simply loses access. |
| Integrations | No documented impact on site integrations from removing a contributor. |
| License freed | No per-seat licensing model documented for standard plans; removing a contributor does not affect billing on standard plans. |
Watch out for:
- The Owner cannot be removed by contributors; only the Owner can transfer ownership.
- Removing a contributor does not delete their Squarespace account.
- If the removed contributor was the only Admin, the Owner retains full access but should assign a new Admin if needed.
- Re-inviting a previously removed contributor requires sending a new invitation.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Site subscription | One Squarespace website with unlimited contributors (no documented per-seat contributor limit on standard plans) | Basic $16/mo, Core $23/mo, Plus $39/mo, Advanced $99/mo (annual billing, 2025 pricing) |
- Where to check usage: Settings → Permissions (shows current contributors and their roles)
- How to identify unused seats: No built-in last-login or activity reporting for contributors documented in official help center. Admins must manually review the contributor list under Settings → Permissions.
- Billing notes: Standard Squarespace plans do not charge per contributor seat. Billing is per site subscription. Enterprise pricing is custom and may differ.
The cost of manual management
Standard plans (Basic through Advanced) do not charge per contributor seat - billing is per site subscription. SCIM-based provisioning is gated behind the Enterprise tier, which requires custom pricing and is not available on any self-serve plan. Teams managing multiple sites must configure contributor roles individually per site;
there is no cross-site bulk management interface.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
If your team needs fine-grained, per-section access control, Squarespace's current model will not support it - every app or contractor gets the full role scope or nothing. For organizations already on Enterprise with Okta or Entra ID, SCIM provisioning handles the user lifecycle cleanly.
For everyone else, contributor management is a fully manual, per-site process with no API surface to automate it.
Bottom line
Squarespace contributor management is straightforward for small teams but becomes operationally heavy at scale. The fixed role set covers common use cases but offers no granularity below the role level, no cross-site bulk actions, and no visibility into contributor activity.
Teams on self-serve plans should plan for manual provisioning and deprovisioning workflows with no automation path available until Enterprise.
Automate Squarespace 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.
