A small office can use Claude (formerly Cowork) to tidy shared folders safely by connecting one folder at a time, setting permissions to Manual and asking first for a dry-run: a spreadsheet of proposed renames and moves with nothing changed. Approve it row by row, apply it to a copy, keep the change log for rollback, then schedule only read-only weekly reports.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe reason for all that caution is a detail that's easy to miss. Anthropic says Claude asks before permanently deleting any file (its safety page adds that this does not cover computer use), but renames and moves aren't deletions: they run under whatever permission mode is set, and Anthropic's help centre says Auto is rolling out as the default on Pro, Max, Ultra and Team plans. A tidy-up that renames 1,200 files can be finished before anyone has looked at it. And if the folder is synced (Dropbox, OneDrive or Google Drive on the desktop), every change lands on your colleagues' computers too. The safeguards below are cheap; an afternoon spent undoing a bad rename is not.
Which shared folders can Claude reach?
Claude reaches shared files in two ways: through Claude Desktop in folders you have connected, and through connectors to cloud storage, where each person's own access applies. In Claude Desktop, it reads and writes only in folders you've connected, and only while the app is open. Through connectors, it works with cloud storage directly: Anthropic's connector help page says that if someone can't open a file in the source system, Claude can't reach it from their account either.
| Where the files live | How Claude gets in | Can it rename and move? |
|---|---|---|
| Folder on the office PC, or a synced copy of Dropbox, OneDrive or Google Drive | Claude Desktop, folder connected | Yes, inside the connected folder |
| Dropbox | Dropbox connector | Yes: its listed tools include move, copy, create folder and delete |
| Google Drive | Google Drive connector | Partly: listed tools copy, create, update, share and trash files |
| SharePoint, OneDrive (Microsoft 365) | Microsoft 365 connector | No: it searches and reads, and creates and updates files only if an administrator turns on write actions; no move or rename tool is listed |
That last row surprises Microsoft 365 offices. The connector is good for finding things ("which job folder has the commissioning certificate for the dental practice?") but Anthropic's documentation lists no tool to move or rename files, so it can't tidy a library. If the shared library is synced to a PC, Claude Desktop can work on the synced copy; otherwise use Claude to produce the plan and apply it yourself. One more line from Anthropic's safety page matters for any office whose computers are managed by an IT provider: connecting local folders makes them reachable from a session in the cloud, so check what you've connected before you leave it there.
For connectors, set the limits before the first task. In Customize > Connectors, select the connector and open Tool permissions; tools are grouped into read-only and write/delete, and each can be set to Always allow, Needs approval or Blocked. One subtlety from Anthropic's help centre: in Auto mode, a tool marked Needs approval runs without asking unless an automated check flags it. Only Manual mode makes "Needs approval" mean a person approves, and only Blocked stops a tool in every mode.
What naming rules should I write before Claude touches a file?
Write naming rules for folders, file names, document types and photos before Claude touches anything, because a clean-up without written rules only swaps one person's habits for another's. The illustrative example here is a security installer with an owner, two office staff and four engineers, sharing a synced Dropbox folder called Jobs. Three years in, it held 2,140 files across 236 job folders: 386 photos still named IMG_ or DSC_, 52 documents with "final" or "final2" in the name, 129 loose files at the top level and 31 job folders named after a customer's first name rather than a job number. The rules the owner wrote in one sitting:
JOBS FOLDER: NAMING RULES (v1, saved as Jobs/_RULES.txt)
Folder per job: Jobs/YYYY/JOB-#### Customer - Site
e.g. Jobs/2026/JOB-1187 Dental practice - Rear car park
Subfolders: 01 Survey | 02 Quote | 03 Install | 04 Handover | 05 Maintenance
File names: YYYY-MM-DD_JOB-####_DocType_v#.ext
DocTypes: SurveyNotes, SitePhoto, Quote, Order, InstallPhoto,
CommissioningCert, Handover, MaintReport, Correspondence
Photos: keep camera date; add JOB number and DocType
Never: delete anything; overwrite a file; change a file's contents
Unsure? put it in Jobs/_Review with a note, don't guess
Notice the date format. Year-month-day sorts correctly in any file list, and Anthropic's own help centre gives batch renaming "with consistent patterns like YYYY-MM-DD formatting" as a standard Cowork example. Put the rules file inside the folder itself so it travels with every task, and so a new member of staff can read the same rules Claude follows. The broader thinking on structuring shared files for AI tools is in organising shared files so AI tools can use them.
What is a dry-run, and why start with one?
A dry-run makes Claude list every proposed rename and move in a spreadsheet without changing a file, which is the step that makes the rest safe. With the permission setting on Manual and only the Jobs folder connected, the office manager sends:
Read Jobs/_RULES.txt, then look through every folder and file in Jobs.
Do NOT rename, move or change anything.
Create Jobs/_Review/proposed-changes.xlsx with one row per file or
folder you would change. Columns:
current path | proposed path | proposed name | action
(rename / move / to-review) | reason | confidence (high / medium / low)
Rules:
- Take dates from the file's own content or photo date, not today.
- Take JOB numbers only from folder names, quotes or orders. If you
can't find one, action = to-review.
- Possible duplicates: action = to-review, never delete.
- Add a Summary tab: counts by action and confidence.
An illustrative Summary tab from the first run:
| Action | High | Medium | Low | Total |
|---|---|---|---|---|
| Rename | 988 | 174 | 42 | 1,204 |
| Move | 96 | 21 | 12 | 129 |
| To-review | n/a | n/a | n/a | 139 |
Reviewing 1,472 rows sounds daunting, but sorting by confidence makes it quick. High-confidence renames were checked by sampling 40 rows across different years; 39 were right, and the one mistake (a quote dated by when it was last edited rather than the date printed on it) led to a clearer rule. Medium and low rows were read individually, and 14 were rejected. The 139 to-review items went to a person: mostly photos from engineers' phones with no job number anywhere, plus 52 near-duplicates where a person had to decide which version was current. Total review time was about 90 minutes, for a folder that had defeated two previous tidy-up attempts.
What the dry-run caught that a live run would have broken
Two finds justified the step on their own. First, 11 job folders shared a customer name with a different site, such as two branches of the same estate agent, and Claude proposed merging their files into one folder. The confidence was "medium", the reason column said "same customer", and a live run would have mixed two sites' commissioning certificates. Second, a folder of scanned signed contracts had file names containing the customer's own reference numbers, which Claude proposed replacing with the office's job numbers. The contracts' names were deliberate, so the office manager added a rule: "Never rename anything in a folder called Signed."
If the spreadsheet side of reviewing proposed changes is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
Apply on a copy first, then on the real folder
- Make a trial copy of Jobs somewhere outside the synced area, say Desktop/Jobs-trial, and connect that folder in Claude Desktop instead of the real one.
- Apply only the approved rows: "Using proposed-changes.xlsx, apply every row marked Approved to Jobs-trial. Write each change to change-log.csv with old path, new path and time. Skip anything that doesn't exist and list it at the end."
- Check the counts. Files before and after must match: 2,140 in, 2,140 out. Any difference means something was overwritten or lost, and you stop.
- Open ten random job folders and check they make sense to someone who knows the jobs.
- Run it on the real folder at a quiet time, when nobody has files open, with the same prompt and a fresh change log.
In Manual mode Claude asks before each action it hasn't been cleared for, which is tedious for 1,333 changes. A reasonable compromise: Manual for the trial run, so you can watch the first few dozen actions and confirm they match the spreadsheet, then the real run with the same approved spreadsheet. Whatever you choose, never use the mode Anthropic calls "Skip all approvals" for file work; its help centre describes it as one where nothing checks Claude's actions at all.
How do I undo a bad Claude clean-up?
Undo a bad clean-up by asking Claude to reverse the change log, moving each file from its new path back to its old path, starting from the last row. The change log is the rollback plan. If something looks wrong a day later (an engineer can't find the survey photos for a job), the fix is a prompt, not an afternoon of searching:
Using Jobs/_Review/change-log-2026-11-14.csv, move every file from its
new path back to its old path, starting from the last row and working
up. Before changing anything, list what you'll do and wait. Report any
file that is no longer at its new path.
Rolling back in reverse order matters when a file was renamed and then moved: undoing the move first puts it back where the rename expects it. Keep each change log in _Review for at least three months, and keep a backup of the folder taken before the real run, as Anthropic's safety page recommends for important files. If your cloud storage keeps file history, that's a second safety net, but don't make it the only one.
Which weekly admin tasks can Claude run on a schedule?
Anthropic's scheduled tasks, available on all paid plans, run weekly or on other frequencies, and the safest ones are read-only reports that keep the folder clean and spot gaps. In the new Claude experience you describe the task and how often it should run in any conversation, answer Claude's questions, then review the proposed name, schedule and instructions and click Schedule. Set up manually from the Scheduled page, a task takes a name, the prompt, an approval mode, a frequency (hourly, daily, weekly, on weekdays or manually), an optional model and an optional folder.
Where the task runs decides what it can reach. Scheduled tasks run in the cloud with your connectors and files saved to your Claude account, so they keep going while the office PC is asleep. Pick a folder on your computer, and the task runs only while that computer is awake with Claude Desktop open. For a synced Dropbox folder, the connector is the more reliable route. Three tasks the security installer scheduled, all read-only:
| Task | When | What it does | Output |
|---|---|---|---|
| Naming check | Mondays, 8 a.m. | Lists files added to Jobs last week that break _RULES.txt | A short list with proposed names; nothing renamed |
| Handover gaps | Fridays, 2 p.m. | For jobs with install photos in the last 30 days, checks 04 Handover for a commissioning certificate | Jobs missing paperwork, with the engineer's name from the job folder |
| Maintenance due | First weekday of the month | Reads 05 Maintenance folders for last visit dates | Customers due a visit in the next 45 days |
For each, the Dropbox connector's read tools are set to Always allow and every write tool to Blocked, so even in Auto mode the task can look but not touch. An illustrative Monday result: "7 files added last week break the naming rules. 5 are site photos from JOB-1203 named IMG_2290 to IMG_2294; proposed: 2026-11-10_JOB-1203_SitePhoto_v1.jpg to v5. 2 are quotes saved to the top level of Jobs; proposed folder: Jobs/2026/JOB-1205." The office manager approves the renames in a normal supervised conversation, which takes two minutes.
A fourth task, kept read-only: the Monday inbox digest
Enquiries reach the office manager's Outlook inbox in Microsoft 365, and the Microsoft 365 connector's listed tools include Outlook email and calendar search, with no tool for sending. That's enough for a weekly digest without giving Claude any way to reply:
Every Monday at 7:30 a.m.: search my Outlook inbox for emails
received since last Monday that have no reply from us. Group them as
new enquiries, existing customers, suppliers, other. For each: date,
sender's company, one-line summary, what they're asking for.
Never quote passwords, alarm or door codes, bank details or anything
that looks like a security setting: write "contains sensitive details"
instead. Don't draft replies.
The line about sensitive details was added after the first trial run. An existing customer had emailed a new keyholder's details and their alarm code so an engineer could attend, and the digest repeated the code in its one-line summary. Nothing left the account, but a digest is exactly the kind of document that gets forwarded. After the change, the same email appeared as "Existing customer, keyholder change for maintenance visit, contains sensitive details". For a security installer that rule is non-negotiable; for most offices it's still a sensible default.
Anthropic's safety guidance on scheduling is blunt and worth following: start with low-risk tasks such as summaries, avoid sensitive data and actions that are hard to undo, don't schedule anything that sends messages on your behalf, review outputs after each run from the Scheduled page, and pause tasks you no longer use. So the installer keeps these supervised, never scheduled: renaming or moving anything, emailing customers about maintenance visits, and anything in the HR or accounts folders, which aren't connected at all. For more weekly prompts in the same spirit, see ten weekly admin prompts for small businesses.
What clean-up problems only show up later?
A few clean-up problems only show up later, such as dates taken from the wrong place or someone saving into the old structure mid-run. The dry-run catches most problems. Each has a symptom you can spot and a rule that prevents it next time.
- Dates taken from the wrong place. A file's "modified" date changes whenever someone opens and saves it, and sync tools can refresh it too. The symptom is a cluster of documents all dated the day of the clean-up. The rule: take dates from the content (the date printed on a quote, the photo's own capture date) and send anything without one to _Review.
- Someone saves into the old structure mid-run. An engineer uploads photos to a folder that no longer exists, and the sync tool quietly recreates it. The symptom is a stray folder with the old name next week. The fix: run at a quiet time, tell the team beforehand, and let Monday's naming check pick up anything that slipped through.
- Names that grow too long. Folder names with customer, site and job number, inside year folders, inside a shared drive, can produce very long paths, and some sync tools and older programs struggle with them. Keep the detail in folder names and keep file names short.
- Old habits refill the folder. Within a fortnight, new IMG_ files appeared because engineers upload straight from their phones. Rather than fight it, each job got a "_Drop photos here" subfolder, and the Monday task proposes names for whatever lands there.
A permission set-up for a small office, filled in
| Job | Permission setting | Connected | Write tools |
|---|---|---|---|
| One-off clean-up (dry-run and trial) | Manual | Jobs-trial only | Local folder only |
| Real clean-up run | Manual | Jobs only | Local folder only |
| Weekly scheduled reports | Auto acceptable | Dropbox connector | All Blocked |
| Approving weekly renames | Manual | Dropbox connector | move: Needs approval; delete: Blocked |
| Never connected | n/a | HR, Accounts, Signed contracts | n/a |
If several people will use Claude on the same folders, Team plans add central billing and admin controls for connectors, and Anthropic's help centre says Team and Enterprise admins decide whether Auto mode is available at all. For a sense of how a design office set up similar first tasks, five Claude admin tasks for architects is a close sibling, and keeping each recurring job in its own project is covered in one Claude project per recurring office job.
If you want help setting permissions for your own office, I offer one-to-one AI consultations for small businesses.
What does a Claude clean-up cost in hours and dollars?
In the security installer's illustrative sum, the one-off clean-up took about four and a half hours of staff time, and the weekly tasks replaced roughly two hours a week with about 15 minutes. That clean-up time was an hour writing rules, 20 minutes on the dry-run prompt and waiting, 90 minutes reviewing, an hour on the trial and checks, and 40 minutes on the real run. The two earlier attempts by hand had each stalled after a day. The weekly tasks replace roughly two hours a week the office manager spent chasing handover paperwork and maintenance dates, against about 15 minutes reading three reports and approving renames.
On cost, Claude's pricing page lists Pro at $20 a month billed monthly ($17 a month on an annual plan), and Team at $25 a seat a month billed monthly or $20 billed annually, for 2 to 150 people. Two Team seats come to $50 a month on monthly billing. Anthropic notes that agentic work uses limits faster than chat; if the big clean-up hits a limit, split it by year folder.
Signs the folder is staying tidy a month on
- Naming breaches fall week on week. If Monday's list isn't shrinking, the rules aren't being followed at the point of saving; that's a team habit to fix, not a Claude task.
- Handover gaps close faster. Count jobs on Friday's list that are still there the following Friday.
- Nobody asks where a file went. If they do, the change log answers it in a minute.
- _Review stays small. If it keeps growing, a rule is missing; read the items and add one.
The pattern holds for any shared folder: rules first, dry-run second, copy third, real run last, and a log you can reverse. Weekly automation only comes after the folder is clean, and only for jobs that look rather than touch.
Claude for office admin: questions owners ask
Can Claude (formerly Cowork) tidy a shared folder safely?
Yes, if you connect one folder at a time, set permissions to Manual and run a dry-run first, with nothing changed. Approve the proposed renames row by row, apply them to a trial copy, and keep the change log so any change can be reversed.
Will Claude delete files without asking?
Not by default: Anthropic says Claude asks for explicit permission before permanently deleting any file, though its safety page adds that this protection does not cover computer use. Renames and moves are different: they run under whatever permission mode you've chosen. That's why the method here never deletes, moves suspected duplicates to a review folder, and keeps a change log for every rename.
Can Claude tidy our SharePoint folders through the Microsoft 365 connector?
Not directly. The Microsoft 365 connector searches and reads SharePoint, OneDrive, Outlook and Teams content, and if an administrator turns on write actions it can create and update files, but Anthropic's connector documentation lists no tool to move or rename them (checked 20 November 2026). To tidy a SharePoint library, work on a synced local copy through Claude Desktop, or make the plan with Claude and apply it yourself.
Do scheduled tasks need my computer switched on?
Not if they use connectors or files saved to your Claude account: Anthropic says those run in the cloud even when your computer is asleep. A scheduled task pointed at a folder on your computer is different; it runs only while the computer is awake and Claude Desktop is open.
Which plan does a two-person office need?
A paid plan. Scheduled tasks and Cowork's file work need one, and Claude's pricing page lists Pro at $20 a month per person billed monthly, and Team at $25 a seat a month billed monthly ($20 annually) for 2 to 150 people, with central billing and no model training on your content by default.
Is Cowork still a separate product from Claude?
No. Cowork's file tools are now part of Claude, so this tutorial calls the tool Claude (formerly Cowork). Older guides and videos may still say Cowork and show earlier menus, so check Anthropic's current help pages for exact menu names before following one.
Further reads
- Alarm Company Software: Monitoring, Service and Billing, and Where AI Helps — Where job and billing software already covers admin for installers.
- Which Claude Skills Should a Small Business Install First? — Seven Claude skills to install first, in a safe order, with a broker's worked examples and a filled-in safety check for third-party skills.
- Claude (Formerly Cowork) vs ChatGPT Work: Which Cuts Owner Admin? — Run the same folder, customer-reply and weekly-report tasks in both tools, then compare checked owner time.
Browse all AI-for-business tutorials
Sources: claude.com (Cowork is now Claude announcement, Cowork product page, pricing, connector pages for Dropbox, Google Drive and Microsoft 365), Claude help centre (Claude Cowork and chat are one Claude; Get started with Claude Cowork; Use Claude Cowork safely; Schedule recurring tasks; connector tool permissions). Checked 17 November 2026.
