Operations

Why Suite file streaming still needs an internet connection

Understand how connected access supports Suite’s shared workspace, and plan reliable sessions with caching and connectivity in mind.

Connect people to the same shared work

Suite is designed for connected file access, pairing a mounted cloud drive with authenticated access and coordination around shared data. A reliable internet connection lets distributed collaborators reach the work from their supported environments. That connection is required even for cached files; pre-caching prepares active data for a session while keeping the workflow connected to Suite. See our explanation of offline use.

This matters when choosing a filesystem for travel, locations with unreliable connectivity or automated work on an isolated host. Make connectivity a product-fit question before relying on the workflow.

Ask about the actual period of disconnection

“Works remotely” and “works offline” describe different requirements. A remote editor with a reliable connection may have a suitable environment for connected file access. A person working through a long flight may need an approved local-copy workflow that remains usable without a network.

Describe the requirement in operational terms: how long the connection may be absent, which inputs must remain available, whether outputs must be saved during that period, and who needs to see changes afterward. Do not assume a filename visible in a file browser proves its content will remain accessible.

Plan a separate deliverable for offline work

The presence of data in a client cache does not establish that it can be opened outside the client’s supported behavior. Treat cache configuration and offline access as separate decisions.

If disconnected work is essential, ask the data owner to approve an appropriate local-copy process. Verify the required files and application dependencies while connected, and agree how outputs will be reconciled later. This is general workflow planning, not a documented Suite offline feature or an instruction to manipulate Suite’s internal cache files.

Protect the end of a connected session

Before intentionally disconnecting or shutting down after writing files, confirm that Suite has finished uploading and investigate reported errors. A completed operating-system copy does not by itself demonstrate that the remote upload is complete. Our upload instructions explain which client status to check.

For a team handoff, include a read of the intended output by an authorized collaborator. For an agent, an uncertain upload should be reported as uncertain; a finished local command is not a reason to invent a successful remote result.

Design remote work around a connected handoff

A connected team can organize work around the shared library instead of treating each location as a separate copy-distribution project. In a proposed follow-the-sun edit, the outgoing editor saves a named revision, confirms upload completion, and records the media and outputs needed for the next shift. The incoming editor opens that revision through their authorized Suite environment and verifies the intended shot or sequence.

The handoff note should identify the current project revision and the next task. It does not need to include another complete media package when the recipient already has access to the shared sources. Application-specific project coordination still matters; two users should follow the application’s supported collaboration model when modifying the same project.

This is the useful distinction between location independence and disconnection: people can work in different places while remaining connected to shared files. Use the multi-location editing guide to plan that handoff, and keep any truly disconnected task as a separate, explicitly prepared workflow.

Include connectivity in a deployment decision

Use these questions in the evaluation brief:

  1. Is the host expected to remain online while Suite is in use?

  2. What is the approved response if the connection fails during a task?

  3. Who can investigate an incomplete operation or client error?

  4. What evidence confirms that outputs are ready for the next person or process?

  5. Does any essential task require a separately supported offline workflow?

Suite may fit the connected portions of a broader workflow even when another process serves disconnected work. The useful decision is explicit about where each requirement is met. Choose a deployment path below once that boundary is understood; neither Managed storage nor S3 Native should be assumed to remove the internet requirement.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.