Squarespace Roles and Permissions — Owner to Store Manager | OpsBlu Docs

Squarespace Roles and Permissions — Owner to Store Manager

Squarespace Owner, Administrator, Editor, Store Manager, and specialized contributor roles with per-area access controls.

Understanding Squarespace's permission system is crucial for properly managing team access. This guide provides a comprehensive breakdown of each role and what contributors can and cannot do.


Permission Levels Overview

Squarespace offers several permission levels, each with specific capabilities:

Role Access Level Best For
Owner Full control including ownership transfer Site owner only
Administrator Full site access (except billing/ownership) Trusted team members, agencies
Website Editor Edit pages and content, limited settings Content managers
Store Manager Manage products, orders, and customers E-commerce team
Blog Editor Create and edit blog posts Writers, content creators
Reporting View analytics only Data analysts
Commenter Leave comments on blog posts Community engagement
Scheduling Permissions Manage appointments Service businesses with Acuity
Billing Manage billing and subscriptions Finance team

Owner

What Owners Can Do

Everything. The owner has complete control over:

  • All site content and design
  • All settings and configurations
  • Billing and payment information
  • Adding/removing contributors
  • Transferring site ownership
  • Canceling the site
  • Accessing support as the account holder

Limitations

  • Only one owner per site
  • Cannot be removed unless ownership is transferred
  • Responsible for billing and legal compliance

When to Use

  • You are the site owner/business owner
  • You are ultimately responsible for the site
  • You handle or oversee billing

Transfer Ownership

To change site owner:

  1. Owner goes to Settings > Permissions
  2. Click "Transfer Ownership"
  3. Enter new owner's email
  4. New owner must accept transfer
  5. Original owner becomes Administrator (or is removed)

Warning: Ownership transfer cannot be undone. Only transfer to someone you completely trust.


Administrator

What Administrators Can Do

Almost everything except:

  • Transfer ownership
  • Cancel the site
  • Access billing information (unless separately granted)

Full Access To:

  • Pages and content
  • Design and templates
  • Settings and configurations
  • Code Injection
  • Integrations and connected accounts
  • Domain settings
  • SEO settings
  • Analytics
  • All commerce features (if applicable)
  • Member areas (if applicable)
  • Adding/removing contributors (with some limitations)

What Administrators Cannot Do

  • View or change billing information
  • Transfer site ownership
  • Cancel or delete the site
  • Remove the owner
  • Access support as the account holder

When to Use

  • Web designers/developers: Building or maintaining the site
  • Agency partners: Managing client sites
  • Trusted team members: Full-time employees with broad responsibilities
  • Technical managers: Need access to all features

Security Note

Administrators have extensive access. Only grant to:

  • People you trust completely
  • Those who need this level of access
  • Temporary access should be downgraded after project completion

Website Editor

What Website Editors Can Do

Content Management:

  • Edit existing pages
  • Create new pages
  • Manage page settings
  • Add and edit content blocks
  • Upload and manage files in asset library
  • Edit navigation menus

Limited Settings:

  • Some basic page settings
  • Can publish changes they make

What Website Editors Cannot Do

  • Access Code Injection
  • Change design/template
  • Modify site-wide settings
  • Access billing
  • Manage integrations
  • Add/remove contributors
  • Access analytics (unless also given Reporting permission)
  • Manage domains
  • Access commerce features

When to Use

  • Content managers: Update pages regularly but don't need technical access
  • Marketing team: Manage landing pages and content
  • Junior team members: Safe access for day-to-day updates
  • Temporary editors: Short-term content projects

Best Practices

  • Ideal for ongoing content updates
  • Limits risk of accidental configuration changes
  • Can be combined with other permissions (e.g., + Reporting)

Store Manager

What Store Managers Can Do

E-commerce Functions:

  • Add, edit, and delete products
  • Manage product variants and options
  • Update inventory levels
  • Process orders
  • Issue refunds
  • Manage customers
  • View sales reports
  • Create discount codes
  • Manage product categories
  • Edit product pages

Limited Access:

  • Can only access commerce-related features
  • Cannot edit other site content

What Store Managers Cannot Do

  • Edit non-commerce pages
  • Access site settings
  • Change design or template
  • Access Code Injection
  • Manage billing
  • Add/remove contributors
  • Modify shipping or tax settings (Administrator only)

When to Use

  • E-commerce managers: Daily product and order management
  • Inventory specialists: Stock level management
  • Customer service: Order processing and refunds
  • Product team: Product listing and updates

Important Notes

  • Store Managers can see customer data (names, addresses, emails)
  • Ensure they understand data privacy responsibilities
  • Only grant to those who need customer access

Blog Editor

What Blog Editors Can Do

Blog-Specific Access:

  • Create new blog posts
  • Edit existing blog posts
  • Delete blog posts
  • Upload images for posts
  • Manage categories and tags
  • Schedule posts
  • Edit post settings (author, categories, excerpt)

What Blog Editors Cannot Do

  • Edit other pages (non-blog)
  • Access site settings
  • Manage design
  • Access Code Injection
  • View analytics (unless also given Reporting)
  • Manage contributors
  • Access commerce features

When to Use

  • Writers: Content creators focused on blog
  • Content team: Regular blog contributors
  • Guest bloggers: Temporary contributors
  • Social media managers: Creating blog content for sharing

Best Practices

  • Perfect for content-focused team members
  • Safe permission level for external writers
  • Consider combining with Reporting to see post performance

Reporting

What Reporting Users Can Do

Analytics Access:

  • View all Squarespace Analytics data
  • See page views, visitors, traffic sources
  • View commerce analytics (if applicable)
  • Export analytics data
  • View real-time statistics

What Reporting Users Cannot Do

  • Edit any content
  • Change any settings
  • Access anything except analytics
  • Make any changes to the site

When to Use

  • Data analysts: Need to view data but not edit site
  • Marketing team: Track performance without editing access
  • Stakeholders: Interested in metrics only
  • Clients: Want to see their site's performance

Important Notes

  • Read-only access to analytics
  • Completely safe - cannot break anything
  • Perfect for "view only" access needs
  • Can be combined with other permissions

Limitation

  • Only shows Squarespace's native analytics
  • Does not include Google Analytics access (share GA4 separately if needed)

Commenter

What Commenters Can Do

  • Leave comments on blog posts (if comments enabled)
  • Reply to other comments
  • Edit their own comments

What Commenters Cannot Do

  • Access admin panel
  • Edit any content
  • View any settings or analytics
  • Anything besides commenting

When to Use

  • Community members: Active blog community
  • Moderators: People who participate in discussions
  • Rarely used: Most sites don't need this role

Note

This is a very limited role, rarely used in practice. Most sites either:

  • Allow public commenting without login
  • Or don't use Squarespace's built-in comments

Scheduling Permissions

What Scheduling Users Can Do

If you have Acuity Scheduling:

  • Manage appointments
  • View calendar
  • Edit availability
  • Manage clients/customers
  • Send appointment reminders

What They Cannot Do

  • Edit site content
  • Access non-scheduling features

When to Use

  • Service businesses: Staff who manage appointments
  • Receptionists: Scheduling team
  • Service providers: Individual practitioners

Note: Only relevant if your site uses Acuity Scheduling.


Billing

What Billing Users Can Do

Financial Access:

  • View billing information
  • Update payment methods
  • View invoices
  • Manage subscription
  • Add/remove billing details

What Billing Users Cannot Do

  • Edit site content
  • Access site settings (unless also Administrator)
  • Transfer ownership
  • Cancel site (Owner only)

When to Use

  • Finance team: Managing company subscriptions
  • Accountants: Need access to invoices
  • Billing managers: Separate from site management

Important

  • Billing can be granted separately from site access
  • Someone with only Billing permission cannot edit the site
  • Recommended to keep billing separate from content access

Combining Permissions

Some contributors may need multiple permission types.

Common Combinations

Content Manager + Analyst:

  • Website Editor + Reporting
  • Allows content updates and performance tracking

E-commerce Manager + Analyst:

  • Store Manager + Reporting
  • Manage products and see sales data

Blog Manager:

  • Blog Editor + Reporting
  • Write posts and track engagement

Designer + Analyst:

  • Administrator + Reporting (redundant - Admins already see analytics)

How to Add Multiple Permissions

Unfortunately, Squarespace doesn't always allow combining permissions:

  • Some roles are mutually exclusive
  • You may need to choose the broader permission level
  • Or use multiple accounts (not recommended)

Best Practice:

  • Choose the permission level that covers most needs
  • Grant Administrator if truly needs multiple broad access types

Permission Comparison Table

Feature Owner Admin Website Editor Store Manager Blog Editor Reporting Commenter
Edit pages
Change design
Code Injection
Manage products
Process orders
Create blog posts
View analytics
Manage contributors *
Access billing
Transfer ownership

*Administrators can manage some contributors but cannot remove owner


Choosing the Right Permission Level

Decision Framework

Ask yourself:

  1. What does this person need to DO?

    • Specific task determines base permission level
  2. How long will they need access?

    • Temporary: Consider higher access, then remove
    • Permanent: Use most restrictive level needed
  3. How much do you trust them?

    • Complete trust + ongoing: Administrator
    • Trust but limited: Website Editor, Store Manager, Blog Editor
    • New or external: Most restrictive appropriate level
  4. What's the risk if they make a mistake?

    • High risk area: More restrictive
    • Low risk area: Can be more permissive

Common Scenarios

Scenario Recommended Permission
Building new site Administrator (temporary)
Monthly content updates Website Editor
Writing blog posts Blog Editor
Managing online store Store Manager
Viewing performance data Reporting
Emergency access backup Administrator (but inactive)
Client wants to see data Reporting
Finance department Billing only

Security Best Practices

1. Principle of Least Privilege

Always give the minimum access needed:

  • Don't make everyone an Administrator
  • Use specific roles for specific tasks
  • Upgrade temporarily if needed for a project

2. Regular Audits

  • Review contributor list quarterly
  • Remove inactive users
  • Downgrade permissions when projects complete
  • Verify each person still needs their access level

3. Documentation

Keep a record of:

  • Who has what access
  • Why they have it
  • When it was granted
  • When it should be reviewed

4. Onboarding/Offboarding

When adding:

  • Explain what they can/can't do
  • Set expectations for access duration
  • Provide training if needed

When removing:

  • Remove promptly when no longer needed
  • Document the removal
  • Verify it's complete

Limitations to Know

Squarespace Plan Limitations

Personal Plan:

  • Maximum 2 contributors
  • Limited permission types

Business Plan and above:

  • Unlimited contributors
  • All permission types available

Permission System Limitations

  • Cannot customize permission levels beyond what Squarespace offers
  • Some permissions cannot be combined
  • Cannot create custom roles
  • Cannot set page-level permissions (e.g., edit this page but not that one)

What You Can't Restrict

Even with limited permissions, contributors can see:

  • That the site exists
  • Some basic site structure
  • Their allowed sections

Cannot hide:

  • Specific pages from specific contributors
  • Certain settings from Administrators
  • Individual products from Store Managers

Migration Considerations

From Other Platforms

If coming from WordPress, Shopify, etc.:

  • Squarespace permissions are less granular
  • May need to adjust team access patterns
  • Some platforms offer more custom permission options

Plan Upgrades

When upgrading from Personal to Business:

  • Can add more contributors
  • More permission types become available
  • Existing contributors keep their permissions

Troubleshooting Permission Issues

Issue: Contributor Can't Do Something

Check:

  1. What's their permission level?
  2. Is the feature available for that level?
  3. Is it a plan limitation?

Solution:

  • Upgrade their permission if appropriate
  • Or provide alternative method (screenshots, share access differently)

Issue: Too Much Access

If contributor has too much access:

  1. Immediately reduce to appropriate level
  2. Review recent changes they made
  3. Document the change

Issue: Need Custom Permission

Squarespace doesn't offer:

  • Custom permission levels
  • Page-specific access
  • Feature-specific restrictions beyond standard roles

Workarounds:

  • Choose closest standard permission
  • Use Administrator for broad access
  • Consider alternative solutions (share screenshots, separate tools)

Next Steps


Additional Resources