Admin / Editor · Allow about 8 minutes
Before you begin
Owner or Admin for connector setup and import review; Editors can review and publish articles they are authorised to edit. Start with a small pilot batch and know which source content you are allowed to copy.
1. Find the imported drafts
For Google Drive or Confluence guided imports, finish the selected-source previews and inspect the import progress and failures.
Open Review imported drafts from the guided import, or Settings → Integrations → Needs review.
Check the source and destination knowledgebase. Do not interpret a successful connection or completed import as approval to publish.
For direct document, folder, CSV, or ZIP imports, use the per-file result and open successful drafts in Content Manager. Review any partial failures separately. CSV article bodies, titles, and tags are checked before drafts are created; titles may contain at most 180 characters and each tag at most 40. Invalid or oversized content is rejected rather than cut off. Split oversized content into shorter articles and retry.
2. Inspect content and audience
Read the complete draft. Check the title, summary, headings, lists, tables, links, images, and attachments against the source.
Resolve conversion warnings and replace missing or unsupported content. Test links with the intended Reader access rather than your source administrator account.
Open Article properties and check the knowledgebase, category, owner, tags, and visibility. Private source permissions do not automatically establish an appropriate Beetl audience.
For connector-managed content, check source ownership and sync behaviour before local editing. Use the offered detached local-copy workflow when local ownership is intended.
Approve the reviewed connector draft for Beetl using the review workflow. Approval and publication are separate actions.
3. Publish a checked pilot
Open the checked article in Content Manager, preview it, and choose Publish when the required fields and intended audience are correct.
Open the live Reader article as an intended Reader. Check navigation, search, formatting, media, and access.
Repeat the review for the remaining drafts only after the pilot meets your standard. Recheck changed source content after subsequent imports or syncs.
Check your result
Only checked content is published, with an audience that has been reviewed independently from source-system permissions.
If something goes wrong
Import finished but the Reader article is missing: confirm review and publication separately.
Some documents failed: inspect each failure and retry the affected batch; successful drafts do not need to be imported again blindly.
Links or attachments are missing: resolve the conversion warning or source access before publishing.