Skip to main content
A promotion policy sets the conditions a change must meet before it can become live in an environment. Each environment has its own policy, applied separately for prompts and for routing rules. The policy belongs to the destination environment — it governs what’s allowed to move into production, not what leaves staging.

​
How promotion works

You promote a change from the surface where it lives:
  • Prompts — the Releases tab in the prompt editor.
  • Routing rules — the Environments tab on a routing rule’s detail page.
From there you pick the version to promote, choose the target environment, and enter a reason for the change. to11 evaluates the target environment’s policy before the change goes live. If the policy is satisfied, the version becomes the one that environment serves. If the policy requires approval, the promotion is recorded as a pending release that waits for sign-off — see Release approvals.

​
Policy options

A promotion policy can require any of the following:

​
Configuring a policy

Promotion policies are set per environment in the dashboard at Project → Settings → Environments, in the Promotion policy section of the environment editor.
Editing a promotion policy requires the env:policies:manage permission. See Roles & permissions.

​
Next steps

Release approvals

Require sign-off before a change applies.

Scheduled changes

See changes queued to apply later.