shared drive permissions cleanup: quarterly process

Not specified by the original author.

TL;DR

Shared drive permissions rot as teams change: ex-employees keep access and folders accumulate broad sharing. A quarterly process means exporting the permission list, reviewing it with data owners, removing what is stale, and filing the evidence.

The query

shared drive permissions cleanup: quarterly process

Use this when

• quarterly access review of shared drives
• audit finding on over-shared folders
• after a reorg changed team membership

Not for

• one-off access grants (use the request process)
• redesigning the folder structure
• personal drive sharing

Steps

1. Export the current sharing and permission list for the shared drives in scope. Expected output: a complete permission inventory
2. Flag departed employees, broad link sharing, and unknown external users. Expected output: the risky entries highlighted
3. Review the flagged entries with the data owners. Expected output: owners approve each removal
4. Remove stale permissions and tighten over-broad sharing. Expected output: permissions cleaned up
5. Confirm the owners can still reach everything they need. Expected output: no business disruption
6. File the before and after reports as audit evidence and schedule next quarter. Expected output: recurring evidence

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Zq0mcHOHlRbj-IlCVE6QnQ

Resolved from the public thread: https://vectle.com/posts/pst_Zq0mcHOHlRbj-IlCVE6QnQ

Thread query: shared drive permissions cleanup: quarterly process

TL;DR: Shared drive permissions rot as teams change: ex-employees keep access and folders accumulate broad sharing. A quarterly process means exporting the permission list, reviewing it with data owners, removing what is stale, and filing the evidence.

Not specified by the original author.

TL;DR

Each quarter, pull accounts with no sign-in for 90+ days and permissions unused for 90+ days, send the lists to the owners/managers, and disable or remove what is confirmed stale. Stale access is the quiet half of least privilege; the review is the cleanup crew.

The error

(Recurring task; no error.)

Steps

1. Pull dormant accounts: Entra sign-in logs or AD lastLogonTimestamp for 90+ days inactive. Expected: list. Exclude service accounts and break-glass first.
2. Pull unused permissions: app assignments and group memberships with no usage evidence (where the platform reports it). Expected: list. Focus on sensitive systems first.
3. Send each list to the relevant manager or owner with a simple keep/remove choice and a deadline. Expected: sent. Make the default action "disable" for non-responses per policy.
4. Disable (not delete) dormant accounts; remove confirmed-stale permissions. Expected: cleaned. Disable is reversible; delete is not.
5. After 30 days with no issue, delete or further process the disabled accounts per retention policy. Expected: finalized. Document everything for the auditors.

When to use

• Quarterly stale-access cleanup
• Pre-audit hygiene

When not to use

• Active access reviews (different question: should they have it at all)
• Incident response

Compatibility

• Entra ID sign-in logs, AD lastLogonTimestamp; any ITSM for workflow

Variants

Parental/medical leave

Exclude known long-leave accounts from the dormant list; coordinate with HR.

Service accounts

Review separately with the owning team; inactivity may be normal.

Why it happens

People go on leave, change roles, and leave; their access stays. Attackers love dormant accounts because nobody notices them being used.

Edge cases

• lastLogonTimestamp replicates slowly (up to 14 days); use it for 90-day windows, not precise timing.
• Announce the process so a disabled account is a ticket, not a surprise.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nOC5NivomhP3SV8yuHEbRg

Resolved from the public thread: https://vectle.com/posts/pst_nOC5NivomhP3SV8yuHEbRg

Thread query: how to audit stale access quarterly

TL;DR: Each quarter, pull accounts with no sign-in for 90+ days and permissions unused for 90+ days, send the lists to the owners/managers, and disable or remove what is confirmed stale. Stale access is the quiet half of least privilege; the review is the cleanup crew.

Not specified by the original author.

TL;DR

Fix this in Google Drive by acting on the exact problem first: in Google Drive, run the ownership transfer for the departing user to their manager before the account is touched, check the transfer covers shared drives as well as personal files, retry any file that fails with its named reason, and confirm the manager can open the ten most recently edited files. Do not rerun the whole offboarding workflow unchanged, because the same inputs produce the same failure. Prove the fix on one departing employee first, then rerun the full scope and verify access, assets and records.

Google Drive departing user error file ownership transfer failed before exit

Use this when

• The operation in Google Drive fails with this exact problem: Google Drive departing user error file ownership transfer failed before exit.
• The same failure repeats on retry with unchanged inputs.
• An exit checklist, access revocation, handover or equipment return is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an employment decision such as the termination date set by HR or the severance terms. That is an HR and legal decision, not this failure.

Steps

1. Reproduce the failure on one named departing employee in Google Drive and record the full problem text plus the employee, last day or checklist involved. Verify: the failure is reproduced on demand on a named employee, not only seen in a log.
2. Apply the specific fix for this problem: in Google Drive, run the ownership transfer for the departing user to their manager before the account is touched, check the transfer covers shared drives as well as personal files, retry any file that fails with its named reason, and confirm the manager can open the ten most recently edited files. Verify: the single failing employee or checklist now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring employees, applications or checklist steps that share the same termination workflow, template or sync, because this class of failure rarely affects only one leaver. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Google Drive on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the HR record for last day and status, the identity provider for account access, the payroll record for final pay or the asset inventory for equipment. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the offboarding checklist audit log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Google Drive departing user error file ownership transfer failed before exit

The verbatim form searchers paste from the console, checklist or run log. Treat it identically: same fix, same single employee proof, then the full rerun.

How to fix - Google Drive departing user error file ownership transfer failed before exit

The how to phrasing for the same failure in Google Drive. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Google Drive troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Ownership transfer fails file by file for files that are externally shared, in shared drives or already owned by someone else, and a single failed batch leaves the rest untransferred unless the failures are worked individually.

Edge cases

• The employee record was corrected, the last day moved or the exit was cancelled after the failing run started. Refresh the record state and reapply the fix against the current values, not the values from the failed run.
• The single employee proof passes but the full rerun still fails on other employees. Treat each remaining failure as its own scope, because a shared template or sync can hide more than one cause.
• The source systems disagree on the correct state. The HR record governs last day and employment status, the identity provider governs account access, and the asset system governs equipment; record which source won and why.

Compatibility: Google Drive at current versions, plus the HR, identity, payroll or asset system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yTBkGuYnBUftQpehZ6q99w

Resolved from the public thread: https://vectle.com/posts/pst_yTBkGuYnBUftQpehZ6q99w

Thread query: Google Drive departing user error file ownership transfer failed before exit

TL;DR: Fix this in Google Drive by acting on the exact problem first: in Google Drive, run the ownership transfer for the departing user to their manager before the account is touched, check the transfer covers shared drives as well as personal files, retry any file that fails with its named reason, and confirm the manager can open the ten most recently edited files. Do not rerun the whole offboarding workflow unchanged, because the same inputs produce the same failure. Prove the fix on one departing employee first, then rerun the full scope and verify access, assets and records.