Find sensitive files sitting in a shared drive
Walk a file share's names and snippets and have Jev flag files likely to hold credentials, personal data or contracts.
The use case
IT and security teams know shared drives collect passwords in text files, HR spreadsheets and signed contracts in folders open to everyone, but nobody can read them all. This pattern lists file names, paths and short text snippets, and asks Jev whether each looks like it holds credentials, personal data or confidential business documents. Flagged files go to a review list sorted by probability. A security person checks each one and fixes the permissions; nothing should be deleted or moved automatically, and the scan itself must run with access the team is authorised to use.
Example workflow
- Export file paths and names from SharePoint or Google Drive
- Extract short text snippets where allowed
- Ask Jev Noul questions on credentials, personal data and confidential content
- Sort flagged files by probability in a review sheet
- A security analyst checks files and tightens sharing settings
Tools
- Jev (TypeSafe AI)
- Microsoft SharePoint
- Google Drive
Risks and guardrails
- Snippets sent to an API may themselves be sensitive
- Missed files give false comfort
- Scanning without authorisation is a policy breach
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Jev finds the sensitive files in a share by _xpn_ on Made with Jev: madewithjev.com/builds/jev-sensitive-files
- Jev finds the sensitive files in a share: original post or repo by _xpn_: x.com/_xpn_/status/2102739497829961734
- Google Drive (official page): developers.google.com/workspace/drive (checked 2026-11-19)