Approval gates are the checkpoint between "ready to publish" and "published". They are what makes LD3 draft/approval-first by default.
How a gate works
Publication of external posts is held until a named approver confirms*. The gate records:
- Who* approved.
- When* they approved.
- Which channel* the post goes to.
That decision is written onto the content package, so the audit trail is part of the artefact, not a separate log.
Part of Ottili ONE
LD3 approvals use the same approval model as the rest of Ottili ONE. If your organisation already routes AI actions and publishes through an approval queue, LD3 fits that flow rather than inventing its own.
Levels and gates
At the default publishing level (L1), every external post hits a gate. Higher levels can relax this within the limits you set — but the trail is always recorded.
Related
- LD3 publishing levels — how much automation a gate allows.
- LD3 reviews — the editorial check before the gate.
Was this article helpful?