Allowlist & Blocklist approach

You can now create an environment—a place to test automation tools (like FlowMotion or the MCP Server), workflows, and configuration changes without touching production. Teams increasingly run automation tools directly in their production spaces. This first release gives you a safe place to test those automations and reduce the risk of unintended changes. We’ll expand Environments based on your feedback. 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 carry over asset folder structure and internal tags (note: assets themselves are not duplicated)Environment switcher: a new sidebar component to check which environment you’re in and switch between environments tied to the same production space.Environment scoped personal access tokens: you can restrict tokens to a specific environment to keep your production space safe. Learn more in the access tokens documentation. How it works: The environment has access to the same functionality as the main space.The 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, traffic, API requests) counts toward your organization’s overall quota.A limited number of environments is included in Premium and Elite plan organizations at no additional cost. Additional environments beyond this allowance are available for purchase.Environments are non-production spaces. They're not meant for live sites and come with no uptime guarantee, no custom domain support, and no production-level support. For this initial release, there is no visual tool to promote changes, but you can still promote changes via the CLI. Furthermore, environment creation does not yet duplicate apps configuration, releases, pipelines, or workflows and workflow stages—support for these is considered for future iterations. Learn More

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 configurationEnable the feature and select participating spacesOptionally, define one-directional workflows (for example, a source-of-truth space that pushes content, but never receives it)Clone across spacesClone any story to another participating space, maintaining the same relative folder pathMissing folders are created automatically in the target spaceSource and cloned stories are automatically associated with one another across spacesContent associationNew organization-level grouping mechanism links all versions of a story across spacesDistribute from the Visual EditorIn the Visual Editor, the Distribute section equivalents to the current story in available other spacesClone, overwrite, and merge actions are availableThe status of each connected story is visibleUpdate via overwrite or mergeOverwrite replaces a target story's full content and structure with the source storyMerge 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 actionAI-powered translation when cloning contentManual management of content associationsCross-space visibility surfacing content status at a glanceAdditional improvements based on customer feedback Multi-Space Content Distribution is available now on the Elite Plan. Interested organizations can enable it from Organization Settings → Content Distribution. Learn More