Apple plans stronger Full Disk Access controls, but gives no release date

Apple described a future change to an unusually broad permission

Apple’s developer news notice on October 2 was short but consequential. Full Disk Access can let an app reach files and data that ordinary macOS privacy controls would otherwise protect. Apple says some developers have used the permission in ways that could expose files, mail, messages, and browsing history without users fully understanding what access they granted.

The post says Apple will add controls so a person who wants to grant this level of access must take a “very explicit” action. Apple connects the change to increasingly capable AI agents, which may act across more of a person’s apps and information. The announcement identifies a risk in the permission system; it does not accuse a named developer or say that every app requesting Full Disk Access is unsafe.

The original reason for the broad permission still matters. Apple says it largely bypasses the usual controls to allow backup apps to work properly. A restriction that is too blunt could disrupt legitimate tools as well as reduce unnecessary access. The product question is how Apple can make the scope clear while preserving cases where system-wide access is genuinely required.

The setting reaches beyond one file or one AI connector

Apple’s current Mac privacy settings guide describes Full Disk Access as permission to reach all files on the computer, including data from other apps such as Mail, Messages, Safari, and Home, Time Machine backups, and some administrative settings. The same guide lists Files & Folders separately as a way to let apps access files in different locations. That contrast helps explain why Apple calls Full Disk Access extraordinary: it is a system-level grant, not permission to one folder or one conversation.

A person often thinks about access in terms of a task: “read this file” or “summarize this message.” The operating-system setting, however, may authorize an app to read far more than the task needs. The risk can extend to other people, because mail and message stores contain what colleagues, friends, and family members sent. Apple specifically notes that communication apps could compromise the privacy of people on the other side of those exchanges.

This is also a different boundary from giving an agent access to a single online connector. A service-level permission may govern actions inside one account; Full Disk Access operates at the Mac level and can expose local data from multiple apps. The October 2 notice does not say how the proposed control will interact with a particular AI agent or its own permission screen.

The backup exception is not an abstract edge case. A backup utility may need to read data across many folders to create a complete restore point; an app that only summarizes one document has a different need. The current settings guide shows that macOS already distinguishes broader Full Disk Access from Files & Folders. Apple has not said whether the upcoming control will add a narrower permission, but users can still ask an app developer why the broad option is necessary for the task they plan to perform.

A release candidate appeared, but Apple did not connect it to this change

Apple’s October 2 notice uses future tense and does not identify a macOS version, an interface change, a developer migration rule, or a date. That is the most precise public status supported by the announcement: additional controls are planned, while the implementation and schedule are unspecified.

Apple’s developer release index lists macOS 27.2 RC, build 26B118, dated October 19. That confirms a release candidate exists, not that it contains the Full Disk Access change. The October 2 notice does not tie the update to 27.2, and the existence of a release candidate cannot stand in for a feature note.

TechRadar’s October 5 report said the first two macOS 27.2 betas predated Apple’s announcement and did not show the new controls. That was a useful snapshot at the time, but it cannot settle the contents of the later October 19 RC. Readers should treat a predicted release window as speculation unless Apple names a version or documents the new flow.

An explicit click helps only if the request explains its scope

A more deliberate confirmation can reduce accidental grants, but the wording matters. A prompt that only says “Allow Full Disk Access?” still asks a user to approve a large category without showing which data an app can reach or why it needs that access. A more useful design would explain the requesting app, the scope, the task that needs it, and whether a narrower choice is available. Apple has not described those details in the October notice, so this is a design question rather than a feature Apple has promised.

For a Mac user reviewing permissions today, the current settings page provides a baseline: Full Disk Access and Files & Folders are separate permission categories, and the former covers substantially more. A user can check which apps appear in the Full Disk Access list and ask whether each still needs it. That audit does not predict the new interface, but it can reveal permissions granted under an older workflow that no longer fit the current app use.

For example, someone setting up a backup tool should see that the request covers many locations and supports a full-device restore. Someone granting access to a writing assistant should be told whether it needs email, message archives, or browser history for the requested job. A strong confirmation would let the user compare that stated purpose with the actual scope before tapping allow. Apple has announced the need for explicit action, not that this level of explanation or a task-specific toggle will arrive.

Developers should wait for the actual API and compatibility details

The notice is a warning about the breadth of access, not a migration guide. It does not say that Apple will remove Full Disk Access, force apps to use one new API, or require every developer to change their software. Backup, endpoint-security, and other tools may have different needs, so developers need Apple’s eventual technical requirements before assuming what will break.

The next useful update should name the macOS version, show the consent flow, explain whether users can grant narrower access, and state how existing approvals will be handled. Until then, the concrete story is that Apple has recognized the risk of broad system access and promised a stronger user action, while the product details remain open. That distinction keeps a real policy signal from turning into a fictional release date.

A small organization can make a basic inventory while waiting: list each app with Full Disk Access, the task that relies on it, the person responsible for it, and the data it can reach. Review that list when an app changes purpose or a team member leaves. This is an internal housekeeping step, not an Apple requirement, and it does not replace the technical guidance Apple still needs to publish. It gives a team a concrete record to compare against the eventual prompt and migration notes.