> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/operate/recording-and-interaction-data/manage-screen-recordings.md).

# Manage screen recordings

Review screen-recording triggers and administrative safety considerations for Dialogue Cloud deployments.

Use this page to review screen-recording triggers and the administrative checks to make before you enable screen recording in Dialogue Cloud.

## Before you begin

* Confirm whether screen recording is approved for the inbound, outbound, or both interaction paths in your deployment.
* Confirm which screen should be recorded on the agent workstation or host.
* Confirm which administrators are allowed to enable, disable, and review screen-recording behavior.

{% hint style="warning" %}
Screen recordings can capture customer data, agent actions, and audio. Review privacy, retention, and access requirements before enabling automatic capture.
{% endhint %}

## Recording triggers

### Inbound interactions

The inbound source says the recording can start when an agent is contacted by the Unified Contact Center (UCC).

### Outbound interactions

The outbound source says the recording can start when an agent calls a customer and the call is intercepted.

## Administrative guidance

* For Snapper-managed screen recording, use the canonical [Configure Snapper screen recording](/platform-administration/maintenance-mode-applications/snapper/configure-snapper-screen-recording.md) procedure in Platform administration.
* Validate the trigger conditions for inbound and outbound screen recording in a controlled environment before enabling the feature for production users.
* Confirm that privacy, retention, and access policies are documented for any recorded screen content before the feature is turned on.
* Treat storage location, upload method, and downstream reporting behavior as deployment-specific implementation details unless a current product-owned source confirms them for your environment.

{% hint style="info" %}
Keep inbound and outbound behavior together unless a later verified product source shows a meaningful support difference between the two paths.
{% 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://atlas.anywhere.now/operate/recording-and-interaction-data/manage-screen-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.