Files.com sites handle complex environments every day. Multiple teams, hundreds of users, dozens of remote server connections, automations, and partner relationships across business lines, all managed by Site Administrators with full control.

As organizations keep scaling, the administrative workload concentrates on the same small group of Site Administrators. Automations, remote servers, folder structures, and partner configurations from different teams all live in the same place. One team's configurations overlap with another's. Teams step on each other's workflows without realizing it. Troubleshooting turns into guesswork. Misconfiguration turns into risk.

Growing organizations need delegated administration with structural separation. Each team needs their own isolated environment where they manage their own users, partners, automations, and integrations on a self-service basis. They need a focused view of only their resources. And they need a hard boundary that prevents them from seeing, touching, or breaking anything outside their environment. At the same time, site-wide security, authentication, compliance policies, and governance need to stay centralized under the Site Administrator, applied consistently across every environment.

That is exactly what Workspaces do. We are excited to make them available in the Files.com platform.

What Defines a Workspace

A Workspace is an isolated, self-contained environment within your Files.com site. Each Workspace gets its own users, groups, partners, folders, automations, remote servers, syncs, notifications, and data governance settings. Nothing inside a Workspace is visible to any other Workspace.

A Site Administrator creates a Workspace and assigns a Workspace Administrator to run it. The Workspace Administrator then handles everything on a self-service basis: onboarding users, offboarding contractors, setting up remote servers, configuring automations, managing partners, and applying data governance policies. No tickets. No waiting.

The Site Administrator keeps full visibility and control over the entire site. Site-wide security, authentication, branding, and compliance stay centralized. Workspaces delegate operations without giving up governance.

We Studied the Trade-Offs and Built Something Better

Concepts like security domains, multi-tenant organizations, and business units have existed across file transfer platforms for years. But most implementations come with trade-offs: licensing caps on the number of partitions, heavy-weight multi-tenancy that requires separate infrastructure for simple departmental separation, view-based filtering that depends on admin behavior rather than architectural enforcement, and limited delegation that still requires the global admin to step in for common tasks.

Workspaces avoid all of these trade-offs. They are unlimited with no licensing caps. They are lightweight, sharing site-wide security and branding while providing complete operational isolation. The isolation is structural, not cosmetic.

The self-service is real. Workspace Administrators create users, reset passwords, onboard partners, configure remote servers, set up automations, manage encryption keys, and apply data governance policies end to end, on their own schedule.

Files.com already has Child Sites for full site-level isolation. Use Child Sites for hard boundaries. Use Workspaces for operational independence within a shared site.

Anywhere You Need a Boundary

Business units and departments. A financial services company gives Lending, Insurance, and Wealth Management each a Workspace. A healthcare organization separates clinical operations, research, and billing so patient data never crosses departmental lines. A law firm creates a Workspace per practice group so client files are structurally inaccessible across groups.

Client engagements and projects. A managed services provider creates a Workspace per client engagement. No client's data, automations, or integrations can intersect with another's. A construction firm does the same per project and tears down the environment when the project wraps.

Agentic and automated workflows. Organizations building AI-driven automations use Workspaces as secure, isolated execution environments. Each agent operates within a Workspace boundary with access only to the resources within that Workspace. The isolation is structural, not policy-based.

Testing and experimentation. A Site Administrator creates a temporary Workspace to test new automations, validate remote server connections, or prototype workflows before rolling them out to production. Creating a Workspace requires minimal setup, and removing it when done does not affect any production resources.

Start Building

Creating a Workspace takes minimal setup. Create a new Workspace, assign a Workspace Administrator, and they build out the environment from scratch: a clean slate for their team, department, or project.

Workspaces can be created through the Web App. They can also be provisioned automatically as part of onboarding workflows or infrastructure-as-code practices through the API, CLI, SDKs, or Terraform.

Read the full documentation:

• Workspaces overview
• Creating and managing Workspaces
• Workspace Administrator