> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/create-and-publish/production/content-hub/set-brand-guardrails.md).

# Set brand guardrails

Define the tone, audience, calls to action, banned phrases, and brand briefing for every generation.

Use this task to tell Content Hub how your brand sounds. The guardrails in **Brand Settings** apply to every generation in Content Hub, for example in Text Composer, Clipper, and Quote Finder.

## Before you start

* You need Content Hub access. See [Get started with Content Hub](/documentation/create-and-publish/production/content-hub/get-started-with-content-hub.md).
* Any user with Content Hub access can edit the guardrails.
* Podigee stores guardrails one time for each organization. An account without an organization stores them one time for each user. All podcasts of the organization or user share the same guardrails.

{% tabs %}
{% tab title="Classic view" %}

### Complete the task

1. In the sidebar, select **Brand Settings**. The page subtitle reads **Tone, banned phrases and CTAs applied to every generation.** CTAs are calls to action.
2. Write a **Custom Brand Briefing** of up to 2000 characters. Describe your brand, your products and how you speak. Content Hub includes the briefing in every generation.
3. Set the **Tone**. The default is **On-brand**.
4. Set the **Audience**. The default is **General**.
5. Enter the **Default CTAs** for the end of the generated content.
6. Enter **Banned phrases**, one phrase per line. Content Hub instructs the tools never to use them.
7. Save the settings.

You can also open the same form as a dialog from Text Composer, Clipper, or Quote Finder with **Set Up Brand Voice**.

![Brand Settings page in the classic view with the subtitle, the values Tone, Audience, Default CTAs, and Banned phrases set to Not set, and the Edit button](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-206a45861b28c3245ec786a499259dc4c87d4646%2Fdoc-production-021-classic-brand-settings-page.png?alt=media)

The Brand Settings page shows the current values and opens the form with Edit.

![Edit guardrails form in the classic view with the Custom Brand Briefing field and the Tone, Audience, Default CTAs, and Banned phrases fields](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-cde27470dd5427420a77f8bbf7314870679a27a2%2Fdoc-production-021-classic-edit-guardrails.png?alt=media)

The Edit guardrails form holds the brand briefing of up to 2000 characters and the four guardrail fields.

### Expected result

The page shows **Guardrails saved.** Text Composer and Quote Finder now show **Brand voice active**, and Clipper shows **Brand briefing active**. New generations follow the tone, audience, calls to action and banned phrases. Existing assets do not change.

### If you cannot complete the task

* The page shows **Unable to save. Please check the form and try again.**: check the form fields and save again.
* A generation still uses a banned phrase: regenerate it. Text Composer offers **Regenerate Content** with instructions, and Content Hub sends the guardrails with every new generation.
  {% endtab %}

{% tab title="Podigee workspace" %}
The Podigee workspace does not include brand guardrails yet. Switch to the classic view to set brand guardrails.
{% endtab %}
{% endtabs %}

## Next step

[Generate text content from an episode](/documentation/create-and-publish/production/content-hub/generate-text-content-from-an-episode.md) with the new brand voice. For one text you can still override the tone with **Tone override**.


---

# 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://docs.podigee.com/documentation/create-and-publish/production/content-hub/set-brand-guardrails.md?ask=<question>&goal=<endgoal>
```

`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.