Publication and readership
Zendesk knowledge article settings distinguish management permissions from viewing audience. An agent allowed to edit or publish is not the same thing as a customer allowed to read. An article also needs section placement.
For an original example, create an internal troubleshooting article for Larch Channel. Choose the Billing section, an authorized manager and an agents-only audience. Save as a draft. Preview can help review the result, but it does not publish it. Use the explicit publication action only after the content and audience are approved.
Permission mistakes
If the article is set to Everyone, restricting managers will not make it internal. Correct the viewing audience and verify the published read-back. Conversely, selecting a private audience does not grant an otherwise unauthorized agent permission to edit or publish.
The real product offers account- and plan-dependent management and user-segment options. The local Zendesk course uses a disclosed small configuration; publication changes only its fictional article state and creates no external URL.
Support evidence
A support ticket may reveal a missing article, but remove customer identifiers and internal diagnostics before drafting customer-facing help. Keep the approved source and revision owner. For a reply that uses an existing approved article, practice macros and verify the public/internal audience before Submit.