Locale Specific Roles & Permissions

For added flexibility, customize permissions within the Content API to restrict users down to particular content, locations and languages.

  • It's best for multi-language e-commerce platforms that have high tariffs.

    Hygraph User
  • My team needed a scalable headless CMS for our homepage, company blog, and all of our periodic content. Why we chose Hygraph: rich-text visual editor, easy-to-use localization feature (our content is in 11 languages), scalability (several hundred thousand visitors per month) and the ability to write content into the CMS programmatically (awesome for importing content from other systems).

    Tatyana M.CEO
  • Localization API is amazing.

    Hygraph User
  • ...we’ve found the platform to be quite flexible. Being able to not only specify relationships between content, but also the way it relates to other parts of the schema (one-to-one, one-to-many, etc.), makes for great control over the schema. We’ve internally started using it for prototypes that go beyond the scope of a simple CMS because of this flexibility.

    Roland P.
  • Hygraph is a way for us to allow non-engineers at our company to create content for our marketing website. Once the engineers define the data model within GraphCMS, other employees at our company can easily add the content through their UI, and once published, our build system automatically rebuilds the website with the new content.

    Hygraph User
  • The interface - It's slick. Intuitive and best of all, rapid fast. You can get exactly what you need done in a fraction of the time for other headless CMS about.

    Doug S. Product Consultant


Created via the UI and API, Locale Specific Locales are a facet of the broader Granular Permissions or Custom Permissions feature.

Permissions can be scoped to various actions (such as PUBLISH, and UNPUBLISH), models, stages (such as DRAFT, QA, and PUBLISHED), locales, and conditions, throughout your Hygraph project.

Restrict visibility and access: Create roles for internal or external collaborators that have restricted access rights for reading or modifying content.

Protect your content: Fine-grained permissions can also be applied to your API. Allow different content sets to be seen for authorized users.

Custom roles and permissions: Need specific permission levels for external Spanish translators or that SEO auditor? Set up custom roles to perform exactly those functions. Nothing more, nothing less.