How to revoke shared-file access, preserve data, and complete an employee offboarding handover
A controlled offboarding process must cover the account, group membership, file and NAS access, secure remote access, business systems, file ownership, mail, and documented handover.

Establish a factual baseline with “AD account disablement and offboarding process” and “group-membership cleanup”, then move to “share, NAS and cloud-drive permissions”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking AD account disablement and offboarding process, group-membership cleanup and share, NAS and cloud-drive permissions independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · AD account disablement and offboarding process | Checking AD account disablement and offboarding process helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of AD account disablement and offboarding process. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 02 · group-membership cleanup | Checking group-membership cleanup helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of group-membership cleanup. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 03 · share, NAS and cloud-drive permissions | Checking share, NAS and cloud-drive permissions helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of share, NAS and cloud-drive permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 04 · remote access to business systems | Checking remote access to business systems helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of remote access to business systems. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 05 · file ownership and data handover | Checking file ownership and data handover helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of file ownership and data handover. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 06 · audit records and retention period | Checking audit records and retention period helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of audit records and retention period. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
Investigation and change sequence
- Capture a baseline for AD account disablement and offboarding process and group-membership cleanup and compare it with a known-good system.
- Correlate evidence from share, NAS and cloud-drive permissions and remote access to business systems to distinguish the direct fault from dependent symptoms.
- Only if evidence points to file ownership and data handover, plan a controlled change with backups, a change window and rollback triggers.
- Finally check audit records and retention period and the real business workflow. Confirm the final effective access and application behavior for real file, print or share workflows.
Validation and rollback evidence
- Confirm the final effective access and application behavior for real file, print or share workflows.
- Recheck file ownership and data handover and audit records and retention period against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming AD account disablement and offboarding process is sufficient while overlooking group-membership cleanup and dependent checks.
- Changing several settings before preserving the original evidence for share, NAS and cloud-drive permissions.
- An administrator being able to access a file does not prove normal users have the intended rights.
Common questions and acceptance criteria
What should be checked first?
Begin with AD account disablement and offboarding process and group-membership cleanup. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Confirm the final effective access and application behavior for real file, print or share workflows.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
