Skip to the page

DocsKnowledge base

DocsKnowledge base

Help articles

Draft support articles from your customer-facing sources, review and publish them, and keep them right as sources change.

Business plan and aboveFor owners, admins and support agents

Help articles are what customers read in a project’s support portal. Claude drafts each one from your customer-facing sources, and nobody outside your team sees it until one of you publishes it.

Open Knowledge › Articles in the sidebar. Owners, admins and support agents write, review and publish. Other members can read the articles there.

Drafting and reviewing work on the Team plan. Publishing needs Business.

Draft, review and publish a help article

Before you start#

An article can only be drafted from sources that are customer-facing for its project: Customers is ticked under Who it’s for, and the project is one of the source’s projects. If a project has none, the New article dialog says so. Set that up first in Add sources.

Draft an article#

  1. Choose New article.
  2. Choose the Project it’s for.
  3. Choose what to draft from:

    • A topic: a question or subject, the way a customer would put it. Claude finds the passages that cover it.
    • A source: one document or page, turned into an article.
  4. Choose Draft it.

Drafting takes a moment and runs in the background. You’re told in the bell when it’s ready. Each draft uses your AI allowance.

If nothing customer-facing covers the topic, the draft fails and says why. Add or update a source, then choose Try again.

Review and edit#

The draft opens beside Sources: the passages it was written from. Check that the article says what they say. Numbered markers in the body show which source each part came from. They’re removed when customers read the article.

You can edit:

  • Title and Summary. The summary shows in the portal’s article list and search results.
  • Body, in Markdown, with a Preview tab.
  • Address: the last part of the article’s address in the portal.
  • Projects: only projects that every cited source is customer-facing for can be ticked.
  • Categories: customer-visible ones only. Those suggested from the sources are marked Suggested.

Things to check#

Projik flags anything in the draft that often shouldn’t reach a customer: an email address, a phone number, a link that isn’t in the cited sources, or something that looks like a password or key. Show finds it in the body. Edit it out, or choose It’s fine to dismiss it. An article can’t be published while any are open.

Statuses#

StatusMeaning
DraftBeing written or edited. Only your team sees it.
In reviewReady for someone to read and publish. Only your team sees it.
PublishedLive in the portal for its projects.
ArchivedTaken out of use. It can be restored as a draft.

Save draft keeps your edits. Move to review saves them and moves the article on.

Each tab lists its articles. Search their titles, and narrow the list by Projects (tick as many as you like) and by category. An article shows when it’s for any of the projects you’ve ticked.

Publish#

On an article that’s In review, choose Publish and confirm. Customers of its projects see it in the portal straight away. Your name is recorded as the approver.

As you publish, Projik checks again that:

  • every cited source still exists and is customer-facing for every project the article is for
  • each project still exists, and the article has at least one
  • every category is still customer-visible
  • no things to check are left open

If any check fails, the article isn’t published and every reason is listed. Fix what it names, or choose Draft again to start over from the same topic or source.

Editing a published article works the same way. Save and republish puts your changes live at once, after the same checks.

Take an article down#

Choose Archive. A published article leaves the portal immediately. Restore, in the Archived tab, brings it back as a draft to review and publish again. It never goes straight back to the portal.

How articles appear in the portal#

Once a project has a published article, its portal gains a Help articles tab and opens on it. Customers can search, browse by category, and see up to three matching articles under These might help as they type a new ticket’s subject. Search there matches words. It isn’t AI, and it never reads your sources.

Customers see the title, summary and body. They never see the sources, the things to check or who approved it.

Who can read articles is one setting for the workspace, in Settings › Knowledge under Who can read published support articles. Owners and admins change it.

  • Signed-in customers: only customers with access to that project’s portal. The default.
  • Anyone with the link: articles are public and search engines can find them. Tickets still need a sign-in.

See What your customers see.

When a source changes#

  • A cited source is updated. The article stays live and moves to the Needs a look tab, with what changed. Compare it with the source, then edit and save it, or choose Still right.
  • A cited source stops being for customers, is taken off one of the article’s projects, or is removed. The article is taken down at once and goes back to In review, marked Taken down with the reason. When the change is to who the source is for, you’re warned and asked to confirm first.
  • A category is made staff-only or deleted. It comes off the article. The article stays published.

As a last check, the portal looks at an article’s sources every time it’s read, and won’t show one whose sources no longer qualify.

On a plan without publishing#

Published articles stay up, and customers can still read them. You can’t publish anything new or edit a published article, since an edit goes live as it saves. You can still archive one, and write and edit drafts. See Plans and billing.

    Type to search every page. ↑ ↓ to move, Enter to open.