> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/account-management/organization-account-settings/company-branding.md).

# Company branding

[Account Owners](/getting-started/dscout-quickstart-guide/user-roles-and-permissions.md) can set up default company branding to apply to Dscout studies. Once company branding is set up at the [account level](/account-management/organization-account-settings/manage-organization-account-settings.md), you will see a button to Add Default Branding on your studies. When clicked, all fields will populate automatically with the default company branding for your account. You will also have the option to fill in custom branding if you choose.

## Setting up company branding

Only Account Owners can set company branding defaults. To do this, head to your [Account](/account-management/organization-account-settings/manage-organization-account-settings.md) settings by clicking "Account" in your profile dropdown, located in the top right corner of your screen. Alternatively, from the [Dscout home page](/getting-started/dscout-quickstart-guide/navigate-the-dscout-platform.md), click the "Account Management" button to the left of your profile photo.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RPLZoLW2Hb2pg8hCCxdi/25523720774420)

From the account page, head to the Settings tab. This is where you can adjust your company branding settings.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/967sYmup4XRNVKSOaXS1/25523720784020)

## Default vs. custom branding

Setting up default company branding will allow you to easily load company branding for your studies without having to fill in each field. Company name, URL, description, and logo will populate automatically when you click “Add Default Branding” once your default settings are in place on the Settings page.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/jch9xpWXe1uNtyhDJbxr/11759430443540)

You’ll also have the option to edit each field with custom values or start from a blank slate.

## Tips for logos

To make sure your company’s logo looks its best, follow these guidelines!

* Your image should be no larger than 560 px by 560 px and no smaller than 150 px by 150 px.
* Choose a JPG or PNG with an opaque background. We do not recommend the use of transparent backgrounds.
* The aspect ratio of your image must be between 3:4 and 4:3
* Opt for a square image. If the image you upload is not a square, it will be cropped! Consider using an app icon or social media profile image.

Below is an example of how cropping could result in parts of your logo getting cut off. Opting for a square image will render the best results as shown on the right:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/s6DK7oLjxht3glPUrFN9/11728059560852)

FYI - Your Company branding logo will save automatically without clicking ‘Done’ so be aware that if you navigate away from the Settings page without clicking ‘Done’ it’s possible to only save the logo.

## Use cases for company branding

Use this feature any time you want participants to know who is running the study they're participating in. Including your company’s branding can be helpful for projects which recruit participants outside of the Dscout Scout Panel so they know who they’re working with. It also may be helpful to include company branding for projects that have niche recruits, projects that don’t require anonymity, or any projects that require allowlisting into a beta experience.


---

# 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://help.dscout.com/account-management/organization-account-settings/company-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.