RichText v5

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, storage, traffic) counts toward your organization’s overall quota.One environment per organization is included at no additional cost for Elite plan organizations. Additional environments are available for Premium and Elite plans.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

OAuth 2.0 Scoped Grants are now available for custom integrations connecting to the Management API. Instead of relying on long-lived personal access tokens, integrations can request clearly defined permissions that users review and approve on a consent page. Scopes are set at the resource-action level using a publish, write, and read hierarchy, with per-space selection, short-lived access tokens, rotating refresh tokens, and immediate revocation. OAuth 2.0 Scoped Grants are available on Premium and Enterprise. [Learn More]