Publication Safety
ADMINISTRATOR
Publication safety is the last line of governance before content leaves the system. Every gate here refuses before an external send rather than repairing afterwards.
Publication safety configuration. Settings shown are point-in-time examples.
Controls
- Global publication enablement — a single switch that determines whether external execution is possible at all.
- Dry-run posture — executions are simulated and recorded without contacting the platform.
Safety gates
| Gate | Refuses when |
|---|---|
| Workspace membership | The acting user is not a member of the owning workspace |
| Cross-workspace refusal | Content, account, or asset belongs to a different workspace |
| Account ownership | The destination account is not owned by the workspace |
| Asset ownership | An attached asset is not owned by the workspace |
| Destination eligibility | The destination is inactive, unmapped, or not approved |
| Approval requirements | The current version is not approved |
Every refusal is recorded as failed before send, with the reason, in Publications.
Generation, approval, scheduling, and publication are separate decisions. Enabling one never implies another. Keep global publication disabled until readiness reports no blocked checks and the acceptance criteria in Getting Started are met.
Recommended pilot posture
- Keep global publication disabled.
- Run dry-run executions and inspect the resulting records.
- Confirm destinations, ownership, and approval behave as expected.
- Enable publication deliberately, for a limited set of destinations, once the evidence supports it.
Was this helpful?
Last updated 1 month ago