Docs / Get started
Reviewing and publishing drafts
Where AutoKnowledgeBase drafts appear in Zendesk, how to publish a new article, how to apply a proposed update to a live article, and what to check before you publish.
AutoKnowledgeBase never publishes anything. Every new article and every update arrives in your Zendesk help center as a draft, and someone on your team decides what goes live. This page covers how to find those drafts and what to do with each kind.
Finding drafts
Every draft AutoKnowledgeBase creates carries the label akb-review. To see them all:
- In Zendesk's knowledge admin, open the article list, show drafts, and filter or search by the
akb-reviewlabel. - In AutoKnowledgeBase, open Article Suggestions for a list of every new article and update. Click one, then Review in Zendesk to open the draft in the Zendesk editor.
- If internal notes are on, the note on each ticket links straight to its draft. See Ticket tags and internal notes.
Creating a draft doesn't notify the section's subscribers.
New articles
A new article is a normal draft in the section that fits the ticket best. To publish it:
- Open the draft in Zendesk and read it against the source ticket. The ticket is linked from the article's page in AutoKnowledgeBase.
- Edit anything that's wrong, too specific, or missing.
- Check the article settings (see below), then publish.
If you don't want the article, delete the draft or leave it unpublished.
Proposed updates to a published article
AutoKnowledgeBase never edits a published article, because writing a draft to a live Zendesk article would unpublish it. Instead, it creates a separate draft:
- Title: [Proposed update] followed by the live article's title
- Location: the same section as the live article
- First paragraph: a notice saying it's a proposed update, with a link to the live article
To apply it:
- Open the proposed-update draft and compare it with the live article. The Diff tab on the ticket's page in AutoKnowledgeBase highlights exactly what changed.
- Copy the parts you want into the live article and publish the live article.
- Delete the proposed-update draft.
Don't publish the proposed-update draft itself. It would appear as a second article next to the original, with "[Proposed update]" in its title.
One proposed update per article
Each published article has at most one proposed-update draft at a time. While one is open, new suggestions for that article aren't added to it. They wait on the article's page in AutoKnowledgeBase, where you can still see the suggested text and the diff.
Once you delete the draft (or apply it and delete it), the next suggestion for that article creates a new one. AutoKnowledgeBase notices the deletion the next time it syncs your help center, which happens before every ticket analysis.
Updates to a draft article
If the closest article is itself still a draft, AutoKnowledgeBase writes the update straight into that draft. Nothing is published either way. Review the draft as usual before publishing it.
Before you publish: check the article settings
AutoKnowledgeBase sets these on new drafts and proposed updates. Check them before publishing, because they decide who can see and edit the article:
- Visibility (user segment): set to Signed-in users if your help center has that segment, otherwise to your first segment. If the article should be public, change it to Everyone before publishing.
- Editing (permission group): set to Admins if that group exists, otherwise to your first permission group.
- Labels:
akb-review. You can remove it after publishing. It's only there to help you find drafts.
Tips
- Review on a schedule. A short weekly session working through the
akb-reviewdrafts keeps the queue small. - Fix the template, not every draft. If drafts in a section keep coming out in the wrong structure, edit that section's template. See Section templates.
- Watch the "already covered" share. If most tickets come back as already covered, your help center is in good shape. If few do, the drafts are where the gaps are.
Last updated November 21, 2026