> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/access/account-creation-and-onboarding-guide/branding.md).

# Branding

## Overview

Branding is how your organisation/government Complaint Management System looks to citizens and employees. Your logo, name and colour appear across your workspace and in the citizen and employee apps.

## Steps

### Step 1. Add logo

* On the Branding page, find the Account logo.
* Select Upload logo and choose your picture.
* Check the small preview. To use a different picture, select Replace. To remove it, select Remove.

<table><thead><tr><th width="210.20703125">Logo rule</th><th>Details</th></tr></thead><tbody><tr><td>File type</td><td>PNG or JPG only. SVG, WebP and other formats are not accepted.</td></tr><tr><td>Size on screen</td><td>At least 128 × 128 pixels. A square picture looks best.</td></tr><tr><td>File size</td><td>No more than 2 MB.</td></tr></tbody></table>

You can change this in the Management Console.&#x20;

### Step 2. Check your account name

Your Account name is shown here but cannot be changed on this page. To change it, go to Workspace settings (from your initial at the top right) and select Change workspace name.

### Step 3. Choose your colours

Your theme is the main colour used in the citizen and employee apps. Under Brand Theme, select one of the three colour sets. A tick shows your choice.

* CMS Blue (the default)
* DIGIT Orange
* Green and Gold

### Step 4. Save

Select Save and continue. Your logo and name appear in the left menu straight away, and Geography opens.

### If something goes wrong

<table><thead><tr><th width="313.7421875">What you see</th><th>What to do</th></tr></thead><tbody><tr><td>What you see</td><td>What to do</td></tr><tr><td>Use a PNG or JPG image.</td><td>Save your logo as PNG or JPG and upload it again.</td></tr><tr><td>That image is over 2 MB.</td><td>Use a smaller file. Most image editors can reduce the size.</td></tr><tr><td>That image is … px. Use one at least 128px on each side.</td><td>Use a larger picture.</td></tr><tr><td>Your name and logo are saved, but the theme isn't.</td><td>Select your colour again and save.</td></tr><tr><td>Saving your branding failed.</td><td>Try again, or select Continue anyway.</td></tr></tbody></table>


---

# 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.digit.org/complaints-management/access/account-creation-and-onboarding-guide/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.
