KitaUpload All articles
Security & Privacy

The Last Day Is Not the Deadline: Reclaiming Files Before a Coworker Walks Out

KitaUpload
The Last Day Is Not the Deadline: Reclaiming Files Before a Coworker Walks Out

Photo: photographer not credited, Public domain, via Wikimedia Commons

Offboarding plans usually cover two things well: revoking access and transferring knowledge. Somewhere near the bottom of the list sits a third item — ownership — and that is where the trouble hides. Who actually controls the files, folders, and share links a person created while they were on payroll?

Most teams find out the hard way, usually on a Friday.

The quiet moment a file becomes an orphan

When an employee is deleted from a workspace, platforms handle their content in one of four ways: transfer it to a manager, leave it attached to a deactivated account, delete it, or keep it but strip the sharing settings. Every one of those outcomes is survivable if you planned for it. None of them are fun to discover mid-project.

The messier part is links. A file living in your storage might still be reachable through a URL the departing person generated months ago and pasted into a client email. Whether that URL still resolves — and whether it resolves for anyone with an internet connection — depends entirely on settings nobody wrote down.

Three ways orphaned ownership bites

Access breaks quietly. The shared folder stays visible, so nobody notices that permissions died with the account. Two weeks later, a designer cannot open the brand assets and assumes the drive is broken.

Live links keep living. Public or 'anyone with the link' permissions do not care that the creator is gone. Files stay fetchable until someone manually revokes them, and nobody thinks to check.

The audit trail goes cold. If you operate under SOC 2, HIPAA, or a client contract with data-handling terms, you may need to show who touched a record and when. A deactivated account with deleted activity logs is a bad answer during a review.

What 'owned' really means

In most cloud platforms, ownership is not about who cares about the file. It is about which account holds the permission record. Shared drives and team folders fix this by assigning ownership to a group rather than a person — but plenty of organizations still let employees create content in personal spaces, then share outward.

That single design choice is the root of the whole problem.

A checklist that actually fits a small team

Seven to fourteen days before the last day

On the last day

The week after

Contractors, agencies, and founders

Contractors are the classic blind spot because their work often originates in a personal account. Ask for a handoff export in a standard format, and get it before the invoice is paid.

Founders are the other one. The person who set up the workspace is usually the super admin, which means the entire organization's recovery options can live inside one former employee's login. Transfer admin roles to a group address early, not during a transition.

The cheap structural fix

Two habits prevent most of this. First, default new projects into shared, team-owned spaces instead of personal folders. Second, label every outbound link with its purpose and owner so a replacement can find and revoke it without guessing.

Neither takes a budget. Both take about ten minutes of setup — and they turn a time bomb into a routine checklist item.

All Articles

Related Articles

Fifteen Minutes to Find Every Risky Link You've Ever Shared

Fifteen Minutes to Find Every Risky Link You've Ever Shared

Stop Digging Through Folders: The Case for Search-First Cloud Storage

Stop Digging Through Folders: The Case for Search-First Cloud Storage

Six Files That Should Never Ride a Public Link (And the Settings to Use Instead)

Six Files That Should Never Ride a Public Link (And the Settings to Use Instead)