A shared-drive file does not belong to the person who uploaded it. It belongs to the Workspace organization. That changes where Trash is selected, who may restore the item, and which administrator can help after permanent deletion.
Fast route: In Drive, open Trash, use the Deleted from filter to select the shared drive, choose the file, and restore it. Google documents that restoration requires at least Contributor access.
1. Confirm the file was in a shared drive
- Open drive.google.com with the work or school account.
- Select Shared drives.
- Confirm that the expected drive still appears.
- Search within that drive by filename or file type.
- Open View details > Activity for the drive or nearby folder.
If the entire shared drive is missing, membership may have been removed. Contact the person who granted access or a Workspace administrator. Searching My Drive will not reveal organization-owned content that the account can no longer access.
2. Restore from the correct Trash
Google's current shared-drive instructions use a Trash source filter:
- Select Trash in Drive.
- At the top, open the arrow beside Deleted from.
- Choose the relevant shared drive.
- Select the deleted file.
- Choose Restore.
- Return to the shared drive and verify its folder.
Files remain in Trash for up to 30 days. A shared-drive Manager can permanently delete an item sooner. Google states that restoring a shared-drive item requires at least Contributor access, so a viewer or commenter may see fewer recovery controls.
3. Map the role to the available action
| Situation | Person to involve | Reason |
|---|---|---|
| File is visible and you are Contributor or above | You may restore it | Google permits shared-drive Trash restore |
| File is visible but Restore is unavailable | Content manager or Manager | Your role may be insufficient |
| Shared drive no longer appears | Manager or Workspace admin | Membership may have changed |
| Trash was emptied | Workspace admin | Self-service restore is finished |
| File was under legal retention | Workspace admin or records team | Vault policy may control availability |
Do not ask the original uploader to check personal Trash unless the item was never actually moved into the shared drive. Once added to the shared drive, the organization owns it.
4. Separate deletion from a move or access restriction
A file can disappear because it moved to another folder or entered a limited-access folder. Search the shared drive from its root and inspect Activity around the last known time.
Provide the old URL to a Manager. A request-access page can indicate that the file remains present but the containing folder now restricts access. Restoring a similarly named copy would create parallel records and would not repair the permission path.
5. Escalate after the shared-drive Trash is empty
Contact the Workspace administrator immediately and send one precise incident description:
- Workspace domain and shared-drive name;
- file or folder title and old URL;
- approximate deletion date and time zone;
- account that deleted or last edited it, if known;
- whether a Manager emptied Trash;
- original folder path;
- business deadline and data sensitivity.
The administrator can evaluate Drive audit events, recovery options, and retention policy. Available recovery depends on timing and organization settings; it should never be promised in advance.
If an entire folder was deleted, list critical child files rather than asking for a vague “whole drive restore.” A narrow request reduces ambiguity and accidental restoration of unrelated content.
6. Verify organization context after restore
Open the restored item and confirm:
- It returned to the intended shared drive rather than My Drive.
- Its parent folder is correct.
- Expected collaborators can open the old URL.
- Comments, version history, and metadata are present.
- Linked files, embedded assets, or shortcuts still resolve.
- A responsible team member is assigned as the operational owner.
For Docs, Sheets, and Slides, inspect editor version history if content is older than expected. Drive restoration recovers the item; it does not select a different document revision.
7. Handle folders and shortcuts carefully
Restoring a folder does not guarantee that every collaborator retained permission to every nested item. Limited-access folders can intentionally narrow access below the shared-drive level. Test with an affected user rather than relying solely on a Manager's view.
A shortcut is not the target file. If a restored shortcut reports that the item is unavailable, locate or recover the target using its own owner, location, and deletion trail.
Decide from the evidence
| Evidence | Likely event | Next action |
|---|---|---|
| Item appears under shared-drive Trash | Recent deletion | Restore with sufficient role |
| Restore control is absent | Role limitation | Ask Content manager or Manager |
| Old URL requests access | Permission or folder restriction | Inspect access and Activity |
| Shortcut returns missing target | Target moved or deleted | Trace target file separately |
| Entire drive vanished | Membership change | Contact Manager or admin |
| No item remains in Trash | Permanent deletion or retention event | Escalate with timestamp and URL |
Reduce future recovery time
Keep high-value files in a clearly named shared drive rather than a person's My Drive. Assign at least two active Managers, document restricted folders, and review membership when staff roles change. For major releases, keep a dated export or independent backup according to organizational policy. Avoid giving Manager privileges merely for convenience because that role can permanently delete shared-drive content.