trio.so
How-Tos

How to Configure a Privacy Preferences Profile (PPPC) on macOS

How to set up a Privacy Preferences (PPPC) profile on macOS: what it can approve or only deny, the payload keys, MDM delivery, and the Mac settings.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A Privacy Preferences Policy Control (PPPC) profile lets an MDM decide in advance which apps on a Mac may use protected services, so users do not have to click through privacy prompts. You list each app by its bundle ID and code signing requirement, then set its access to a service such as Full Disk Access, Accessibility, Apple Events or specific folders to Allow or Deny. Camera and Microphone can only be denied, never pre-approved; Screen Recording and Input Monitoring can be denied or left for a standard user to approve. The profile only works when an MDM delivers it to an enrolled Mac; a profile installed by hand is ignored.

If you manage Macs and a security tool or agent keeps asking users for access, the PPPC sections below show how to set it up; if you just want to change privacy settings on your own Mac, go to "Accessing Privacy Settings".

Built-In Privacy Features of macOS

macOS protects personal data and sensitive parts of the system with a framework called TCC (Transparency, Consent and Control). Before an app can read your contacts, open files in Documents, control other apps or record the screen, macOS asks you, and the answer is stored per app.

That works well for one person on one Mac. In a company it creates two problems: users get prompts they do not understand and click Don't Allow on a security tool that needs access, or they allow things they should not. A PPPC profile moves those decisions from each user to IT.

macOS also includes a firewall, FileVault disk encryption and Gatekeeper, which are configured separately (see below).

How to Configure Privacy Preferences Profile on macOS

For IT, configuring privacy preferences means building a PPPC payload and delivering it through MDM. For a single user, it means the Privacy & Security pane in System Settings. Both are covered here, admin steps first.

What a PPPC Profile Can and Cannot Do

Service (payload key)What PPPC can doExample
Full Disk Access (SystemPolicyAllFiles)Allow or denyEndpoint security and backup agents
AccessibilityAllow or denyRemote support and automation tools
Apple Events (AppleEvents)Allow or deny one app controlling anotherA script tool sending events to System Events
Files and folders (SystemPolicyDesktopFolder, DocumentsFolder, DownloadsFolder, NetworkVolumes, RemovableVolumes)Allow or denyA sync client that reads Documents
Contacts, Calendar, Reminders, PhotosAllow or denyA CRM app that reads contacts
Camera, MicrophoneDeny onlyBlock an unapproved app from the camera
Screen Recording (ScreenCapture), Input Monitoring (ListenEvent)Deny, or let a standard user approveLet staff approve screen sharing for a video tool

The deny-only rule is Apple's: camera, microphone and screen access stay the user's decision, so an MDM can block an app but cannot silently grant it.

Building the PPPC Payload

The payload type is com.apple.TCC.configuration-profile-policy. Under Services, each service holds a list of app entries with these keys:

  • Identifier: the app's bundle ID (for example com.example.agent) or, for a command-line tool, its path.
  • IdentifierType: bundleID or path.
  • CodeRequirement: the app's designated code requirement, so the rule applies only to the genuine, signed app.
  • Authorization: Allow, Deny or AllowStandardUserToSetSystemService (Screen Recording and Input Monitoring only).
  • StaticCode (optional): validate the code requirement against the app on disk.

Apple Events entries also name the receiving app with AEReceiverIdentifier, AEReceiverIdentifierType and AEReceiverCodeRequirement. To get an app's code requirement, run this in Terminal on a Mac that has the app installed:

codesign -dr - /Applications/ExampleAgent.app

Copy everything after designated =>. Most security and remote support vendors publish a ready PPPC configuration for their agent, which is the safest starting point.

Delivering the Profile with MDM

macOS accepts a PPPC payload only from an MDM, on a Mac enrolled through Automated Device Enrollment (Apple Business) or a user-approved MDM enrollment. Double-clicking a .mobileconfig file with a PPPC payload installs nothing useful. Deploy the profile before the app it covers, so the app never shows a prompt. To check what a Mac has received, run sudo profiles show -type configuration in Terminal.

Accessing Privacy Settings

On macOS Ventura and later, open the Apple menu > System Settings > Privacy & Security. (Before Ventura this was System Preferences > Security & Privacy > Privacy, with a lock to click before making changes.) The pane lists each protected service, such as Location Services, Camera, Microphone, Full Disk Access and Accessibility.

Managing App Permissions

Click a service to see which apps have asked for it, and switch each app on or off. Some services, such as Full Disk Access, also let you add an app with the plus button. Settings that an MDM set through a PPPC profile appear greyed out and cannot be changed by the user. Review the list now and then and remove access from apps you no longer use.

Location Services Settings

Under Privacy & Security > Location Services, you can turn location off for the whole Mac or for individual apps. On work Macs, leave it on only for the apps that need it.

Your Privacy Preferences Profile: Key Features to Customize

A PPPC profile covers app permissions only. These related settings are separate payloads that IT usually deploys alongside it from the same MDM.

Customizing the Firewall Settings

The macOS application firewall controls incoming connections. Through MDM, the Firewall payload turns it on, can block all incoming connections and enables stealth mode, and lists which apps may accept connections. For individual users it is in System Settings > Network > Firewall.

Enabling FileVault for Disk Encryption

FileVault encrypts the whole startup disk, so a lost or stolen Mac does not expose its data. Through MDM, a FileVault payload turns it on at the user's next login and escrows the recovery key. A single user turns it on in System Settings > Privacy & Security > FileVault.

Limit Data Sharing With Apple

System Settings > Privacy & Security > Analytics & Improvements controls whether the Mac shares diagnostic data with Apple and app developers. On managed Macs, an MDM restriction can turn off diagnostic submission so users do not have to.

Advanced Privacy Tips for Enhanced Security

Use a VPN for Better Privacy

For staff who work from home or travel, a company VPN or zero trust access service encrypts traffic on untrusted networks. Deploy its PPPC and network extension approvals together, so the client works without prompts.

Control Browser Privacy

Keep browsers updated, block third-party cookies where your sites allow it, and manage browser settings centrally rather than relying on each user.

Third-Party App Privacy Auditing

Check which apps hold Full Disk Access, Accessibility and Screen Recording on your Macs, and remove what you cannot explain. Those three are the most powerful permissions on a Mac. Security tools such as XProtect and approved system extensions (see macOS system extensions) cover the malware side.

Regular Updates

Install macOS and app updates promptly. Updates fix privacy and security flaws, and an outdated macOS may not support the newest PPPC keys.

Managing this across many devices

Setting privacy permissions Mac by Mac does not scale, and a single wrong click blocks a security tool. trio.so sends Privacy Preferences (PPPC) policies to managed Macs, so the apps you approve get the access they need without asking each user. See Apple device management.

The trio.so Create policy wizard for a macOS Privacy preferences (PPPC) policy, allowing Full Disk Access and Accessibility for two example apps.
In trio.so, a PPPC policy lists each app, the service and its access.

Conclusion: Take Control of Your Privacy

On a single Mac, privacy settings live in System Settings > Privacy & Security. Across a fleet, a PPPC profile delivered by MDM decides which approved apps get Full Disk Access, Accessibility and the other protected services, while camera, microphone and screen access stay with the user. Build each entry from the app's bundle ID and code requirement, deploy it before the app, and review the most powerful permissions regularly.

Related reading: macOS system extensions, Mac administrator accounts, two-factor authentication on Mac and XProtect for Mac.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Approve app access on every Mac without user prompts

trio.so sends Privacy Preferences policies to managed Macs, so the apps you approve get the access they need.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

A configuration profile with the Privacy Preferences Policy Control payload. It tells macOS in advance which apps may use protected services such as Full Disk Access or Accessibility, so users are not prompted.

Create a PPPC payload with an entry under SystemPolicyAllFiles for the app's bundle ID and code requirement, set Authorization to Allow, and deploy it from your MDM to the enrolled Macs before the app is installed.

No. A PPPC profile can only deny camera and microphone access. Approving them stays with the user. Screen Recording and Input Monitoring can be denied or set so a standard user can approve them.

On macOS Ventura and later, in System Settings > Privacy & Security. On older versions, in System Preferences > Security & Privacy > Privacy.

Transparency, Consent and Control: the macOS framework that asks for and records permission before apps use protected data and services. A PPPC profile sets TCC decisions through MDM.

Related

From the blog

The related industry news, interviews, technologies, and resources.