.png){kind=logo}
File Management
- 15 Aug 2025
- 2 読む分
- 印刷する
- 闇光
- PDF
File Management
- 更新日 15 Aug 2025
- 2 読む分
- 印刷する
- 闇光
- PDF
The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
記事の要約
この要約は役に立ちましたか?
ご意見ありがとうございます
File Management (Storage, Visibility, Transfer Settings)
Introduction
Configure where files, screenshots, and recordings are stored, who can access them, and how transfers are handled in ScreenMeet Remote Support.
Supported storage destinations
CRM case
ScreenMeet cloud
AWS S3 bucket
Azure Blob
Storage destination notes
ScreenMeet Cloud uploads files, recordings, and screenshots to ScreenMeet-owned AWS storage resources.
CRM Case uploads session artifacts (files, retained files, recordings, etc.) directly to your CRM platform such as Salesforce or ServiceNow, bypassing ScreenMeet storage.
Visibility and playback controls
Control | Options | Purpose |
|---|---|---|
Who can view logs, recordings, and files | Original Agent and Group Admins / Group Admins Only / All Agents | Restrict access to session artifacts. |
Allow Embedded Video Player | On / Off | Enable built-in playback in the Console. |
Allow Video Recordings to be Downloaded | On / Off | Permit local downloads of recordings. |
After any modifications or updates to settings, click Save.
File Transfer settings
Setting | Description | Guidance |
|---|---|---|
File Extension Blacklist | Comma-separated extensions blocked from transfer. | Block risky types (e.g., |
Retain Transferred Files | Keep or remove transferred files after session ends. | Set to Remove for stricter data hygiene. |
Scan transferred files with Antivirus Scanner | Scan uploads with Clam AV and reject infected files. | Enable in regulated or high-risk environments. |
After any modifications or updates to settings, click Save Configuration.
Transfer size limit
Individual file transfers are limited to 2 GB. Use third-party tools for larger files.
AWS S3 File Storage configuration
Use this procedure to store recordings, logs, and files in your S3 bucket.
In the AWS IAM console, create a policy that grants
s3:PutObjectands3:GetObjecton your bucket path.Create an IAM user (programmatic access) and attach the policy.
Record the Access key ID and Secret access key.
In the ScreenMeet Console, go to Organization > Settings and Policies > AWS S3 File Storage.
Enter the bucket name and region (e.g.,
us-east-1), Access key ID, and Secret access key.Click Save configuration, then Test bucket access.
Example IAM policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "screenmeetbucketaccess",
"Effect": "Allow",
"Action": ["s3:PutObject", "s3:GetObject"],
"Resource": "arn:aws:s3:::<my-bucket-name>/*"
}
]
}
S3 object path convention
Uploads use the following path pattern:
<prefix>//<year>//<month>//<day>//<session_id>
Azure Blob and ScreenMeet Cloud
Azure Blob: Configure the storage account and container in the Console under storage settings.
ScreenMeet Cloud: Uses ScreenMeet-owned AWS storage for files, recordings, and screenshots.
Screenshots destination
CRM case
ScreenMeet cloud
AWS S3 bucket
Azure Blob
Verification
Start a session and take a screenshot and a short recording.
Confirm artifacts appear in the selected destination (CRM/cloud/S3/Azure).
Validate access per the “Who can view” control and test embedded playback if enabled.
Conclusion
Select a storage destination per compliance needs, enforce access and playback controls, and apply transfer policies that match your organization’s security requirements.
この記事は役に立ちましたか?