> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/style.md).

# Style

The Virtual Desktop seen by the player, and to some extent what is seen by the Facilitator, can be styled by the designer.

This can be customised to represent your **brand, client, or tone**, allowing you to effectively **whitelabel an exercise** so it feels bespoke to the organisation running it.

These finishing touches can also make a big difference to the player experience, helping to **worldbuild and increase immersion**.

<table><thead><tr><th width="229.88885498046875">Customise</th><th>Description</th></tr></thead><tbody><tr><td><strong>Access screen</strong></td><td><ul><li>Background</li><li>Logos</li><li>Click to play button</li><li>Browser favicon</li></ul></td></tr><tr><td><strong>Player desktop</strong></td><td><ul><li>Channel icons and names</li></ul></td></tr><tr><td><strong>Bespoke URL</strong></td><td>Custom web address for the exercise</td></tr></tbody></table>

## Access

Navigate to `Configuration` > `Style` > `Access`.

### Background, logos, and click to play button

The access screen is often a player's first impression of the exercise, so it's worth branding to match the organisation. You can **apply your own branding** to the screens players see before they enter the exercise.&#x20;

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FgRNCBb4qk7DckzeujGkV%2Faccess%20screen.gif?alt=media&amp;token=1c97d093-ba40-4ba9-9317-afb4b5931f62" alt=""><figcaption></figcaption></figure>

### Browser favicon

You can also customise the browser tab name and favicon for your exercise.

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2F9fj4zwD83u4fNhsNXTOB%2Fbrowser%20tab%20config.png?alt=media&amp;token=f78426b1-eee5-4370-b4d6-ad32d4c92eb8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We recommend keeping your registration page branding **consistent with the rest of the exercise (colours, logo, tone of wording)** so the world you're creating feels coherent.
{% endhint %}

***

## Player desktop

### Channels

Navigate to `Configuration` > `Style`  > `Player desktop`.

{% embed url="<https://youtu.be/rKVPPMEjs5k>" %}

Customising channel icons is one of the quickest ways to make an exercise feel realistic. Edit the name and icon for each channel to match client branding and/or the platforms you're simulating.

Here you can:

* Choose whether channel icons are visible from the **start**, or only after the **first message**
* Modify the channel icon **size**
* Edit the channel icon **text** (font, size, and colour)

Click on a channel icon directly or drag and drop to upload your own.

{% hint style="success" %}
Free icons for popular apps are available at [www.flaticon.com](https://www.flaticon.com).
{% endhint %}

***

## Bespoke URL

Give your exercise a **custom web address** instead of a generic Conducttr link. Ask your account manager if you'd like to customise your URL.&#x20;

#### Export/import style

You can export and import style to **reuse** across exercises. This is useful if you're running the same client through multiple scenarios, or want to keep a consistent look across a series of exercises for the same world/organisation.

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2F1WdoYDBgFPKkms7SqgeB%2Fimport%20export%20style.png?alt=media&amp;token=6748c0df-b499-4ce0-aa4d-73f37bd02e7a" alt=""><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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/style.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.