ONE FILE ACCESS REMOVAL WORKSHEET
HowCurio | Original planning resource
Examples below are modeled permission states, not results from a live tenant.
This worksheet does not certify account offboarding or erase downloaded copies.

File name / exact URL: _________________________________________________
Target person's exact invited / signed-in identity: ______________________
Requested scope: one file / one folder / entire collaboration: ____________
Owner authorized to approve this scope: _________________________________

For EACH route, record:
Route ID / direct grant, link, folder, site, group: _______________________
Where granted / parent URL if inherited: ________________________________
Audience and permission before: ________________________________________
Other people affected if this route is removed: _________________________
Action approved / person responsible: ___________________________________
Observed permission after / date and observer: __________________________
Remaining route or unknown: _____________________________________________

Recipient access check, if performed in their own session: _______________
Continuing collaborator check, if performed: ____________________________
Local copy issue referred to file owner separately: _____________________
Closure: recorded routes removed / actual access checked / unresolved
Exact limitation and next owner: ________________________________________

WORKED CASE A: Budget-review.xlsx
Morgan has direct View plus named link L1 for Morgan and Priya.
Remove direct View: L1 still grants Morgan a route.
Remove Morgan from L1 if supported, or replace L1 for Priya and delete L1.
Modeled final listed routes: Morgan 0, Priya 1. Tenant result untested.

WORKED CASE B: Launch-notes.docx
Morgan has direct Edit plus Campaign Members Read on the parent folder.
Remove direct Edit: group Read remains. File removal is incomplete.
Owner must decide whether Morgan leaves the whole collaboration or only
this file should have a narrower approved audience. Do not remove the
group's site permission just to address one member and one file.
Modeled final state: unresolved until the authorized scope decision.

WORKED CASE C: Pricing-draft.pdf
Anyone link L2 exists plus named link L3 for Morgan and Priya.
Remove Morgan from L3: a holder of L2 still has a bearer access route.
Delete L2 for all holders and arrange intended recipients' permitted access.
Modeled cloud routes for Morgan: none listed after both paths closed.
Other site/group paths must be checked; unknown is not zero.
Any downloaded ordinary unprotected copy is a separate issue.

MODEL NOTES
These states assume only the listed routes and identities. They omit
administrator access, policy exceptions, protected-file rules, and future
resharing. Record your real account observations in the blank fields.