> For the complete documentation index, see [llms.txt](https://security.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://security.screendesk.io/end-user-access/recordings-security.md). # Recordings Security ## Recordings Security Guide ### Overview This guide details the security features and controls available for managing recordings within Screendesk, including access controls, storage options, and data retention policies. ### Recording Access Controls #### Access Level Restrictions * Administrators can restrict recording access to authenticated users only * When enabled, only logged-in Screendesk users can view recordings * Prevents unauthorized access to sensitive content #### Role-Based Access * Owners & Admins: Full access to all recordings * Editors: Can manage all recordings within the organization * Members: Can only manage their own recordings ### Data Storage and Management #### Storage Location Options * Administrators can select preferred storage region: * North America * Europe * Benefits: * Meets data residency requirements * Ensures compliance with regional regulations * Optimizes access speed for local users #### Automatic Data Retention * Configurable automatic deletion rules * Administrators can set recordings to delete after specified number of days * Benefits: * Maintains data hygiene * Supports compliance requirements * Reduces storage costs * Automates data lifecycle management ### Security Considerations #### Data Protection * All recordings are stored with encryption * Access logs are maintained for audit purposes * Regional storage supports data sovereignty requirements #### Compliance Support * Automatic deletion helps maintain data minimization principles * Storage location selection aids in regulatory compliance * Access restrictions support data protection requirements ### Best Practices for Recording Security 1. Implement authenticated-only access for sensitive content 2. Choose storage location based on compliance requirements 3. Set up appropriate data retention policies 4. Regularly audit recording access patterns 5. Document storage and retention configurations 6. Review and update security settings periodically 1. Train users on proper recording sharing practices --- # 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://security.screendesk.io/end-user-access/recordings-security.md?ask=&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.