Separate Production from change work
Each content environment isolates content, media publication state, delivery credentials and environment-local configuration. Choosing an environment is intent, not a grant of access.
How to use it
- The Owner creates or inspects environments in Management → Environments within the plan allowance.
- Use the navbar select to switch environments and verify the new label before proceeding.
- Configure consuming websites with the selected environment's credentials; verify the returned workspace/environment identity.
Good practice
- Try structural and editorial changes in an isolated environment before Production.
Avoid
- Do not reuse another environment's key or assume switching changes only a visual badge.
Review controlled content and media promotion
Promotion moves a reviewed set of changes between environments. It must account for schema compatibility, references, media and target changes.
How to use it
- Open Environments → Promote content and choose the intended source and target.
- Select the authorized content/media scope, inspect the plan and conflicts, and complete the required review confirmations.
- Apply the reviewed promotion only while its source and target checks remain valid.
- Inspect target drafts and publish separately when ready; promotion preserves existing target public snapshots and does not copy approvals, schedules or keys.
Good practice
- Resolve target conflicts intentionally; include required dependencies and remember that promoted entries and media remain drafts until explicitly published.
Avoid
- Do not assume promotion copies users, integration secrets, API keys or unrelated workspace configuration.
Export or import a portable content bundle
Transfers are bounded, permission-checked operations for portable model/content/media data. A bundle can contain private editorial data even when it contains no API keys.
How to use it
- Open the transfer controls from Environments and choose the supported schema/content scope.
- For export, review scope, wait for completion and download the bundle through your authenticated session.
- For import, upload a supported bundle, inspect validation and conflicts, and explicitly approve the proposed operation.
- Keep the target stable while applying a reviewed import, then inspect its resulting content and history.
Good practice
- Treat exported bundles as private files with a retention policy and share them only with intended operators.
Avoid
- A portable content bundle is not a full backup of accounts, credentials, storage infrastructure or application code.