Security Reference
Files.com is critical infrastructure for thousands of customers. Customers should be able to understand and evaluate the systems they trust with their most important files and workflows. Security Reference defines the product's security behavior so administrators, integration developers, and security teams can make informed decisions about access and data handling.
We set a high bar for transparency. Alongside our independent assessments and compliance materials, we publish detailed explanations of the platform's security behavior, the reasons behind our design decisions, and the consequences of different configuration choices. We go well beyond general assurances: we give your team the information needed to evaluate how the product actually protects your data and access.
The controls need to be understood together. An integration's permissions, a workflow's ownership, and the lifetime of a shared link can all affect the same business process. This reference explains where those controls apply, where their boundaries lie, and which responsibilities remain with the customer.
Publishing this detail is a commitment. We consider the behavior described here secure within its stated permissions, controls, and configuration requirements, and we expect the platform to honor those boundaries. We are proud to make those expectations explicit so you can evaluate our reasoning and hold us accountable to what we publish.
Capabilities and Controls
Files.com provides powerful capabilities for administering sites, connecting systems, and publishing or exchanging content. Permission to use a capability carries its documented effects. Administrative access can deliberately expose information beyond a person's own files, and a hosting service can deliberately run content supplied by its publisher. Choose administrative permissions or a feature with those effects in mind.
A control has a specific purpose. Preventing new credentials from being created is different from revoking existing credentials. Restricting changes is different from restricting visibility. File access permissions are different from the contents of a file already delivered. Understanding these distinctions helps you select the control that produces the result your organization needs.
The configuration pages linked throughout this reference explain where to apply the controls. If observed behavior differs from the documented contract, contact Support.
Planning a Security Assessment
We welcome and encourage assessments by customers' internal security teams and independent firms. Before conducting tests against the Files.com service, you must obtain our approval and coordinate with us in advance. Contact your account representative or Support and follow the Customer Security Assessments requirements in the Compliance section. That policy covers eligibility, the required agreement, sharing the full results, and testing restrictions.
Coordination lets us review the proposed methods, agree on timing, and protect service availability for other customers. Reading this reference helps your team prepare an informed assessment; it does not authorize testing against the service.