File Management

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

Visibility and playback controls

After any modifications or updates to settings, click Save.

File Transfer settings

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.

1. In the AWS IAM console, create a policy that grants s3:PutObject and s3:GetObject on your bucket path.

2. Create an IAM user (programmatic access) and attach the policy.

3. Record the Access key ID and Secret access key.

4. In the ScreenMeet Console, go to Organization > Settings and Policies > AWS S3 File Storage.

5. Enter the bucket name and region (e.g., us-east-1), Access key ID, and Secret access key.

6. 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

1. Start a session and take a screenshot and a short recording.

2. Confirm artifacts appear in the selected destination (CRM/cloud/S3/Azure).

3. 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.