Role-Based Access Control (RBAC)

Strapi Page Builder uses the built-in Strapi Role-Based Access Control (RBAC) system to control user permissions. This allows you to control which users have access to the Strapi Page Builder editor and what changes they can make.

RBAC permissions are set in the Strapi admin panel under Settings > Users & Permissions Plugin > Roles. Here you can create new roles or edit existing roles to set the permissions for the Strapi Page Builder editor.

Four levels of permissions are available:

• None: No access to the Strapi Page Builder editor.
• Access Page Builder: Access to the Strapi Page Builder editor, but no ability to make changes. Read-Only access.
• Edit Template Content: Access to the Strapi Page Builder editor with the ability to make changes to content, but not template shape. This is ideal for translators or content editors.
• Add & remove template components: Access to the Strapi Page Builder editor with the ability to make changes to both content and template shape. This is ideal for developers or designers.

A separate permission, Access the Page Builder settings (under Settings in the same roles screen), controls who can change the API key and the editor URL. Users without it see the API key masked and cannot save settings.

Content permissions

Strapi Page Builder respects the Content Manager permissions of the editing user. For a Strapi field in a component, the editor can only list and pick entries of content types that the user has the Read permission for. Give editors Read access to every content type your components reference, such as products or categories. Users, admin and other system content types are never available.