“Who deleted it?” — What happens when your whole team shares one Google Drive login
Three people, one Google Drive, one shared login, and 1,200 client files gone. Nobody could say who did it.
The Teakfile teamNotes on sharing Drive safely
We run a small content team: three people, one Google Drive, and one shared login that we have all used for two years without thinking much about it.
Last month, on a Tuesday morning, someone deleted an entire client folder. It held 1,200 files.
It took us a few hours to track it down, but it was in the trash and we restored everything. Then came the question nobody wanted to answer: who did it?
Everyone said it wasn’t them, and we believed each other. It was most likely an accidental drag-and-drop, which can happen to anyone. But we couldn’t know for sure. There was no log and no history, only three people looking at a screen, each hoping the others didn’t suspect them.
The real problem isn’t trust, it’s the setup
“We didn’t have a people problem. We had a systems problem.”
When everyone logs in as the same Google account, Google can’t tell the three of us apart. It records what the account did, not what a person did. So on a shared login:
- Anyone can move or delete any file
- Anyone can download anything
- Nobody can find out afterwards who did it
That isn’t a fault in Drive. It’s how shared logins work. Everyone holds the same key, so there is no telling who unlocked the door.
“The shared login isn’t a shortcut. It’s a single point of failure for your entire file system.”
“But we trust our team”
So did we, and it doesn’t change anything. The risk with a shared login isn’t that your team will do something wrong. It’s that when something does go wrong, even by accident, you can’t work out what happened or fix it properly.
A new freelancer reorganises a folder structure they didn’t know was deliberate. Someone leaves, and their laptop keeps syncing for three more days before anyone remembers to change the password. None of that is malicious, but you can’t trace any of it.
What we needed instead
We looked at Google Workspace and decided it was too much. At ₹99 per seat for 30GB of pooled storage, it felt like overkill for three people who needed control over who can open which files, not Gmail, Docs and Meet.
Our list was short:
- Each person logs in as themselves, not as “the Google account”
- Each person sees only the folders that are relevant to them
- If someone deletes something, there’s a record of who did it
- If someone leaves, we can remove their access in one click, without changing a shared password that lives in seven people’s notes apps
What could have happened
This story could have ended badly. The folder might never have come back, and two years of working together could have soured over a drag-and-drop that nobody could prove either way. We were lucky the trash still had it, and not every team is.
If your team shares a Google Drive login, try this question:
“If a file disappeared today, would you know who touched it last?”
If the answer is no, or “we’d have to ask around and hope someone remembers”, that is the gap to close.
Key takeaways
- On a shared login, Google records the account’s actions, not a person’s, so nobody can tell who deleted a file.
- It’s not a trust problem, it’s a setup problem: accidents happen, and without a record you can’t understand them or fix them properly.
- Ask yourself: if a file disappeared today, would you know who touched it last? If not, that’s the gap.
Frequently asked questions
- Can you see who deleted a file in shared Google Drive?
- No. When a team shares a single Google account login, Google has no way to distinguish between users. All actions are logged under the account, not the individual.
- How do small teams manage Google Drive access without Workspace?
- Most small teams either share a single login (cheap but no accountability) or use Google Workspace (identity control but expensive storage pricing). A third option is a team access layer like Teakfile that sits on top of an existing Google Drive account and gives each member their own login and permissions.
- What happens when someone leaves a team that shares a Google Drive login?
- You need to change the shared password and notify everyone. Until you do, the former team member retains full access to all files.
Share this story
