> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/settings/brand-kit.md).

# Brand kit

## <mark style="color:$primary;">Overview</mark>

The Brand Kit allows partners and customers to personalise their CybaOps experience, ensuring the platform reflects their own brand identity.&#x20;

This is particularly useful for partners and organisations operating under their own branding, providing a consistent experience for users from login through to day-to-day platform usage.&#x20;

Partners can customise their branding by uploading a logo, configuring a unique login URL, and defining brand colours used throughout the platform.

***

## <mark style="color:$primary;">Logo/Icon</mark>

The Logo section allows you to upload your organisation's icon for use throughout CybaOps.

Your icon will be displayed in key areas of the platform, helping create a familiar and consistent experience for users.

#### <mark style="color:$primary;">Best Practice</mark>

* Upload an SVG with a transparent background where possible.
  * An icon works best, however you can upload as many files.
* Choose a icon that remains clear when displayed at smaller sizes.
* Avoid excessive whitespace around the logo image.

<figure><picture><source srcset="/files/64aPbt4sFgACPXBV52xP" media="(prefers-color-scheme: dark)"><img src="/files/Q9hQCwM0lrSClA1F4a6R" alt=""></picture><figcaption></figcaption></figure>

You can update your logo at anytime by clicking remove and then uploading a new one.&#x20;

***

### <mark style="color:$primary;">Login URL</mark>

The Login URL allows you to create a branded access point for your users.

Instead of using a generic platform address, you can provide users with a customised login URL that aligns with your organisation's branding.

#### <mark style="color:$primary;">Add your company name as a subdomain</mark>

* You do not need to add https\:// or [www](http://www).
* keep it short and memorable

#### <mark style="color:$primary;">Example</mark>

If your company name was ABC Limited we would suggest abc.cybaops.com

This would allow your customers to view your branding on your subdomain.&#x20;

<figure><picture><source srcset="/files/aA7FmHvhb3xzVKXLWxby" media="(prefers-color-scheme: dark)"><img src="/files/4tHf1HpMQrtGHy6UNLGv" alt=""></picture><figcaption></figcaption></figure>

***

### <mark style="color:$primary;">Colour Scheme</mark>

The Colour Scheme section allows you to apply your organisation's branding colours throughout CybaOps.

You can configure:

* **Primary Colour** – Used for key actions, navigation elements, buttons, and highlights.
* **Secondary Colour** – Used to complement the primary colour and provide additional visual styling across the platform. Partners can configure two brand colours as part of the branding experience.&#x20;
* **Colour Theme** – Used to dictate what colour theme your end clients will see.&#x20;

#### <mark style="color:$primary;">Colour Theme</mark>

If you select system default then end client users will be deafulted to the colour theme used on their system, however they will be able to change this manually in their personal preferences.

If you select either light or dark mode, then this will be the theme applied to all users on your end client tenancies, and they will not be able to change it.&#x20;

#### <mark style="color:$primary;">Best Practice</mark>

* Select colours that align with your existing corporate branding.
* Ensure sufficient contrast for accessibility and readability.
* Choose colours that remain clear across both light and dark interfaces.

{% hint style="info" %}
If you want to find out more about light & dark modes and how you can set them for your end clients, visit the [Settings Overview](/settings/settings-overview.md) page.
{% endhint %}

<figure><picture><source srcset="/files/ZXKxMggWENXEcvBIJokn" media="(prefers-color-scheme: dark)"><img src="/files/qVVSukbs9uXw5Ua61GPy" alt=""></picture><figcaption></figcaption></figure>


---

# 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://docs.cybaops.com/settings/brand-kit.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.