Granular Permissions
This approach enables teams to model their organizational structures and business logic, and makes it possible to restrict visibility and access as required. Teams are now able to create custom roles for internal and external users, and tokens, to give more control over who has access to what content and their ability to interact with that content. Using custom roles and permissions, teams’ Hygraph projects can be even more flexible and a broader range of use cases are now possible.
The most essential and most fantastic thing is that now we can quickly create CMS for our data. The development and prototyping are quick and fast. Things get ready speedily and rapidly with good efficiency.
Ali S.Software EngineerSuper impressed with the fine grained roles and permissions; I had a colleague on a hangout who has experience with other headless CMS vendors, and his jaw dropped at the sheer capability.
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.Easy to set up and get started with. Versatile content modeling with flexible model relations and on-fly changes without the need or worry about API, GraphQL obviously, and a cherry on top - included CDN with image transformation. Oh wait, there are two cherries on top, Netlify integration being the other.
E-LearningOur team uses Hygraph to push breaking news stories to our project's webpage. The project is a part of a large non-profit initiative and the goal is to feature current content (news stories, celebrity endorsements). Authors are able to quickly add content to the CMS without sacrificing the high quality our readers expect.
Matthew F. Manager, Social Good
Highly Granular Permissions System
Until now, Custom Roles allowed setting Management API permissions, such as reading environments, creating tokens, and reading stages. With this new rollout, permissions can be set for the Content API, allowing more flexibility in defining who is permitted to perform which action within a 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.
