[Draft]Elite Plan

Multi-Space Content Distribution

Collaboration
Content Authoring
Internationalization

Storyblok dashboard showing shared assets, including image thumbnails labeled "Joy" and "Amsterdam," with navigation menu on the left.

Multi-Space Orchestration launches with its first capability: Multi-Space Content Distribution, giving content teams a native way to distribute and keep content in sync across multiple spaces — without relying on manual, developer-driven workarounds.

This feature brings the familiar Dimensions App workflow (clone, overwrite, and merge) to content distributed across multiple spaces in an organization.

What's new

Organization-level configuration
- Enable the feature and select participating spaces
- Define one-directional workflows (for example, a source-of-truth space that pushes content, but never receives it)
Clone across spaces
- Clone any story to another participating space, maintaining the same relative folder path
- Missing folders are created automatically in the target space
- Source and cloned stories are automatically associated with one another across spaces
Content association
- New organization-level grouping mechanism links all versions of a story across spaces
Distribute from the Visual Editor
- In the Visual Editor, the Distribute section equivalents to the current story in available other spaces
- Clone, overwrite, and merge actions are available
- The status of each connected story is visible
Update via overwrite or merge
- Overwrite replaces a target story's full content and structure with the source story
- Merge updates only the block structure, preserving the target story's existing content

Prerequisites

Participating spaces must have consistent (or shared) component schemas for distributed content to map and render correctly. This is not yet validated automatically.
Users must have permission to create and edit content in both the source and target spaces to perform clone, overwrite, or merge actions.
Distributed content is not automatically published in the target space; it must be reviewed first

Known limitations

Content and asset references are not automatically updated. Editors must review and update these manually to ensure content renders correctly.
Bulk actions are not currently supported.

What to expect in future iterations

Easier updating of content references during the distribution action
AI-powered translation when cloning content
Manual management of content associations
Cross-space visibility surfacing content status at a glance
Additional improvements based on customer feedback

Multi-Space Content Distribution is available now on the Elite Plan, and as an add-on for other plans. Interested organizations can enable it from Organization Settings → Content Distribution.

Learn More

Related Updates

[Draft]Elite Plan

Environments

Collaboration
Developer Experience
Content Authoring

You can now create an environment — a place for safely testing automation tools (like FlowMotion or the Storyblok MCP Server), workflows, and configuration changes without touching production. As teams are increasingly adopting automation tools directly inside their production spaces, we're releasing this initial version to get a safe place to test automations into your hands quickly to reduce the risk of unintended changes, and we'll be expanding the Environments capabilities based on what we hear from you. This is the first step in a longer roadmap we'll build with you. In this first release, the feature introduces: Environment creation: a new setup flow lets you configure your new Space with options to decide what you'd like to bring from your Space to the new environment, including:Whether to recreate custom roles and user access assignmentsWhether to duplicate the component structure or use the Shared Components App insteadWhether to carry over asset folder structure and internal tags (note: assets themselves are not duplicated)Environment switcher: a new sidebar component to see which environment you're in and switch between environments tied to the same production space.Environment Scoped Personal Access Tokens: tokens can be restricted to a specific environment to keep your production Space safe. How it works: The environment has access to the same functionalities as the main SpaceThe environment automatically duplicates the content, components, and datasources from the main Space. Duplicating custom roles and user access assignments during environment creation is optional.Usage inside an environment (AI credits, storage, traffic) counts toward your organization's overall quota.1 Environment per Org is included at no additional cost for Elite Plan Organizations. Additional paid Environments are available for Premium & Elite Plans. For this initial release, there is no visual tool to promote the changes, but it can still be done via CLI. Also, Apps configuration, releases, pipelines, workflows/stages, and other items are not yet duplicated during the Environment creation — support for these is considered for future iterations. Learn More

NewJuly 20, 2026Premium Plan

Workflows for field-level translations

Collaboration
Workflows
Internationalization
Content

Spaces using field-level translations can now run a separate workflow per language. Until now, a story had one workflow for all languages where a stage that fit default language applied to every other language too. Teams that needed to translate, review, and publish languages on different schedules had to work around a single shared state. Add a "workflow for languages" to a workflow and configure per-language stages, colors, content rights, and transitions. Language variants show in the Workflows page, the Visual Editor, and the Content list. Assignees are still global so you cannot assign a different person per language variant. Key Benefits: Translate, review, and publish each language on its own schedule Regional teams work in their language variant without blocking others Approvals and content rights map to the language, not the whole story [Learn more]