--- title: "My rules don't move anything from Documents or Desktop" url: https://storagestudio.us/wiki/rules-dont-move-documents-or-desktop category: "Troubleshooting" tags: ["troubleshooting", "rules", "full disk access", "free up space"] summary: "If automatic moves never take anything from Documents, Desktop or Downloads, check Full Disk Access first, then the rule's age, the hard floor and whether you've opened the files recently. Preview the next run to see exactly what it would do." updated: 2026-10-01T05:37:44.000Z --- # My rules don't move anything from Documents or Desktop If automatic moves never take anything from Documents, Desktop or Downloads, check Full Disk Access first, then the rule's age, the hard floor and whether you've opened the files recently. Preview the next run to see exactly what it would do. If your rules never move anything out of Documents, Desktop or Downloads, the usual reason is permission: macOS protects those folders, and Storage Studio needs **Full Disk Access** to look inside them. If permission is fine, the files are probably just not old enough for the rule yet, or you've opened them recently — rules deliberately leave those alone. ## Likely causes - **Full Disk Access isn't granted**, or macOS has stopped honouring it after an update. Without it, Storage Studio can't see inside the protected folders, so a rule finds nothing to move. - **The files aren't old enough.** Each rule has an age; only items older than that are moved. - **The hard floor is higher.** **Hard floor — never act on anything younger than … days** in Settings → Rules overrides every rule. - **You've opened the files recently.** "Move rules use the age below, but keep any file you've opened recently — even if it's old — using macOS's own index, so a reference you still use isn't relocated." - **The automatic run hasn't happened yet**, or it was held. Automatic moves run once a day and don't run while automatic actions are paused, during quiet hours, or while the drive is disconnected. ```mermaid %% caption: Why a rule might not move anything from a protected folder flowchart TD A[Rule moves nothing from Documents or Desktop] --> B{Is Full Disk Access granted?} B -->|No| C[Grant it in System Settings, then Re-check] B -->|Yes| D[Run a preview of the next run] D --> E{Does the preview list files to move?} E -->|No| F[Files are too new, recently opened, or under the floor] F --> G[Lower the rule's age in Settings, Rules] E -->|Yes| H{Paused, quiet hours or drive disconnected?} H -->|Yes| I[Resume, wait, or connect the drive] H -->|No| J[Use Run Moves Now from the More menu] ``` *Flowchart — Why a rule might not move anything from a protected folder. Outline:* - Rule moves nothing from Documents or Desktop - leads to Is Full Disk Access granted? - Is Full Disk Access granted? - No: leads to Grant it in System Settings, then Re-check - Yes: leads to Run a preview of the next run - Run a preview of the next run - leads to Does the preview list files to move? - Does the preview list files to move? - No: leads to Files are too new, recently opened, or under the floor - Yes: leads to Paused, quiet hours or drive disconnected? - Files are too new, recently opened, or under the floor - leads to Lower the rule's age in Settings, Rules - Paused, quiet hours or drive disconnected? - Yes: leads to Resume, wait, or connect the drive - No: leads to Use Run Moves Now from the More menu ## How to fix it 1. **Check Full Disk Access.** Open **Settings…**, then **Permissions**. The **Full Disk Access** row should say **Granted**. If it doesn't, click **Open Settings**, switch Storage Studio on in the list, come back and click **Re-check**. If it already looks on in System Settings, switch it off and on again — macOS can stop honouring it after an update. See [Full Disk Access is on but the app says it isn't](https://storagestudio.us/wiki/full-disk-access-not-detected). 2. **Preview the next run.** Choose **Automatic Moves…** from the **More** menu and click **Run preview**. Lines starting "WOULD MOVE:" are what the next run would move; "WOULD KEEP (you've opened it recently):" are files it will leave alone. See [A dry run shows files I don't want moved](https://storagestudio.us/wiki/dry-run-shows-unwanted-files) for the opposite problem. 3. **Lower the rule's age** in **Settings → Rules** if you want newer items to qualify. A row may show "Will run as …d (floor)" — that means the floor in **Global overrides** is higher than the rule, and the floor wins. 4. **Run it now.** **Run Moves Now** in the **More** menu runs your rules straight away, without waiting for the overnight run. Your external drive needs to be connected. 5. **Check nothing is holding automatic work.** If the Home screen says **Automatic actions are paused**, click **Resume**. If **Run Moves Now** moves files but the overnight run never does, use **Contact Support** in the **More** menu and include your diagnostic logs — see [Sharing diagnostic logs with support](https://storagestudio.us/wiki/sharing-diagnostic-logs). ## What stays safe A rule that can't read a folder skips it rather than guessing — nothing is moved or deleted that it couldn't see. Everything a rule moves leaves a shortcut behind, so files still open from where they were. See also: [Rules: moving folders automatically](https://storagestudio.us/wiki/rules-and-automatic-moves) · [Why Storage Studio asks for Full Disk Access](https://storagestudio.us/wiki/full-disk-access) · [Quiet Hours](https://storagestudio.us/wiki/quiet-hours) · [The shortcut left behind after a move](https://storagestudio.us/wiki/the-shortcut-left-behind) · [Something's not working: start here](https://storagestudio.us/wiki/troubleshooting-start-here) ## What links here - [Full Disk Access is on but the app says it isn't](https://storagestudio.us/wiki/full-disk-access-not-detected) - [Rules: moving folders automatically](https://storagestudio.us/wiki/rules-and-automatic-moves) - [Something's not working: start here](https://storagestudio.us/wiki/troubleshooting-start-here)