> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/team-and-account/branding.md).

# Branding

Add your logo and colors to the emails and upload pages your recipients see.

{% hint style="info" %}
Available on the **Professional** and **Enterprise** plans.
{% endhint %}

Branding puts your logo, header color and button color on the pages and emails your recipients see, so a request looks like it comes from you.

## Set up branding

{% stepper %}
{% step %}

### Open Branding

Go to [Team → Branding](https://pipefile.com/dashboard/settings/team#branding). You need to be a team admin, and your team needs a name first (see [Team members and admins](/team-and-account/team-members-and-admins.md#create-your-team)).
{% endstep %}

{% step %}

### Add your logo

Drop an image into **Logo**. Use **Logo width** to size it between 100 and 300 pixels; the preview shows it on your header color.
{% endstep %}

{% step %}

### Pick colors

Choose a **Header color** (the bar behind your logo) and a **Button color**.
{% endstep %}

{% step %}

### Save

Click **Save**. New emails and every request page use the new branding.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
A horizontal (wide) logo reads best in the header. Pick a header color that contrasts with your logo.
{% endhint %}

## During a free trial

The trial includes branding, but you need a payment method on file to turn it on. The **Branding** section asks for a card; it isn't charged until you start a subscription.

## If you don't see branding options

* The section shows **Available in Professional** with an **Upgrade Now** button: your plan doesn't include branding. See [Billing, plan changes and canceling](/team-and-account/billing-and-canceling.md).
* The **Branding** section is missing: create your team first, or ask a team admin; only admins can open Team Settings.

## Related

* [Plans and features](/getting-started/plans-and-features.md)
* [Your profile page](/intake/profile-page.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/team-and-account/branding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.