Automated Data Governance

Turn file-handling requirements into specific controls: what may arrive, where it goes, who may access it, how long it remains, and what evidence is retained. Each control has a scope and a trigger. Check both before applying a policy across native storage, mounted storage, and external systems.

Control Incoming Files

Upload restrictions can enforce naming, extension, and length rules. A filename rule cannot determine whether the contents are correct or safe. Malware Scanning inspects new uploads and holds them while scanning; Expectation content validation checks business data against your criteria.

An Inbox can collect submissions with registration and separate submission folders. Apply the relevant folder controls to its destination. Registration records what a visitor supplies; choose the appropriate authentication or access controls when identity must be verified.

Processing order matters when scanning, renaming, encryption, and routing are combined. Test the output and the failure path instead of treating the settings as independent switches.

Organize and Protect the Result

Organization rules can place and rename files according to supported patterns. Folder structure locks protect a hierarchy used by people and workflows, while folder permissions control file actions. Structure locks do not make file contents immutable, and Automations have their own documented lock behavior.

Custom metadata can record business context such as an invoice identifier or review status. A metadata value is useful context; it does not enforce access or approval unless the relevant process acts on it.

Configure GPG when the exchange needs file-level encryption beyond normal transport and storage encryption. Uploads and copies trigger folder-based GPG processing; moves do not. On a mount, GPG requires buffered storage and onward delivery. Maintain the appropriate keys and monitor processing outcomes.

Separate Expiration, Recovery, and Preservation

File Expiration deletes files based on their modification age. It is not an archival copy operation. Review existing files before enabling a rule because it applies retroactively. If files must be archived first, define and verify that separate step before deletion becomes eligible.

On a mount, expiration deletes files on the remote storage. The mount is an inheritance boundary, so configure expiration on or within it. Files.com native deleted-file retention does not recover those remote deletions; recovery depends on the remote system.

Deleted-file retention, Restore, and independent backups address different recovery needs. Test recovery of an earlier version, not just the presence of the latest synchronized copy. Keep log retention separate from file retention.

Archive Only Mode permanently prevents modification and deletion through the site. It is irreversible and belongs in a deliberately chosen archive environment. On mounted storage it cannot prevent someone changing the files directly on the remote system.

Govern Sharing and Observe Outcomes

Share Link policies control recipient access and expiration. Watermarks apply to supported previews; they are not a universal rewrite of every uploaded or downloaded file.

Use file history, settings-change records, and the relevant processing logs to verify policy behavior. Notifications report configured file activity, Event Channels route supported operational events, and Expectations detect missing or invalid deliveries. Check that a feature actually emits the event you want; a restriction or expiration rule does not imply a pre-expiration or rejection email.

Export required evidence through SIEM integrations under an appropriate retention policy. Controls applied through Files.com do not automatically govern direct access to external storage, so review that access with the remote system's owner as part of the same policy.