> 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/consent.md).

# Consent

Ask customers to accept a privacy notice before they can record.

Admins turn it on in **Settings → Recorder**, on the **Consent** tab: **Ask for consent before recording**. The recorder then opens on a consent screen with **Decline** and **Accept**. Customers who decline are told to close the tab and can't record.

{% embed url="<https://app.screendesk.io/recordings/ac63bb39-984c-4202-86c1-6ba3c222cf3f>" %}

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

Under **Consent screen**, click the words to change them, then **Save**:

* the consent text
* **Link text** and **URL** of your privacy policy. The link shows once a URL is set; its text defaults to "Privacy Policy".

Each language has its own tab. A language left blank shows the English.

* Acceptance is remembered in the customer's browser, for your workspace. Another browser or device, a private window or cleared site data asks again.
* It shows on request links only, not on videos your team records with **Send video**.
* With [steps before recording](https://docs.screendesk.io/request-screen-recording/branding-and-customization.md#steps-before-recording) also on, customers see consent first, then the steps.
* Test it in a private window: your own browser may have accepted already.

Available on all plans.


---

# 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/consent.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.
