File & Recording Storage
- 03 Dec 2025
- 1 Minuto para leer
- Impresión
- OscuroLigero
- PDF
File & Recording Storage
- Actualizado en 03 Dec 2025
- 1 Minuto para leer
- Impresión
- OscuroLigero
- PDF
The content is currently unavailable in Spanish. You are viewing the default English version.
Resumen del artículo
¿Te ha resultado útil este resumen?
Gracias por sus comentarios
Configuring Cloud File Storage
Introduction
This article describes how administrators can configure cloud file storage options for ScreenMeet sessions, screenshots, and access permissions.
Session File Storage Destinations
Session files can be stored in one of the following locations:
- CRM Case: Files can be uploaded either to the parent CRM object (e.g., Incident, Case) or to the ScreenMeet session record created within the CRM.
- ScreenMeet Cloud: Included with all ScreenMeet subscriptions. Files are hosted in ScreenMeet’s AWS infrastructure within United States datacenters. Storage consumption is unlimited; however, all files are automatically pruned after 90 days.
- AWS S3 Bucket: Requires the organization’s own AWS infrastructure. Suitable for customers needing extended or custom file retention, storage in specific regions for compliance, or alignment with internal security policies. Learn more about AWS S3 file storage.
- Azure Blob Storage: Requires the organization’s own Azure infrastructure. Supports retention customization, regional data residency requirements, and compliance alignment within Azure environments. Learn more about Azure Blob storage.
Screenshot Storage Destinations
Screenshots captured during a session can be stored in the same supported locations:
- CRM Case: Screenshots may be stored on the parent CRM object or the corresponding ScreenMeet session record.
- ScreenMeet Cloud: Included with subsc
¿Te ha sido útil este artículo?