End an outside recipient's file access when the work that justified it ends. Set the closing date when you share, name the person responsible, and check that the recipient can no longer fetch the files. A finished project should leave a clear record of which access ended and which obligations remain.
Give access a closing date and an owner
Record the files, recipients, reason for sharing, and an exact end date with a time zone. Choose a date tied to the work, such as acceptance of the final delivery, with a fixed expiry as a backstop. If the project finishes early, bring the access end forward.
Name one internal owner who can confirm completion and arrange removal. Give that person a backup for absences. An extension should require a fresh reason, an approved date, and a record of who agreed. Open-ended access leaves the next review dependent on somebody remembering the project.
Cancel every permission that reaches the files
Keep an inventory of the ways recipients can reach the shared material. Include individual links, direct file permissions, shared folders, and group membership. A folder can pass its permissions to the files inside it. Removing a direct file permission can therefore leave another route open.
At closeout, cancel project links and remove the recipient's project permissions wherever they appear. Review outside accounts and any software accounts used for automated transfers. Disable accounts dedicated to the finished work. For accounts serving other approved projects, remove only the completed project's access and verify the remaining scope. Keep unrelated work intact.
Test a recipient who is already signed in
Permission changes need a defined deadline for taking effect. Design each request for files to check the current permission, or document the maximum delay before an older permission stops working. A cached authorization is a saved permission decision reused by a service. That saved decision can outlast the change made in an administration screen.
Use a test recipient with the same permissions. Before ending access, open a file and keep the signed-in session active. After removal, try another file request through that session, a fresh sign-in, the old link, and any automated transfer route. Include a previously issued download address if the system uses one. Test expiry as well as manual cancellation.
Record the observed denial time. Check whether an existing transfer continues and document that behavior. If an old session or address still fetches files beyond the agreed deadline, keep closeout open while the owner resolves the gap. An access log can support this test; the actual request shows whether access has ended.
Handle downloaded copies separately
Cancelling access cannot claw back a file already downloaded to a recipient's device. Copies may also exist in email, local folders, or backups. Set expectations for those copies before sharing: permitted use, storage, return or deletion, and the evidence expected at completion. A deletion confirmation is a recipient's statement about their handling of copies, with limits on what your company can independently verify.
Retention means keeping records for an agreed period. Decide retention and deletion separately from permission removal. Ask the responsible records or legal owner to identify applicable contract terms and legal obligations, including any requirement to preserve records for a dispute or investigation. Document authorized exceptions and restrict retained material to the people who still need it. Outside access can end while an internal record remains.
A supplier closeout in practice
In a fictional example, Northfield Components shares drawings with a supplier for a prototype order. Maya, the project owner, records October 30 at 17:00 UTC as the access end. The inventory lists a drawing folder, two review links, and a supplier account used to download revisions.
Northfield accepts the prototype on October 27. Maya brings the end date forward, cancels both links, removes the supplier from the folder, and disables the project-only account. A test account already signed in can no longer fetch a revision. Maya records that result and requests the supplier's agreed deletion confirmation. The records owner keeps Northfield's accepted drawings under its retention schedule. Each action has its own evidence.
Acceptance checklist
- A named owner and backup have confirmed completion and the exact access end.
- Links, folder permissions, group membership, and relevant accounts have been checked.
- Existing sessions, saved permission decisions, and download addresses meet the denial deadline.
- Fresh sign-ins and automated transfers have been tested; continuing transfers are documented.
- Downloaded copies have a recorded return, deletion, or authorized retention outcome.
- The closeout record includes test results, remaining obligations, and owners for unresolved items.