Help articles your team writes once, customers find on their own
Draft and publish help articles from the CRM — published ones go live instantly on your tenant's public support portal.
Knowledge base articles are written and managed from /crm/knowledge: a title, a body, an optional category, and a publish toggle. Draft articles are only visible to signed-in CRM users; publishing an article makes it immediately and publicly readable at your tenant's portal, with no separate deploy step. Each article gets a URL-safe slug generated from its title, which is what both the CRM and the public portal use to look the article up.
Draft and publish, in one click
Every article carries a published boolean shown as a "draft" or "published" badge in the CRM list. Toggling it is instant — no review queue, no separate publish action beyond the one button.
- New articles can be created already published
- Unpublishing an article immediately removes it from public reads, without deleting it
Auto-generated, stable slugs
A slug is derived from the article title (lower-cased, non-alphanumeric characters collapsed to single dashes) and is what the public portal URL is built from. Editing the title regenerates the slug, so a shared link can change if the title changes later.
Public, tenant-scoped reads
Public endpoints only ever return published articles, and only for the tenant they're requested against — there's no way to list or read another tenant's articles, published or not.
- List published articles for a tenant (with title, slug, category)
- Read one published article by tenant + slug (title, body, category) — no authentication required
Optional categorization
Articles can carry a free-text category, shown as a label next to the title both in the CRM list and on the public article page, useful for grouping related help content without a rigid taxonomy.
- Publish answers to your most-asked support questions once, instead of retyping them
- Deflect repeat tickets by linking customers straight to an article
- Keep drafts private while you write, then flip them public when ready
Knowledge base — common questions
Only authenticated users of your CRM workspace. Public reads always filter to published articles only.
Not directly — the slug is regenerated from the title every time the article is saved, so keep the title stable once you've shared a link.
Article bodies are stored and rendered as plain text with line breaks preserved; there's no markdown or rich-text formatting layer today.
Yes. Every article belongs to one tenant, and public list/read endpoints require a tenant slug — there's no shared or global article library.