Choose which pages Site members can edit static content on.
Important
The ability to manage static content editing access by page
is only available on specific Enterprise plans and to eligible partners.
Site managers can choose which pages each Site member can edit static content on. This lets you bring in collaborators for specific tasks while keeping sensitive pages restricted. For example, you might give someone on your legal team access to edit static content on your Terms & Conditions page, without giving them access to edit static content on your homepage.
You can also give Site members access to edit dynamic content only by restricting static content editing on all pages. When a Site member is restricted from editing static content on a page, they also can’t access that page’s settings or create/merge branches.
Site roles restrictions
Site managers can control static content editing access for Site members with these site roles:
Designer, Marketer, or Content editor site roles
Custom roles based on Designer, Marketer, or Content editor
It’s not possible to control static content editing access for members with these site roles:
How to limit static content editing access
You can manage static content editing access for existing team members in Site settings. To control which pages a member can edit static content on:
Go to Site settings > Site access
Click the “page” icon under Access for an eligible member
Deselect pages (or folders) you don’t want them to edit static content on
Select pages (or folders) you want to allow them to edit static content on
Click Save
Good to know
For new Workspace members, you can limit their access to edit static
content on specific pages during
the invite process.
What restricted users can and can’t do
Site members with restricted access to certain pages can still open and view those pages (and any branches), as well as edit dynamic content if they have access to the CMS Collection, but they can’t:
Edit static content (including static component property values)
Access page settings
Create, merge, or edit branches
Bind or unbind CMS fields (even if they have access to the CMS Collection)
FAQs
Can static content editing be restricted on all pages?
Static content editing can be restricted on all pages except Ecommerce pages, including Collection pages and utility pages.
What happens when someone creates a new page?
If a Site member can edit static content on all pages, they automatically gain access to edit new pages. If a Site member is restricted from editing static content on certain pages, they don’t automatically get access — unless they created the page.
Does this affect dynamic (CMS) content?
No. CMS Collection access is controlled separately. If a member has CMS Collection access, they can still edit dynamic content on pages where editing static content is restricted — apart from binding or unbinding elements to CMS fields.
Can static content editing be restricted on secondary locales?
Static content editing access applies across all locales. For example, if a Site member is restricted from editing static content on a page — they won’t be able to edit static content on that page in any locale. It's not possible to grant or restrict access to pages on a specific locale.
Does restricting static content editing affect publishing?
No. If a Site member’s role allows publishing, they can still publish the site, even if they can’t edit static content on certain pages. You can control publishing permissions using custom roles.