> For the complete documentation index, see [llms.txt](https://help.parta.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.parta.io/branding/introduction.md).

# Introduction

## Branding in Parta

Branding in Parta helps you maintain consistent visual styles across your courses. Use branding to define and manage:

* [Theme](/branding/create-branding/theme.md)
* [Typography and fonts](/branding/create-branding/typography-and-fonts.md)
* [Section](/branding/create-branding/section.md)
* [Elements](/branding/create-branding/elements.md)

{% hint style="warning" %}
Parta is designed for branding to be managed at the workspace level, and we discourage users from branding at the course level.
{% endhint %}

## Workspace-level branding

Parta is built to support branding at the workspace level, and we advise against applying branding at the course level.

<table data-header-hidden><thead><tr><th width="360"></th><th></th></tr></thead><tbody><tr><td><strong>🟢 Workspace (recommended)</strong></td><td><strong>🔴 Course (not recommended)</strong></td></tr><tr><td><ul><li>Apply changes across all courses automatically</li><li>Maintain brand consistency effortlessly</li><li>Execute company-wide <a href="/pages/cyAMHeBfJU7INXX7GK3R">rebranding</a> in one click</li></ul></td><td><ul><li>Creates inconsistencies across courses</li><li>Requires manual updates for each course during rebranding</li><li>Increases maintenance time and effort</li><li>Makes brand compliance difficult to track</li></ul></td></tr></tbody></table>

{% hint style="success" %}
Only users with the **Style** permission can make changes to workspace-level branding. For more information about user permissions, see [Manage Company Users](/workspace/set-users/manage-a-user.md).
{% endhint %}


---

# 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://help.parta.io/branding/introduction.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.