Roles
Creating custom roles allows an administrator to restrict the access of users to certain resources. Roles follow an “allow list” approach, which means that you need to define everything a user is allowed to do. A role contains a name, description, permissions and policies.
Permissions can be basic rules which define whether a user can read or create content types, settings and entries.
The following permissions are supported:
and each of those permission can have the following values:
You can also create policies to allow or deny access to resources in fine-grained detail. With these polices you can, for example, limit read access to only entries of a specific content type or write access to only certain parts of an entry (e.g. a specific locale).
For information on how policies are specified, refer to the programmatic role management guide.
Roles collection
This endpoint returns a paginated list of roles for a given space. Each role contains a name, a description, permissions and policies, which describe what a user can and cannot do.
Use this endpoint to create a custom role. The role name must be unique within the space.
Role
Use this endpoint to read an existing single role.
Use this endpoint to update an existing role. You cannot use the endpoint to create a new role with a specific id.
Use this endpoint to delete an existing role. You can only delete roles if there is no user in the space with only that role assigned, i.e. a user must have at least one role.