Locale-specific access

Updated

Restrict which secondary locales team members can edit to delegate content ownership safely.

Workspace admins can choose which locales team members can edit. This lets you limit team members to one or more secondary locales, so you can confidently delegate content ownership without risking accidental changes to the wrong locale.

Note

The ability to manage locale access is only available on specific Enterprise plans and partners. The site must also have at least two locales.

Site roles restrictions

Admins can control locale access for 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 edit locale access for these roles:

  • Reviewer — can't edit content in any locale
  • Site manager — has access to edit all locales on the site

How to limit locale access

You can restrict locale access for existing team members from the Site access settings for each site.

To control which locales a member can edit:

  1. Go to Site settings > Site access
  2. Click the Locales icon under Access for an eligible member
  3. Deselect the locales you don't want them to edit
  4. Select the locales you want to allow them to edit
  5. Click Save

Good to know

When inviting a new team member, you can also set their locale access during the invite process.

What restricted members can and can't do

Members that are limited from editing a specific secondary local can still access that locale in a view-only mode. These restricted locales display a view only badge in the locale switcher.

Members that are limited from editing a specific secondary local can't:

  • Edit any CMS items in that locale
  • Edit any static page content in that locale
  • Access page settings in that locale
  • Create or merge branches that affect content in that locale
  • Reset localized fields to primary in that locale
  • Trigger AI translation into that locale
  • Edit localized component overrides in that locale

Good to know

Page access controls, CMS collection access controls, and locale access controls are independent — each applies at the same time. For example, restricting a member from a page applies across all locales, regardless of their locale access.

Understand default behavior and limitations

  • New locales — members with access to all locales automatically gain access when a new locale is added. Members restricted from some locales don't automatically gain access to new locales
  • Primary locale — it's not possible to restrict access to the primary locale, and members cannot be restricted to the primary locale only. Locale access can only be scoped to one or more secondary locales. The primary locale acts as the source of truth for all secondary locales, and changes made there cascade to secondary locales unless a field has been localized.
  • Publishing — locale access applies to editing only. Members who can otherwise publish (i.e., Designers and Admins) can still publish the site, including locales they're restricted from editing
  • Role upgrades — upgrading a member to Site manager grants full access to all locales, regardless of previous restrictions

Related articles