# Incoming Recordings: Allow Public Access

{% hint style="info" %}
This is for incoming recordings only
{% endhint %}

{% hint style="warning" %}
If enabled: 

* anyone with the link can view incoming recordings.

If disabled:

* only logged-in workspace members can watch, unregistered teammates won't have access incomings recordings (eg. in case agents escalate recordings to devs)<br>
  {% endhint %}

By default, videos can't be accessed by anyone with whom you share the video URL. This is a deliberate choice as it provides a better security level. You can override this setting on a per-video basis using the lock icon button at the video bottom right:

<figure><img src="/files/HcfaRnAfWPLObRsuns07" alt=""><figcaption></figcaption></figure>

In any case, it is worth mentioning that:

* Our servers are behind a secure firewall, and all videos are uploaded over an SSL-encrypted connection.
* Each video is associated with a unique ID that would take a computer years to guess
* We offer an [auto-deletion feature](/birdie-docs/security/custom-data-retention-policies.md) that completely removes a file from our systems, in case you want your content removed.

***

### How to enable public access by default for your workspace

In case you want to allow public access to anyone who get the link for incoming recordings:

1. Go to [settings -> security](https://app.birdie.so/settings/security)
2. Enable the option `Allow Public Access to Incoming Recordings` <br>

{% hint style="info" %}
If you change the setting, it will apply to future recordings. However, past recordings retain the settings they were recorded with.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.birdie.so/birdie-docs/security/recordings-privacy-settings/incoming-recordings-allow-public-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.