Use Cases

Workspaces apply to any scoped operational context where a team needs independent control over its own resources. The examples below show common patterns across business units, regions, projects, partner relationships, and automated workflows.

Delegated Administration for Business Units and Departments

A financial services company with lending, insurance, and wealth management divisions gives each division a Workspace. Each division's Workspace Administrator onboards loan officers, underwriters, or advisors. They set up remote server connections to their own core systems, configure automations for their own file flows, and manage their own external partners. The central IT team focuses on site-wide governance instead of handling every access request.

A healthcare organization takes the same approach to keep clinical operations, research, and billing in separate Workspaces. Patient billing data never appears in the research Workspace. Research trial files never appear in the billing Workspace. When regulators or clients require proof of data separation, the organization demonstrates it at the platform level.

Regional or Geographic Control

A logistics company with distribution centers in North America, Europe, and Asia gives each region a Workspace. The regional IT lead in each location onboards warehouse staff on a self-service basis, connects to local EDI and ERP systems, and manages vendor relationships with local carriers and freight forwarders without waiting on the global IT team. Because all regions share the same security policies, authentication, and branding, Workspaces are the right fit. If the regions required separate IP addresses, custom domains, or different authentication configurations, Child Sites would be the better choice.

Simplifying Complex Permission Models

A media company with 15 departments previously relied on nested folder permissions, permission fences, and group-based access rules to keep teams separated. Over time the permission structure became difficult to audit and prone to misconfiguration. Moving each department into its own Workspace replaced hundreds of overlapping permission rules with clean, structural separation.

Independent Partner Management

An automotive manufacturer's procurement, engineering, and aftermarket divisions each work with different suppliers. Procurement exchanges purchase orders with parts suppliers. Engineering shares CAD files with design partners. Aftermarket sends catalogs to distributors. Each division manages their own partner relationships within their Workspace without creating confusion about who owns which partner.

Client Engagements and Project-Based Environments

A managed services provider runs file transfer operations for multiple enterprise clients. Each client engagement gets its own Workspace. The engagement lead manages their own users, automations, remote server connections, and partner access. One client's data, integrations, and file flows never intersect with another's.

A construction firm takes the same approach per major project, where the project manager onboards subcontractors, sets up automations, and connects to the project management system. When the project completes, the Workspace is no longer needed.

Confidential Projects and M&A Diligence

A corporate development team runs M&A diligence on a target acquisition. The work involves outside counsel, accounting firms, due-diligence advisors, and internal stakeholders from finance, legal, and operations. The corp dev lead creates a Workspace for the deal and becomes its Workspace Administrator. Outside firms are onboarded as Partners scoped to the Workspace, with their own Partner Admins managing their own users. Internal stakeholders are added as Workspace users or granted access from the main site. All diligence materials live inside the Workspace and are invisible to the rest of the company. When the deal closes or falls through, the Workspace is preserved as a record or deleted. The same pattern fits any time-bounded confidential effort: board investigations, restructurings, IPO readiness, or sensitive HR matters.

Rapid Onboarding of New Divisions or Acquisitions

A retail conglomerate acquires a specialty brand. Instead of restructuring the existing site, the IT team creates a new Workspace for the acquired brand. The brand's operations lead becomes the Workspace Administrator and builds out the folder structure, onboards staff, connects to the brand's fulfillment systems, and sets up partner relationships from day one.

Agentic and Automated Workflows

Organizations building agentic workflows or AI-driven automations use Workspaces as secure, isolated execution environments. Each agent or automated process operates within a Workspace boundary, with access only to the folders, integrations, and partner connections within that Workspace. The agent cannot read, modify, or interact with data in any other Workspace or on the main site. This isolation ensures that automated processes operate within well-defined boundaries without the risk of accessing or modifying unrelated data.

Testing and Experimentation

A Site Administrator creates a temporary Workspace to test new automations, validate remote server connections, or experiment with folder structures and file flows before rolling them out to a production Workspace. Because creating a Workspace requires minimal setup, teams can spin up a test environment, run their validation, and remove it when done without affecting any production resources.