> 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.md). # Branding and Custom Domains Learn about custom domains and whitelabelling in Couchdrop ## Overview Customize how customers and partners access Couchdrop by configuring your own domains and applying your organization’s branding. Branding settings are configured by the **Owner** from **Admin Panel → Security & Organization → Branding**. ## Custom Domains Use your own domain for Couchdrop services instead of the default Couchdrop domain. For example: `files.your_domain.com` Custom domains use Couchdrop’s **Dynamic SSL Configuration** and require a DNS CNAME record pointing your domain to the Couchdrop domain shown in the configuration. If you use FTPS with a custom domain, you will also need to provide a certificate that matches your domain. See [**Custom Domains**](/administration/customization/custom-domains.md) for configuration details. ## Branding and Whitelabelling Whitelabelling lets you customize customer-facing Couchdrop interfaces with your company name, logo, favicon, and other branding. Branding can be applied to: * The Couchdrop login page * The main Couchdrop Portal * Shared Links * Request Files portals * Configured custom domains See [**Branding and Whitelabelling**](/administration/customization/branding-and-whitelabelling.md) for the available branding options. --- # 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.md?ask=&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.