What happened
Apple’s November 16, 2026 announcement describes changes arriving in macOS 27.3 beta 2 to two permission areas: Device Control and Data Access, and Full Disk Access. Apple frames the changes as a way to give users more transparency before granting access that could put data on a Mac at risk. The announcement does not provide a general release date for macOS 27.3.
Device Control and Data Access will be split into two settings: System & App Protection Override and Accessibility. Apple says users will grant permissions through a single method: selecting the requesting app from a list. The interface will encourage granting access only to the specific apps needed for a workflow under System & App Protection Override, or to specific folders for Full Disk Access. Apple also says the system will make more visible the range of data apps can access or control when full permissions are granted.
Users will have the option to configure apps to ask each time access is required. When an app controls another app using System & App Protection Override, a transparency indicator will appear. Apple says users will see the updates when approving new app permission requests. Permissions users have already granted remain in effect.
Apple tells developers to adjust onboarding and ensure their apps can gracefully handle access to only a limited set of folders or apps when using these APIs. Developers of disk-backup apps that use Full Disk Access, or accessibility technologies that use the new Accessibility settings, can request entitlements to provide the same experience for new installations as before macOS 27.3. Apple says known apps are not currently affected and will keep the same experience without an entitlement. It says additional entitlement details will be available soon. The announcement does not state a price, a separate access fee, or a general change to existing grants.
What the archive adds
New Runtime covered PrivacyLib, Meta’s shared enforcement library for data access on October 28, 2026. That note concerns agent-session context and checks at a data-access boundary; Apple’s announcement is a new event focused on macOS user permissions, not a continuation of Meta’s implementation.
Trend signal
This supports the idea that agent security depends on boundaries that constrain what software can access and authorize, rather than relying only on instructions. Apple is making permissions more granular and visible at the operating-system boundary, although its announcement is about apps generally, not specifically agents. See Agent security moves to runtime boundaries.
Why now
Apple says these controls are being introduced in macOS 27.3 beta 2 and will appear when users approve new permission requests. This gives developers a reason to review onboarding before the change reaches a general release, especially if their app assumes broad access at first launch.
Why it matters
Broad permissions simplify workflows, but they also enlarge the consequences of a compromised or misbehaving app. More selective folder and app grants can reduce that exposure, while per-request approval gives users another point at which to recognize unexpected access. The transparency indicator also makes cross-app control more visible.
For teams building automation or agent-enabled Mac software, the practical impact is not simply a new dialog. A workflow that previously depended on unrestricted access may become less reliable if the user grants only a subset. That means permission handling and recovery from denial become part of product design: explain why access is needed, request only what the task requires, and make failure modes understandable. Apple’s announcement does not establish that existing users will lose permissions; it says prior grants remain effective. The change chiefly creates a need to test new installations and restricted-access paths.
What happens next
- Apple will publish the additional entitlement details it says are forthcoming. (3 months, 80%). Watch for: updated developer documentation covering eligibility and the request process.
Limits and uncertainty
The announcement is about a beta, and Apple does not give a public release date for macOS 27.3. It says more entitlement details will follow, but does not yet explain the criteria, application process, or timing. Apple also says known apps are not affected for now; it does not define “known” in this announcement or explain how that status is determined. The practical behavior of individual apps under restricted folder or app access will depend on their implementation and user choices, and has not been independently tested here.
Skill to build now
Test a fresh installation with the narrowest permissions your workflow can reasonably receive. For each API-dependent feature, record which folders or apps it needs, then verify the app can explain a denial and continue safely when access is missing. This directly exercises the limited-access behavior Apple says developers should support.
Reader takeaway
macOS 27.3 beta 2 makes app permissions more granular and more visible, while leaving existing grants in place. Developers should prepare for new installs where access is limited: permission explanations, onboarding, and graceful failure are now part of the workflow rather than edge cases.
Open question
What criteria will Apple use to grant entitlements to preserve the previous experience for backup and assistive-technology apps?