Skip to main content

Granting Accessibility to the FileWave Client for UI-scripting Filesets

Who needs this profile?

Use this guide if your macOS script Filesets automate the user interface, such as an osascript script that uses System Events to click a button, choose a menu item or send keystrokes. macOS can attribute these requests to the FileWave Client (fwcld), so a script may depend on permissions granted to that Client.

Not every AppleScript or shell script uses UI automation. Do not deploy an additional Accessibility grant simply because a Mac has the FileWave Client installed. Review the scripts and assign the profile only to Macs that need the approved automation.

These are powerful permissions. Accessibility permits control through macOS accessibility interfaces; PostEvent permits posting events to the system event stream. Restrict who can author and deploy scripts to Macs receiving these grants. The profile is not a substitute for reviewing the script's purpose and behavior.

What changes in FileWave 17.0?

The revised Privacy Preferences for FileWave Client v.6 profile removes these entries for com.filewave.client:

  • Accessibility
  • PostEvent
  • ScreenCapture
  • ListenEvent

Full Disk Access, folder access, AppleEvents and the other retained entries are unchanged by this particular change. Removing a ScreenCapture or ListenEvent entry is not the same as revoking an automatically granted permission: their previous AllowStandardUserToSetSystemService setting allowed a standard user to configure the permission; it did not silently grant screen recording or input monitoring.

The supplemental profile below grants Accessibility and PostEvent only, as requested for this compatibility workflow. It does not restore the entire older privacy profile. In particular, it does not add Full Disk Access, AppleEvents, ScreenCapture or ListenEvent entries.

Keep FileWave's automatic privacy profile installed. The supplemental profile uses a different identifier and is designed to coexist with it. TeamViewer's own privacy profile and FileWave Kiosk location permissions are separate workflows; this download does not configure them.

Prepare before the automatic profile changes

Timing matters. For affected Macs, install and verify the supplemental profile before the updated automatic privacy profile is delivered. Do not assume that waiting until each Client package is upgraded is sufficient: the automatic profile is delivered by the FileWave Server through MDM. Confirm the Server upgrade and profile-rollout timing with the administrator responsible for the upgrade.

Before deployment:

  1. Identify the script Filesets that perform UI automation and the Macs that receive them.
  2. Confirm that those Macs have user-approved MDM enrollment and the native FileWave Client. This classic PPPC payload is delivered through the device channel; it cannot be installed by double-clicking the download, and Apple's User Enrollment is not supported for this payload.
  3. Review existing PPPC profiles for conflicting settings. An explicit denial can prevent the intended grant; adding another profile is not a way to override a restrictive policy.
  4. Select a small, authorized pilot group. Use the same script, user-session conditions and application versions as the intended workflow. A privacy grant does not create a logged-in user session or make every root/background script capable of interacting with a user's desktop.
  5. Keep the existing automatic FileWave privacy profile and any separately required AppleEvents or application permissions. Accessibility and Full Disk Access are not interchangeable.

Download and inspect the supplemental profile

Download the supplemental profile: FileWave Client UI Scripting

This is an unsigned XML .mobileconfig profile, intended for import into FileWave and delivery through MDM—not manual installation. It contains no certificates, private keys or enrollment credentials.

Property Value
Profile identifier com.filewave.kb.client-ui-scripting
PPPC payload identifier com.filewave.kb.client-ui-scripting.pppc
Target bundle identifier com.filewave.client
Identifier type bundleID
Services Accessibility, PostEvent
Grant Allowed = true for each service
Scope System/device
Signing identity FileWave (USA), Inc., Team ID UWMR88SA8G

The bundle identifier used by PPPC and the identifier in the code-signing requirement are different values. Do not replace one with the other. The included code requirement is:

identifier "com.filewave.fwcld.pkg" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "UWMR88SA8G"

The code requirement pins the current FileWave (USA), Inc. signing identity. The obsolete FileWave Europe Team ID is not included.

Import and deploy

  1. Download the profile and import it into FileWave Central as an Apple Profile Fileset. Review the imported Privacy Preferences payload before saving: it must target com.filewave.client and contain only Accessibility and PostEvent grants with the code requirement above.
  2. Name the Fileset clearly and target only the approved pilot Macs. Do not replace or remove the automatic Privacy Preferences for FileWave Client profile.
  3. Publish the intended assignment using Update Model. Coordinate with other administrators: Model Update can publish other pending model changes too.
  4. Confirm that the supplemental profile is installed on each pilot Mac. A saved Fileset or committed model is not proof of MDM installation.
  5. Verify the actual UI-scripting workflow before and after the automatic profile is updated to v6, using an authorized pilot. Check that the intended UI action occurred; do not rely only on script exit status or Fileset status.
  6. Once the pilot and rollout timing are approved, extend the assignment only to the affected Macs before their automatic profile changes.

If a script still fails, check the installed profile, Client signing identity, any explicit deny policy, logged-in session, the target application, and separately required AppleEvents permissions. Keep the scope narrow; do not delete TCC databases, disable macOS security controls or reinstall the older automatic profile as a workaround.

What users may see on macOS

macOS 27 can display a notification when Accessibility access is managed. A notification about a grant does not mean that the Client is currently controlling the interface.

macOS 27.3 Beta 2: FileWave's PPPC Accessibility grant appears under Privacy & Security → System & App Protection Override, locked as managed by a profile. The Accessibility pane still exists separately. Apple describes a Live Activity indicator while an app actively uses Accessibility; a notice about the grant alone does not establish that a script is running.

These 27.3 interface details are beta-specific and may change before the final macOS release. The name of the PPPC service in this profile remains Accessibility.

When the additional grant is no longer needed

Retire or replace the dependent UI-scripting Filesets first. Then remove only this supplemental profile's assignment from the affected Macs through the normal profile-removal workflow. Verify its removal and the intended remaining workflows. Do not remove FileWave's automatic privacy profile, TeamViewer profiles or unrelated permissions as part of this cleanup. Other installed profiles may continue to grant the same service.