> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/portal/branding.md).

# Branding

Branding controls the visual identity applied to the portal. Use it to align navigation, calls to action, links and shared imagery with your organisation's brand.

{% hint style="info" %}
**Location:** Settings → Portal settings → Branding

Select **Save** in the Settings header, then refresh a separate student session to check the result.
{% endhint %}

### Images

| Image              | Where it is used                             | Recommended or supported dimensions                               |
| ------------------ | -------------------------------------------- | ----------------------------------------------------------------- |
| Logo               | Includes exam certificates                   | Approximately 300 × 100 px; uploads support 64–1024 px dimensions |
| Square logo        | Top-left area above the menu                 | Square, approximately 100 × 100 px                                |
| Favicon            | Browser tab icon                             | Square, approximately 30 × 30 px                                  |
| Default card image | Fallback artwork for supported content cards | Approximately 430 × 300 px; editor uses a 245:150 crop ratio      |

### Colours

You can set primary and secondary brand colours, primary and secondary button colours, and the link colour. Portals with advanced branding enabled also expose a primary chart colour.

Check colour contrast after making changes, particularly for button text, links, focus states and charts. A technically valid colour can still make content difficult to read.

Check branding in places with different backgrounds and states: the main navigation, primary and secondary buttons, links, selected items, result charts and certificate previews. Do not use colour alone to communicate whether an action is safe or a result is positive.

### Social links

Optional fields are provided for Twitter/X, Facebook, LinkedIn and YouTube URLs. Use complete public URLs, including `https://`.

### Sub-portal inheritance

A sub-portal without its own styling inherits the main portal's branding. Override only the elements that should differ for that audience; inherited values make organisation-wide brand updates easier to manage.

### Before publishing a brand change

1. Use image files with enough resolution and transparent backgrounds where appropriate.
2. Check the square logo at the small size used in navigation.
3. Check light and dark surfaces if both appear in your portal.
4. Test keyboard focus, links and disabled buttons as well as the default state.
5. Preview a representative email and certificate, not only the dashboard.
6. Check a sub-portal to confirm which values inherit and which are overridden.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://synap.ac/docs/platform/portal/branding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.