How-to
·
5 min read

How to Revoke Shared File Access

Disable intended online access and understand the limits for ordinary downloaded or copied files.

Published byVDR Directory Editorial Team
Professional typing on a laptop at an office desk
On this page (7 sections)▼

Revoking access means closing the intended online path to a shared file. The task is complete only when you know which paths were open and have verified the relevant ones are closed.

It does not automatically recall attachments, erase downloads or remove screenshots. Treat revocation as an access change with a clear scope, rather than a promise to make the document disappear everywhere.

1. Inventory the ways the file can be reached

Combination padlock illustrating controlled access

Locate the source file, all active sharing URLs, room or folder memberships, and any public embeds. Ask the project owner about copies sent through email or another workspace. A dashboard showing one URL may not describe the whole disclosure.

Create a short register before changing settings. This also helps avoid interrupting recipients whose access should remain.

Access pathQuestion to answerNext check
Individual linkWhich audience uses this URL?Disable the intended URL
Recipient permissionWhich identity should lose access?Review membership or allowlist
Room or folderDoes another location expose the file?Check the separate permission scope
Ordinary copyWas it downloaded or attached?Follow the agreed handling process

For an urgent incident, follow your organization's response process while documenting the changes.

2. Choose the smallest appropriate access change

If one recipient no longer needs access, review the identity-level control. If an entire sharing event has ended, close the relevant link or room path. Avoid deleting the underlying record when you only need to stop future access.

Use the provider's supported revocation or deactivation operation. Read its help before treating deletion, expiry and disabling as interchangeable. SendNow's documented allowlist removal blocks that address on its next visit; this is different from claiming every active screen closes immediately. SendNow: Specified-user access

Record the selected scope, reason, owner and time. A colleague should be able to tell whether you closed one URL, removed one person or stopped all external access.

3. Verify from the recipient side

Professional reviewing paper documents at a workspace

Use a harmless sample to understand the operation before relying on it for confidential material. After the change, open the affected URL in a new recipient session. Check that the content is blocked with the expected message.

Test other known routes independently. A direct URL may have different permissions from a folder entry. If remaining recipients should retain access, test an authorized identity as well.

Keep observations about already-open sessions separate from observations about new visits. Do not claim that a refresh, browser cache or previously loaded content behaves a certain way without checking the actual service.

4. Handle ordinary copies separately

Professional holding a document folder at a desk

A downloaded PDF or Office file usually remains with its recipient after its original sharing URL stops working. Contact the appropriate owner when those copies need to be returned, deleted or retained under an agreement.

Some specialized protection systems govern supported files outside the original viewer. That is a separate capability with its own client, identity and offline-access rules. Verify it rather than assuming it is included in ordinary link sharing.

Revocation also cannot remove information from notes, photographs or memory. State the operational result precisely: the tested access path is blocked for the tested identity.

5. Preserve records and explain the outcome

Team working with laptops and reports

Save available activity and permission records before retiring a workspace when your retention process requires them. Keep the original release version in authorized storage. Document any paths that could not be checked and who will resolve them.

If access ended routinely, send a short message giving the reason and contact for renewed access. If the situation is sensitive, follow the designated communication process instead of improvising an accusation.

Do not silently reactivate an old URL during troubleshooting. A renewed business need deserves a new approval check and a verified access state.

Frequently asked questions

Ordinary link revocation does not recall an ordinary downloaded copy. A separately configured rights-management system may have additional controls, which need their own verification.

Do not assume so. Inventory and test all relevant URLs, room permissions and alternate sharing locations.

Use the appropriate access operation first. Deletion may remove useful records or affect legitimate recipients; preserve material according to the responsible owner’s instructions.

Before you share

Mark the task complete with a scoped statement: which identities and paths were closed, how new access was checked, and which retained copies require separate handling.

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.

VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.

Related Guides & Research

Recommended next reading for deal teams and transaction leaders.

View all →