> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/administration/customization/branding-and-whitelabelling.md).

# Branding and Whitelabelling

Apply your organization’s branding to customer-facing Couchdrop interfaces.

## Overview

Branding settings are configured by the **Owner** from **Admin Panel → Security & Organization → Branding**.

Before configuring branding, have suitable versions of your logo and favicon available.

{% hint style="info" %}
Whitelabelling must be enabled for your customizations to appear. Make sure the relevant **Enable Whitelabelled** options are turned on.
{% endhint %}

### Company Name

Configure the company name displayed by Couchdrop.

The company name can appear:

* In the browser tab
* On the login page beneath the logo
* On inbox pages
* In locations where **Show company name** is enabled

### Favicon

Upload the favicon displayed in the browser tab.

Recommended dimensions are:

* `16 × 16px`
* `32 × 32px`

### Portal Branding

These settings apply to the main Couchdrop Portal.

#### Login Page Logo

Replace the logo displayed on the login page.

The maximum height is `300px`, with the width adjusted proportionally.

#### Couchdrop Portal Logo

Replace the logo displayed in the top-left of the Couchdrop Portal.

The recommended height is `24px`, with the width adjusted proportionally.

### Shared Link and Request Files Branding

These settings apply to Shared Links and Request Files portals.

#### Inbox Logo

Replace the logo displayed on Shared Links and Request Files pages.

The maximum height is `300px`, with the width adjusted proportionally.


---

# 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.couchdrop.io/administration/customization/branding-and-whitelabelling.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.