Granting Full Disk Access to the FileWave Client on macOS
When FileWave needs Full Disk Access
Full Disk Access allows the FileWave Client (fwcld) and operations attributed to it to read protected data on a Mac. A script Fileset that reads existing files in a user's Documents or Desktop folder can need this permission even when other FileWave tasks work normally.
Quick answer: For an MDM-enrolled Mac, keep FileWave's automatic privacy profile installed and verify that it grants Full Disk Access. When approving access manually through the macOS 27.3 Beta 2 flow, choose Bypass System Protections and complete the full-access confirmation. Choose Folders is not a working substitute for the FileWave Client in this tested configuration.
Version scope: These steps cover FileWave Client 17.0.0 on Apple silicon running macOS 27.3 Beta 2. The interface and behavior may change before the final macOS release. Check your FileWave release’s platform requirements before deploying that macOS version.
Recognize the symptoms
Missing Full Disk Access does not necessarily stop the Client from checking in or delivering content. In the tested configuration:
| Operation | Without Full Disk Access, or with Choose Folders only |
|---|---|
| List protected user folders or read existing user-created content | Access was denied. Scripts can report Operation not permitted. |
| Deploy new files into Desktop or Documents | Deployment succeeded. |
| Read back files the Client deployed itself | Reading succeeded. |
| Upload inventory | Upload succeeded. |
A successful inventory upload or file deployment therefore does not establish that a script can read existing protected user data. Conversely, Operation not permitted is a reason to investigate permissions, not proof that every failure has this cause.
Before granting access
Full Disk Access is a broad permission. Confirm that the requested operation is authorized by your organization, and restrict who can author and deploy scripts that use it. Use a non-sensitive test file for verification rather than opening personal content merely to test access.
Choose the route that matches the Mac:
- MDM-enrolled Mac: verify the managed grant first. Do not remove a working privacy profile to try the manual route.
- Mac without an MDM-managed grant: an administrator must complete the manual approval. A standard user cannot approve full access without administrator authentication.
MDM-enrolled Macs: verify the managed grant
FileWave delivers its automatic Privacy Preferences for FileWave Client profile through MDM. This classic Privacy Preferences Policy Control (PPPC/TCC) profile provides Full Disk Access for the Client. In the macOS 27.3 Beta 2 test, the managed grant continued to work.
- Confirm that the Mac has user-approved MDM enrollment and that the automatic FileWave Client privacy profile is installed—not merely assigned or awaiting delivery.
- On the Mac, open System Settings → Privacy & Security → Full Disk Access and locate FileWave.app. In the tested beta, the managed entry was enabled, could not be turned off by the user, and displayed “This setting has been configured by a profile.”
- Run the verification described below using the FileWave-delivered operation that needs access.
If the profile is missing or the operation is still denied, investigate profile delivery and applicable privacy policies before adding another grant. See macOS Privacy Preferences Payload for the classic PPPC workflow. Keep the automatic profile installed; the separate Accessibility supplement is not a replacement for it.
Manual approval on macOS 27.3 Beta 2
Choose full access, not folders. Selecting Choose Folders can leave a folder visibly enabled for FileWave.app while the Client still cannot list it or read existing user content. The folder grant in this test was stored for the user, but the FileWave Client runs as a system service.
- Open System Settings → Privacy & Security → Full Disk Access.
- Locate FileWave.app and turn on its access. The FileWave Client application is located at
/usr/local/sbin/FileWave.app; do not grant access to Terminal or another application as a substitute for the Client. - In “Choose Folders for ‘FileWave.app’ to Access Instead of Full Disk Access,” select Bypass System Protections, not Choose Folders.
- Read the next warning. Confirm each of the three categories covering all data, hidden and recently deleted photos, and browsing history. In the tested beta, each category required OK before Turn On Full Disk Access became available.
- Select Turn On Full Disk Access and complete administrator authentication using the offered Touch ID or password prompt.
- Confirm that FileWave.app has Full Disk Access, then verify the actual operation below.
If FileWave.app is missing from the list or the displayed flow differs, confirm the installed Client and macOS versions before following these beta-specific steps. Do not approve an unrelated application to work around the missing entry.
Verify the operation that needs access
If it still fails, check the installed privacy profile or manual grant, any conflicting policy, the target path, ordinary file permissions, and the script's execution context. For support, retain the error text, Client/macOS versions, and whether access is managed or manual. Avoid including the user's private file contents.
Do not delete TCC databases or disable macOS security protections as part of this procedure.
Full Disk Access is separate from Accessibility
Full Disk Access concerns protected data. Accessibility and PostEvent concern UI automation; screen recording and remote-control tools have their own permission requirements.
FileWave 17.0's automatic Client privacy-profile change removes certain UI-related entries but retains Full Disk Access. If your script Filesets click buttons, choose menus, or send keystrokes, see Granting Accessibility to the FileWave Client for UI-scripting Filesets. Its supplemental profile does not add Full Disk Access.
No comments to display
No comments to display