Skip to content

Manage Roles

Roles let space owners and admins control users’ access to resources within a specific space. A role is a set of permissions associated with one or more users.

Each space includes default roles with predefined permissions that you can’t change:

Role Permissions
Admin Manage users, content, apps, and any other aspect of the space.
Editor Manage content, assets, and tags.
Create and view datasources.
Owner All admin-level permissions.
Can manage subscriptions and grant similar access to Admin and Editor roles.

Space owners and admins can also create custom roles to match the project’s content requirements and the organization’s editorial team. Use custom roles to apply granular permissions and assign them to individual users.

To create new custom roles or manage existing ones, open Settings → Roles. Choose an existing custom role and update its permissions, or select + Add new role and configure relevant options and permissions.

To configure single sign-on (SSO) integration, select This role is for integration with SSO and provide the necessary information.

Custom roles are an efficient way to define which users can perform specific actions.

For example, an admin of a multilingual project can assign a German translator role to users who need full access to German content and read-only access to English content.

Different types of users—such as developers and designers—may have their own roles, granting them access to edit blocks and upload assets, respectively.

To assign roles to users, open Settings → Users and select the relevant person. Then, choose Single role or Multiple roles and select the appropriate roles from the drop-down.

Conflicting permissions for multi-role users

Section titled “Conflicting permissions for multi-role users”

A user can have multiple roles in a single space and different roles in other spaces. This has a notable consequence.

If a user has multiple roles, where one role can access specific resources and another can’t, the role without access takes priority. For example, User 1 has both Role A and Role B. Role A can access Story 1, but Role B can’t. In this case, User 1 can’t access Story 1.

When two roles have conflicting permissions, the deny status prevails

Permissions determine which resources and actions a role (and therefore users assigned to it) can access.

Storyblok supports an extensive list of permission levels, allowing admins to manage access to stories, blocks, fields, assets, languages, datasources, tags, and apps.

To view or set permissions available on your plan, open Settings → Roles, and select the role. Each tab covers different permissions configurations:

Tab Description
General • Allow or deny actions in stories, folders, and pipelines.
• Allow or deny access to the Visual Editor and stories’ JSON payload.
• Hide all stories or folders.
• Allow or deny managing tags.
• Allow or deny editing datasources’ values and keys.
• Allow or deny access to an e-commerce app (if installed).
• Allow or deny performing actions in the Task Manager app (if installed).
Content Manage access to selected languages, pipelines, folders, and stories using an allowlist/denylist.
Blocks • Grant access to the block library.
• Manage access to selected blocks and block folders using an allowlist/denylist.
• Manage access to selected block fields using an allowlist/denylist.
Datasources Manage access to selected datasources using an allowlist/denylist.
Assets • Manage access to selected asset folders using an allowlist/denylist.
• Allow or deny actions in assets.
• Allow or deny access to the Image editor.
• Allow or deny actions in asset folders.

By default, the role can access any resource that isn’t explicitly restricted.

Folders, subfolders, and individual resources

Section titled “Folders, subfolders, and individual resources”

Storyblok supports organizing stories, blocks, and assets in folders. For stories and blocks, the permissions settings use a separate allowlist/denylist for individual items and the folders that contain them. For assets, permissions apply to asset folders.

Applying granular permissions to individual items and folders is a powerful way to limit access to restricted resources. Sometimes, you may want to automatically extend these permissions to all resources stored under the same parent folder. To do that, select the option for each resource type

  • Blocks → Apply permissions to sub-items.
  • Assets Automatically apply permissions to asset subfolders.

Most permissions settings support allowlists and denylists that enable admins to create complex permission schemes:

  • To limit access to specific resources, use a denylist. Everything else is accessible.
  • To grant access only to specific resources, use an allowlist.
    • To hide other resources, pair this with the Hide content if unauthorized and Hide folders if unauthorized options in the General tab.

The difference is subtle, so the approach you adopt depends on the nature and sensitivity levels of your content, as well as your team’s organizational structure.

Was this page helpful?

What went wrong?

This site uses reCAPTCHA and Google's Privacy Policy (opens in a new window).Terms of Service (opens in a new window) apply.