> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/generating-a-report/report-branding.md).

# Report branding

**Report branding** is your organization's letterhead. It's set once per workspace and printed at the top of every report, whichever template the report uses.

{% hint style="info" %}
Editing report branding needs the **Sign Off Reports** capability (admins). See [Workspaces & roles](/products/workbench/variant-interpreter/workspaces-and-roles.md).
{% endhint %}

## Opening report branding

1. Click **Settings** in the left navigation.
2. Open the **Report Templates** tab.
3. Click **Report branding**.

## What you can set

### Organization

The laboratory named at the top of every signed report.

* **Organization name** (required).
* **Address**: one line per row. Blank lines are dropped.
* **Logo text**: saved with the branding, but not printed on reports yet.

### Credentials

* **CLIA ID** and **Accreditation**: printed on the letterhead.
* **Signer role**: printed beside the signer's name in the report's sign-off, for example "Laboratory Director, PhD FACMG".
* **Disclaimer**: printed in the sign-off section of every report.

### Logo

A PNG or JPEG, 512 KB or smaller. Choose a file to upload it, or click **Remove logo** to take it off.

{% hint style="info" %}
The logo is saved as soon as you choose it. You don't need to click **Save branding** for logo changes.
{% endhint %}

### Brand colour

The accent colour printed on the report, for example on the letterhead and table headers. Pick one of the presets (**Navy**, **Teal**, **Indigo**, or **Violet**), use the colour picker, or type a hex value such as `#005589`.

The page shows the colour's contrast against white. A colour below **4.5:1** is too light to print legibly, and you can't save it. You can save the branding without a colour, but a template can't be made the default until one is set.

### Page furniture

What runs along the foot of every page:

* **Footer text**, for example the laboratory's name and CLIA number.
* **Show page numbers**: prints "Page X of Y" on every page.

Every page's footer also carries the word "Confidential".

## Saving

The **Preview** card shows how the letterhead and footer will print. When you're happy with it, click **Save branding**.

You can save a partly finished letterhead. However, a template can only be made the default once the branding has both an **Organization name** and a **Brand colour**. See [Report templates](/products/workbench/variant-interpreter/generating-a-report/report-templates.md#choosing-the-default-template).

## Branding activity

The **Branding activity** panel records who changed the organization's branding and when, for example "Uploaded a new logo" or "Set the CLIA ID".

{% hint style="warning" %}
A report's document, including its letterhead, is frozen when it's submitted for review. Branding changes apply to reports submitted after the change.
{% 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 by asking a question.

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

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/generating-a-report/report-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.