Other than system roles, Project Admins and Owners can set up custom roles, each with their own defined set of permissions for content and Hygraph project management.

Define granular permissions for every role in terms of what content they can access (exact models, stage, locales, environments, etc.) and what actions they can perform (read, create, update, delete, publish, unpublish).

Add conditional checks to your permission settings to grant access based on actual field values.

Create custom stages other than the default DRAFT and PUBLISHED stages and map your internal editorial workflows. Combine these with granular permissions to define which users can read and move content for every particular stage.

You can opt to expose your content API to the public and allow developers to query without worrying about authentication. You can selectively choose what permissions are available for the publicly exposed API.

It might be useful to enable public API access if you are storing statistical data that doesn't identify the person it belongs to — an example of this may be the number of Covid-19 cases and deaths recorded in your country, which you want to show on a map or graph.

You can create multiple Permanent Auth Tokens per project, each with its own set of permissions on both the content and management API. Each PAT can have granular permissions defined with conditional checks as well.