Customer Isolation

Files.com separates customers' data and configuration while running on shared infrastructure. Access to one customer's site does not grant access to another customer's site. Each operation must be authorized for the site and resources it affects, including access to file contents and background work performed on the customer's behalf.

This is logical separation through access controls. Sharing a service or storage system does not give customers access to each other's data, and creating a Site or Workspace does not allocate dedicated physical infrastructure.

Site and Workspace Boundaries

A Site has its own users, resources, and site-wide configuration. Child Sites retain that separation, while Parent Site Administrators retain administrative access to them. A Child Site Administrator's role does not grant access to the Parent Site or sibling Child Sites.

Workspaces provide resource and administrative boundaries within a Site. They share the Site's authentication configuration, security policies, and other site-wide settings. Site Administrators retain access across all Workspaces. Workspace Administrators have authority within the Workspaces they administer, and Site Administrators can explicitly grant users access to additional Workspaces.

These distinctions matter when evaluating separation between teams or environments. A Workspace separates delegated work within a common site policy; a Child Site separates site configuration while retaining the Parent Site's administrative relationship. Account Structure & Environments covers the choice between them.

File Access and Connected Storage

File operations remain subject to the permissions granted to the user or integration. A Remote Server Mount makes connected storage available through Files.com; it does not make every file on that storage available to every user. The connection's access to the remote system and the user's Files.com permissions are separate controls.

The Files.com Agent can perform file operations in your environment. It changes where selected work runs, while Files.com continues to provide authentication, permissions, and administration. The location of an Agent or the authoritative file copy alone does not establish where all file contents travel; that depends on the transfer and processing path.

Files.com's own staff access and confidentiality practices are described in How Files.com Handles Customer Data.