> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/advanced-features/set-up-brand-guidelines.md).
# Set up Brand Guidelines
Teach Humanic your brand voice once, and every campaign it generates will speak in your language, reflect your style, and stay on-message, automatically.
Why this matters: Humanic's AI agents generate emails autonomously. Brand guidelines help you stay in control of tone, positioning, and visual identity without reviewing every single campaign manually.
***
### How to set up your brand guidelines
**Step 1 — Open Brand**
From the left navigation, select **Library**. Then select **Brand**.
**Step 2 — Choose how to add guidelines**
Use any of the following options:
* **Upload a brand document.** Upload a PDF, Word document, PowerPoint, or text file. Humanic extracts the guidelines and saves the original file.
* **Learn from a website.** Open the assistant and provide your website. It reviews the site and fills in your guidelines.
* **Write manually.** Start with the template and add your colors, tone, typography, and style preferences.
**Step 3 — Review and complete your guidelines**
Check that the guidelines reflect your brand. Add any missing details, such as audience, messaging rules, and design preferences.
**⭐️ Pro tip:** When you're working on a campaign, chat with the agent to save reusable MJML blocks like headers and footers for easy usage in future campaigns. These can be found in your library under **Components**
***
### What to include
Think of this as a creative brief for your AI team. Here's a basic template to start with:
Create email campaigns (onboarding and newsletter) that welcome new customers, drive product purchase interest, and promote campaigns, offers, and new products. Do not ask follow-up questions; make assumptions independently.
Target audience: \[audience]. Core selling point: \[value proposition].
Use \[Brand] visual identity, including official fonts, colors, and styles. Use a \[color] background throughout the email design.
Tailor all copy and tone for \[audience]. If writing in English for a non-English-speaking market, ensure the tone is respectful, clean, and precise.
**Be specific about your audience**
Instead of "professional tone," say "respectful and direct, appropriate for mid-level SaaS marketing managers in North America." The more precise the persona, the more targeted the output.
**Define your campaign types**
Tell Humanic which emails you create, such as onboarding sequences, newsletters, re-engagement, or promotions. This shapes the campaign structure and cadence.
**Include design preferences**
Specify color schemes, image preferences, and header or subject-line conventions.
**⭐️ Pro tip:** Be explicit about what the AI should not do. Negative constraints like "never lead with discounts" or "do not use informal slang" are just as powerful as positive ones.
{% hint style="info" %}
State what Humanic should avoid. Rules like “never lead with discounts” are as useful as positive guidance.
{% endhint %}
***
### What makes strong brand guidelines
Strong guidelines answer three questions.
**Who am I talking to?** Audience, market, and language preferences.
**What do I want to say?** Campaign goal, product focus, and core value proposition.
**How should it look and feel?** Tone, design style, and formatting rules.
Clear guidelines reduce guesswork and improve every campaign.
***
### Frequently asked questions
**What can I upload?**
Upload PDF, Word, PowerPoint, or text files. Use brand playbooks, product documents, and style guides.
**Can I have different brand guidelines for different campaigns?**
The brand guidelines set global defaults. You can override or extend them per campaign by describing your specific requirements directly in the campaign prompt.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://humanic.gitbook.io/humanic/advanced-features/set-up-brand-guidelines.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.