> 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/security/restrict-access-to-recordings.md).

# Sharing and access

Where recordings are stored and who can open their links.

Admins set these in **Settings → Sharing & access**.

{% embed url="<https://app.screendesk.io/recordings/0f05abe7-4396-453e-95e0-a7eac151c135>" %}

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FODD18csAmmd9i8tpcmy5%2Fdocs-panel-sharing.webp?alt=media" alt="Settings, Sharing &#x26; access"><figcaption></figcaption></figure>

### Storage location

Recordings, bug reports and their thumbnails are stored in **America** (AWS US East) or **Europe** (AWS Paris). You can change it at any time: new ones go to the new region, and the ones you already have stay where they are.

### Who can open a recording

Each recording and bug report is either:

* **Anyone with link**: no sign-in needed.
* **Workspace members**: only members of your workspace, once signed in.

To change one, click the arrow next to **Share**. The person who made it, admins and editors can.

### Defaults for new recordings

* **Team recordings sharing** (Plus and up): what your team's new recordings and bug reports start with.
* **Customer recordings sharing** (Pro and up): what new customer and video call recordings start with.

### Restrict access

**Restrict access** (Pro and up) makes every customer and video call recording workspace-only, including the ones you already have, and stops anyone making one public.

{% hint style="warning" %}
Turning it off doesn't make them public again.
{% endhint %}


---

# 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/security/restrict-access-to-recordings.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.
