> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/request-screen-recording/branding-and-customization.md).

# Customize the recorder

Settings → Recorder: the fields customers fill in, steps and consent before recording, your logo and color, and the name and language customers see.

Admins change the recorder customers open from the workspace name at the top left: **Settings → Recorder**. It has four tabs: **Fields**, **Steps before recording**, **Consent** and **Look**. Switches save as soon as you flip them.

{% embed url="<https://app.screendesk.io/recordings/f27509bf-8a3a-4055-b572-19ff83719263>" %}

To see your changes as customers do, click **Open the recorder** on the **Look** tab.

## Fields

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2F8GhCaCSDUJ98eDTMhAZw%2Fdocs-panel-recorder.png?alt=media" alt="Settings, Recorder, Fields tab"><figcaption></figcaption></figure>

* **Require an email**: customers type their email before sending. Off, they can leave it out. The email field shows only on **Request recording** links that don't already carry the email, not on helpdesk request links.
* **Require a title**: customers name their recording before sending it. Off, there's no title field.
* **Skip the countdown**: recording starts as soon as customers pick what to share. It applies to request links only; your team's own recordings still count down.

## Steps before recording

A short guide customers go through before the recorder opens: what to show you, what to have ready.

1. Turn on **Show steps before recording**.
2. Click **Add the first step**, then **Add step** for more, up to 10. They show in this order.
3. Each step is a card with a title, instructions and an optional image (JPG, PNG, GIF or WebP, up to 5 MB). Click the words on the card to change them, then click **Save** on that step.

Customers move through with **Next** and **Back**, and **Get Started** opens the recorder. They see the steps each time until they tick **Don't show this again**, which is remembered in that browser.

Available on Plus, Pro and Enterprise.

## Consent

Ask customers to accept a privacy notice before they can record. See [Consent](https://docs.screendesk.io/request-screen-recording/branding-and-customization/consent.md).

## Look

* **Logo**: above the recorder, and on the steps and consent screens. PNG or JPEG, up to 5 MB and 800 × 500 px. Without one, the recorder shows the Screendesk logo.
* **Accent color**: on **Start Recording**, and on the buttons and links of the steps and consent screens.

To remove "Recorded with Screendesk" and "Video request by Screendesk", turn off **Screendesk branding** in **Settings → General**. Available on Plus, Pro and Enterprise. See [General](https://docs.screendesk.io/settings/general.md).

## Name shown to customers

The recorder says "*name* is requesting a video of your screen". It uses your **Alias** if you set one (your avatar → **My profile**), otherwise your first name. Links that aren't tied to a person show the workspace name.

## Languages

The recorder follows the customer's browser language: English, French, Spanish, Portuguese, Brazilian Portuguese, German or Dutch. Any other language shows English.

Steps and the consent screen have a tab per language. A language left blank shows the English. To ask for another language, email <support@screendesk.io>.


---

# 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.screendesk.io/request-screen-recording/branding-and-customization.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.
