concept · explanation
Knowledge base and brand voice
Understand how knowledge base and brand voice works in Slash Social.
Approved knowledge keeps AI drafts, replies, and templates aligned with how the brand should sound. Admins maintain source material once; creators and automated flows pull it at generation time.
Overview
Slash Social separates what the brand knows (knowledge base entries and linked Canvas documents) from how the brand sounds by default (configuration in branding and learning domains). Both feed generation, reply suggestions, and related AI flows for the active brand. Stale or missing knowledge produces drafts that drift from your positioning.
The Knowledge Base hub lives under Settings in /social. That is where you create entries, filter by scope and type, link Slack Canvas documents, and control which entries participate in AI context.
Open the hub from the Settings card, then use scope and type filters to narrow long lists. Search helps you jump to an entry by title when the library grows.
How it works
Knowledge base entries store organization and brand material: positioning notes, product facts, tone rules, objection handling, and other prose creators and AI should respect. Each entry has a type, title, body, and scope filters you set in the hub.
You can include or exclude an entry from AI context with a toggle without deleting the source. Archive removes an entry from active retrieval while keeping history. Edit updates title, body, and metadata. Scope and type filters help you navigate large libraries.
Brand voice also lives in configuration. The branding area carries voice, tone, palette, and assets. The learning area carries preferences that influence draft suggestions. Configuration inheritance applies: brand overrides sit on organization defaults, and campaign or pillar settings can refine further.
Knowledge entries and branding config work together. Entries carry factual and stylistic prose; branding config carries structured defaults the product merges when building a draft.
Slack Canvas knowledge links a Canvas document to an entry. Link Canvas stores the URL on the entry. Sync Canvas refreshes the entry body when the upstream Canvas changes. Canvas operations require appropriate Canvas permissions in the workspace. Use Canvas when policy docs already live in Slack and should stay the single source of truth. Use standalone entries when you maintain content entirely inside Slash Social.
Creators do not paste knowledge into every draft. Generation and reply flows pull eligible entries for the active brand, plus org-wide entries when scoped that way. Toggle AI off on sensitive entries until they are ready for automated use.
Examples
An admin adds a “Product positioning” entry at brand scope with tone rules and a competitor contrast paragraph. A creator opens Create and generates a LinkedIn post; the draft references the positioning without manual copy-paste.
A compliance doc already lives in a Slack Canvas. The admin links it to a knowledge entry and runs sync after legal updates the Canvas. The next generation pass uses the refreshed body.
Voice and tone defaults live in branding config at brand scope. A campaign-specific learning override nudges variant selection for a launch week while factual claims still come from knowledge entries.
An admin archives an outdated pricing entry instead of deleting it. Historical drafts remain traceable, but AI context stops pulling the old numbers after archive.