Admin · Allow about 20 minutes
Before you begin
Owner or Admin, an Editor responsible for content quality, and a test account with the intended Reader permissions. Agree whether the knowledgebase is public or private and who owns launch support.
1. Confirm the audience and access
Open the knowledgebase settings and confirm its name, intended Reader address, active status, and public or private visibility.
Check workspace roles, groups, and knowledgebase grants. Use a representative Reader account rather than relying on the Owner’s view.
For a public launch, test without signing in as well as with a member account. Confirm private articles, working drafts, and unpublished media remain inaccessible.
2. Check the published content
Use Content Manager to check the intended launch articles, category structure, owners, and review dates. Complete or defer unfinished content deliberately.
Check the published Reader versions, not just the editor’s working copies. Validate links, meaningful image alternatives, attachments, and any embedded activities.
Run common searches and one known-article lookup as the intended Reader. Check cited sources if the Assistant is enabled. Resolve missing answers or access problems before inviting everyone.
3. Verify the Reader experience
Preview the selected Reader theme and branding. Publish the approved design through Brand Kit → Review & publish → Publish Reader design when ready.
Open the real Reader address on desktop and a phone-sized screen. Test navigation, search, article reading, media, and feedback.
If using a custom domain, verify its configured Reader route and certificate status before sharing it. Keep the current working Reader address available while setup is incomplete.
4. Check learning and hand over
If launching assigned learning, check the approved published journey revision and test its required activities. Preview and review the rollout audience and timing before launching it.
Confirm where learner evidence will be reviewed, who handles access questions, and who will investigate unanswered questions after launch.
Record the tested Reader address, audience, outstanding issues, and content owner. Invite the pilot group first, resolve issues, and then expand the launch.
Check your result
The intended audience can use the approved published knowledgebase, and launch owners know how to handle access, content, and learning follow-up.
If something goes wrong
It works for an Owner but not a Reader: check grants, publication, and the actual Reader route using the test Reader account.
Branding appears only in preview: publish the Reader design, then reload the Reader address.
An activity appears complete only in preview: test the supported live placement or learner assignment and inspect the saved record.
Launch checks reveal unfinished setup: use a limited pilot and resolve the blocker before broad invitations rather than exposing private content to make a test pass.