> ## Documentation Index
> Fetch the complete documentation index at: https://velurahq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Brand Kit: govern every output with your brand identity
> Brand Kit stores your voice rules, audience maps, and knowledge bases so every workflow, agent task, and CMS publish stays on-brand automatically.
Brand Kit is the central layer of brand governance in VeluraHQ. Every workflow run, agent task, and CMS push reads from your Brand Kit automatically — you configure it once and the whole system inherits the rules. Unlike one-off prompt instructions that disappear when a conversation ends, Brand Kit encodes your identity, audiences, and writing standards as durable, versioned rules that travel with every piece of content your team produces.
## What Brand Kit contains
Formality level, point of view, approved terminology, and words to avoid — encoded as reusable rules that every workflow block applies automatically, not just when you remember to include them in a prompt.
Serve the right positioning for each persona, market, and product line. Define distinct audience profiles so workflows can target the correct messaging angle without manual customisation on every run.
Upload case studies, positioning documents, product specs, and FAQs so AI generation stays grounded in your approved sources. Workflows reference these documents instead of hallucinating claims.
Bake legal requirements, disclosure language, and terminology restrictions into every output path. Compliance rules apply at the workflow level — you don't need to add them manually to each brief or block.
## Setting up your Brand Kit
Open your workspace and select **Brand Kit** from the sidebar. This is where all your brand identity settings live.
Add your voice and tone rules, target audience profiles, and product lines. Be specific — the more precisely you define your formality level, POV, and terminology preferences, the more consistently your outputs will reflect your brand.
Add case studies, product specifications, brand guidelines, and any other approved reference material. Supported file types include PDFs, Word documents, and plain text files. Knowledge base storage limits depend on your plan (see below).
Specify terminology your team uses, phrases to avoid, structural requirements (such as always opening with a problem statement), and any formatting standards. These rules are enforced automatically by workflow blocks and SuperBlocks.
Save your Brand Kit settings, then run a test workflow on one or two inputs to confirm that outputs match your guidelines before scaling to a full batch.
## How Brand Kit flows through the system
Every workflow block and agent in VeluraHQ automatically pulls the relevant slice of brand context for its task — not the entire kit at once. A research block reads your knowledge bases and topic focus. A drafting block reads your voice rules, audience map, and terminology requirements. A compliance check block reads your disclosure and legal hooks. This targeted approach keeps generation focused and avoids bloating every prompt with rules that don't apply to the current task.
Workflows can also be configured to target specific Brand Kit sections, so a product page workflow uses different audience context than a thought leadership article — even when both run in the same workspace.
If you manage multiple clients, create a separate workspace per client and configure a dedicated Brand Kit in each one. This keeps voice rules, knowledge bases, and compliance hooks completely isolated — there is no risk of one client's brand context bleeding into another's outputs.
## Per-workspace isolation
Each workspace in VeluraHQ maintains its own Brand Kit. All workflows, agents, and Sheets runs within that workspace read exclusively from its Brand Kit. For agencies managing multiple clients, the recommended setup is one workspace per client, each with its own Brand Kit configured for that client's identity.
## Versioned updates
When you update a Brand Kit rule — changing a tone setting, adding a new compliance requirement, or uploading a revised knowledge base document — all subsequent workflow runs pick up the change automatically. You don't need to update individual workflows or re-prompt agents. Previous runs are unaffected and their outputs remain tied to the rules that were active at the time they ran.
For example, if you update your tone rule from formal to conversational:
```text theme={null}
# Before
Tone: Formal — use third person, avoid contractions, prefer passive constructions.
# After
Tone: Conversational — use second person ("you"), allow contractions, prefer active voice.
```
Every workflow run after you save this change will produce conversational output. Drafts already queued for review are not altered retroactively.
## Knowledge Base limits by plan
| Plan | Knowledge base storage |
| ---------- | ---------------------- |
| Starter | 100MB |
| Pro | 500MB |
| Enterprise | 500MB |
## MCP connector
If you use the VeluraHQ MCP connector, you can read and update Brand Kit rules directly from Claude without opening the workspace. This is useful for teams that prefer to manage brand context from their existing AI chat workflow. See the [MCP & Claude](/docs/integrations/mcp-claude) guide for setup instructions.