Apple introduced revised application-permission controls in macOS 27.3 beta 2 on Nov. 16, 2026. The company urges developers to accommodate narrower access. Its announcement gives no stable-release date.
New requests, existing grants
Device Control and Data Access separates into System & App Protection Override and Accessibility. An indicator appears when one app controls another through System & App Protection Override. The changes apply to new permission requests. Previously granted permissions remain in effect.
Apple’s Oct. 2 notice framed the issue around Full Disk Access, which enables backup applications to work across protected information. It also described broader exposure when developers use that permission for other purposes, including files, messages and browsing history. For communication software, Apple said the privacy implications extend to the people with whom a user exchanges information. Apple’s stated goal was a more explicit user decision about granting access.
Operationally, the distinction is between completing an installation and deciding what information a workflow may reach, particularly when communications involve people other than the installer.
Two different access decisions
The macOS App Sandbox is a separate access-control system. Apple’s configuration guide says it restricts an app’s access to file locations, networks and hardware. Developers declare the capabilities their software needs through entitlements. That declaration normally does not replace the person’s separate permission to use a protected resource.
Apple’s companion security guide describes the limits for a sandboxed application: it does not have unrestricted access to a user’s home folder, and an embedded command-line tool must inherit its host application’s sandbox settings. These are existing platform mechanics, not new restrictions announced for every AI agent. The distinction matters when a product combines a graphical application with background tools: the components’ execution boundaries and their permission requests answer different questions.
Designing for a refusal
Apple’s protected-resource guide sets out another part of that workflow: an application explains why it needs data, and the person chooses whether to approve. A purpose string supplies that explanation rather than granting access itself. The guidance also covers protected-resource access originating in external libraries and SDKs.
The guide says software should check its current authorization status because people can change permissions later. Where there is no dedicated API, it calls for handling an access failure gracefully. These are general developer principles, not a specification for the new macOS permission interface. For product teams, they separate requesting a capability from keeping a useful application running when the answer is no.
