Squarespace Permissions Explained: How to Choose the Right Access for Designers, Developers, and Collaborators
Inviting someone to work on your Squarespace site seems straightforward until you’re staring at a list of permission levels that don’t quite match what people actually need to do. “Website Editor,” “Administrator,” and “Store Manager” all sound reasonable, but choosing the wrong one can quickly slow a project down, create unnecessary back-and-forth, or make it feel like something is broken when it’s really just permissions.
This article explains how Squarespace permissions actually work in practice. We’ll focus on the permissions that matter most, explain when and why Admin access is necessary, then cover the more functional and edge-case roles so you can assign access confidently without overthinking it.
The Permissions That Matter Most
For most sites, there’s a clear hierarchy to Squarespace permissions. At the top are Owner and Administrator. These are the roles that control how the site is built, managed, and evolved over time. Everything else exists to support more limited, task-specific work.
Owner
The Owner is the primary account holder for a Squarespace site. There is only one Owner, and this role is usually held by the business owner or the person who originally created the site.
What they can do
Everything an Administrator can do
Transfer site ownership to another account
Change an Administrator’s permissions
Manage billing, domains, and subscriptions
What they can’t do
Nothing within Squarespace itself
Who uses this permission level
Business owners
Primary site owners
The person financially and operationally responsible for the site
For most day-to-day site work, the Owner role doesn’t come up often. Its importance is mainly around ownership, billing, and long-term control.
Administrator
Administrators have full control over how a Squarespace site is built, styled, and managed. This is the permission level required for most professional design, development, and technical work.
What they can do
Change Site Styles (color themes, fonts, size, spacing, buttons, and other design settings)
Create new pages
Publish disabled or unlinked pages
Edit and delete any content
Add and edit Custom CSS
Add code via Code Injection (header and footer)
Manage navigation and page hierarchy
Duplicate the site
Add, remove, and manage contributors (except the Owner)
Configure integrations and advanced settings
What they can’t do
Transfer site ownership
Change the Owner’s permissions
Who needs Administrator access (and why)
Admin access often feels like a big step, and it’s reasonable to hesitate before giving someone this level of control. In general, you shouldn’t give Admin access casually.
That said, Admin access is often necessary to avoid friction and allow people to work independently.
-
Add custom CSS and JavaScript
Use Code Injection
Implement advanced functionality
Fix layout and responsive issues
Integrate third-party tools
-
Control site-wide styles
Adjust fonts, spacing, and visual hierarchy
Modify navigation and page structure
Ensure consistency across the entire site
-
Modify site-wide SEO settings
Add tracking or schema scripts
Manage redirects
Make structural changes that affect search visibility
-
Maintain the site long-term
Publish content and manage structure
Act as the go-to person for site updates and improvements
The real best practice isn’t “never give Admin access.” It’s giving Admin access intentionally, using it to remove bottlenecks while work is actively happening, and then downgrading or removing that access as roles change.
Other Functional Permission Levels
Once Owner and Administrator are accounted for, the remaining permissions are about specific responsibilities, not overall site control.
Website Editor
Website Editors are meant to manage and maintain content within an existing site structure.
What they can do
Edit content on existing pages (text, images, blocks)
Add and publish blog posts
Add and publish events
Add, edit, and publish products
Update page-level SEO fields
Rearrange sections and blocks within existing pages
What they can’t do
Create new pages
Publish existing disabled or unlinked pages
Change Site Styles
Add or edit Custom CSS
Use Code Injection
Change site structure or navigation
Manage contributors
Access billing or subscriptions
Who uses this permission level
Copywriters
Content managers
Marketing assistants
Team members responsible for routine updates
Website Editor is ideal for content work, but it will feel limiting if someone needs to change how the site looks or behaves.
Store Manager
Store Managers are focused on ecommerce operations rather than site structure or design.
What they can do
Add, edit, and publish products
Manage inventory
Process and fulfill orders
Edit existing page content
What they can’t do
Create new pages
Publish existing disabled or unlinked pages
Change Site Styles
Add Custom CSS or Code Injection
Modify site structure or navigation
Manage contributors
Access billing settings
Who uses this permission level
Ecommerce operations staff
Fulfillment managers
Team members responsible for maintaining the store
Minor and Edge-Case Permissions
These permissions exist for very specific needs and are less commonly used in day-to-day site collaboration.
Analytics
Can do: View site analytics and reports
Can’t do: Edit content, design, or settings
Used by: Marketers, stakeholders, reporting-only users
Email Campaigns Editor
Can do: Create, send, and manage email campaigns
Can’t do: Edit site content, design, or billing
Used by: Email marketing specialists
Viewer
Can do: View private or password-protected site content
Can’t do: Edit anything
Used by: Clients or stakeholders who need view-only access
Comment Moderator
Can do: Approve, edit, and delete comments
Can’t do: Edit site content or settings
Used by: Community or blog moderators
The Real Takeaway
Squarespace permissions aren’t about trust, they’re about responsibility. When access levels match what someone actually needs to do, projects move faster, fewer things break, and there’s less confusion about what’s possible. Give people the access they need to work independently, review permissions occasionally, and adjust them as roles change. That balance is what Squarespace permissions are designed to support.
