Send confidential documents with controls that survive after the transfer.

Define the share

Start with sensitivity, audience, and duration

Before choosing a tool, write down what is being shared, who needs it, how long they need it, and what would happen if it reached the wrong person. A draft brochure and an acquisition term sheet are both documents, but they do not require the same delivery controls.

Separate internal collaboration from external delivery. Internal work may need coauthoring and version history. External delivery may need a read-only copy, a named recipient, an expiration date, and a record that access was removed when the engagement ended.

Link design

Prefer identity-bound access over possession of a URL

A public or “anyone with the link” URL grants access to whoever obtains the link. It is convenient, but the link itself becomes the credential. For confidential material, prefer a link that requires the recipient to authenticate with a named account or a verified one-time code.

Set the narrowest useful permission. If a recipient only needs to review, do not grant editing. If a preview is sufficient, consider disabling download. If the project has an end date, apply expiration at creation instead of relying on someone to remember later.

Encryption in context

Protect data in transit, at rest, and at the point of access

Transport encryption protects the connection while data moves between systems. Storage encryption protects data on the provider’s infrastructure or device. Neither one alone determines who can open the file, whether an administrator can access it, or whether a recipient can copy it after download.

For especially sensitive exchanges, organizations may add file-level encryption or a secure portal. That can reduce exposure, but key and password handling become part of the workflow. Never put the decryption secret in the same message as the encrypted attachment when separation is one of your controls.

The VPN versus encrypted file sharing guide explains why these layers solve different problems.

Before sending

Review the document, not only the sharing settings

A perfectly configured link can still deliver the wrong version, hidden comments, author details, tracked changes, or incomplete redaction. Create a delivery copy, inspect it, confirm the final filename, and open it as the recipient will see it.

For office files and PDFs, review metadata, comments, hidden sheets or slides, embedded attachments, and revision history. For images, consider location and device metadata. The document privacy guide provides a repeatable preflight process.

Lifecycle

Secure sharing continues after delivery

The goal is not to make sharing difficult. It is to make the safe path the normal path, with defaults that reduce accidental exposure and a clear owner for exceptions.

• Confirm the recipient through a known channel when the request is unusual or financially sensitive.
• Record who owns the share and when access should end.
• Revoke unused or expired links rather than leaving them available indefinitely.
• Avoid creating duplicate copies across personal email, chat, desktop folders, and multiple cloud drives.
• Decide whether the recipient is expected to delete local copies and whether that expectation can actually be enforced.
• Escalate mistaken-recipient events quickly so access can be removed and downstream copies assessed.