Storyblok application
Storyblok is a headless CMS. MIA connects to it to inventory a space's collaborators and manage their access, including assigning multiple custom roles.
Authentication type and prerequisites
Authentication type — Personal Access Token
Prerequisites
You need a personal token allowed to manage the Storyblok space's collaborators. When creating it, use one of the following configurations:
- enable Full user permission to allow every space and scope;
- preferably, restrict the token to the relevant spaces and grant only Collaborators: Read, Collaborators: Write, and Spaces: Read.
MIA does not use any other scope. In particular, Spaces: Write is not required.
Connection steps
- In Storyblok, open your account settings and generate or copy a Personal Access Token with the permissions listed above.
- In MIA, open Applications → Add an application, search for Storyblok, then enter the token.
- Click Connect, then select the space from those loaded from Storyblok.
MIA automatically stores the space ID and region so it can use the matching API endpoint.
Roles and permissions
When adding a user, MIA loads custom roles directly from the Storyblok space. The Roles field supports multiple values; MIA automatically enables Storyblok's multi-role API mode.
Available permissions are derived from the roles currently configured in the space. The built-in Admin and Editor roles are also available, but a built-in role must be selected on its own.
WARNING
Custom roles and some permissions depend on your Storyblok plan and space configuration.
Managed data
- Read collaborators, including pagination
- Invite a collaborator with one or more roles and permissions
- Delete a collaborator
See the official Collaborators API reference.