The review queue
Nothing publishes without a person on your side approving it.
- One list of everything waiting on a human decision
- Approvals record who approved what, permanently
- A decided item cannot be silently re-decided
What lands here
- Proposed rewrites — a regenerated version of one page, produced because the Docs Score flagged it.
- Authored artefacts — curricula and courses an author has submitted for review.
Both ask the same question: is this good enough to put in front of our people?
Deciding
Approve publishes the item and records who approved it. Send back returns it to draft, changing nothing that is live.
Decisions are written to your organization's audit trail, and a publication is announced on the internal event stream so monitoring and the academy build both learn that content changed.
Why the gate exists
Generated content is a proposal, not a publication. Your organization is accountable for what its documentation and training say, so the decision — and the name against it — stays with a person on your side. This is also why a decided item cannot be quietly re-decided: an approval record that could be rewritten would not be worth keeping.
Safety
Proposals are derived from your own corpus. They are shown as plain text, never rendered as markup, and never fed back to the system as instructions.
Frequently asked
Who can approve?
Owners, org admins, enablement managers and reviewers. Authors can watch the queue and follow their submissions, but cannot approve them — including their own.
What happens when I send something back?
It returns to draft. Nothing is deleted, the author keeps the work and its history, and the current live version is untouched.
Can an approval be undone?
A published course can be unpublished or archived by a reviewer, which is recorded like any other decision. A decided rewrite proposal cannot be re-decided at all — the database refuses it, so the approval record stays truthful.
Why do AI-proposed rewrites need approval at all?
Because you are accountable for what your documentation says. Generated content is a proposal, never a publication: a person on your side decides, and the record of who decided is kept.
Related guides
The tracks your corpus compiles into, and the lifecycle every piece moves through.
ReadA 0–100 rubric score for your documentation, with a fix queue ordered by impact.
ReadWhat miatz reads from your documentation, and what it turns that into.
Read