You want an assistant to work on one document. Its setup asks for a permission that reaches into other parts of your digital life. That is the moment to slow down and connect the size of the request with the size of the task.

Full Disk Access is a powerful permission on a Mac . Apple’s settings guide describes access that includes information from other apps, such as Mail, Messages and Safari, as well as backup data. It is a much broader grant than handing an assistant a selected document.

The permission and the task answer different questions. The task says what you want done. The permission helps determine what the software can reach while doing it. A reassuring description of the task does not make those two things identical.

What Apple’s October notice actually promised

In its October 2 announcement , Apple said it would introduce additional controls requiring more explicit user action before granting Full Disk Access. It warned that some developers were seeking broad access without users fully understanding the exposure.

Apple also raised a human consideration that can disappear inside a settings screen. Conversations contain other people’s information. Giving an app access to your messages can affect someone who never chose that app.

The October notice did not specify a release date, named macOS version or finished approval sequence. Read that as the scope of that announcement. For the steps available on a particular Mac, use Apple’s maintained guidance and the controls shown by that macOS version.

The underlying question survives any change in the interface. Can the person granting access explain why this particular app needs it?

The Mac permission and the assistant’s switch

The contemporary dispute involved Meta ’s Muse assistant. Reuters’ report by Stephen Nellis described Jason Aten’s complaint that Muse read private messages. Aten said he had not enabled Full Disk Access. Meta spokesperson Andy Stone maintained that reading Messages required both Full Disk Access and a separate Messages connector.

Apple’s notice did not name Meta or Muse. The timing supplies context, but it does not establish that Apple identified Aten’s complaint as the reason for its plan.

Dan Goodin’s account reports security researcher Patrick Wardle questioning whether an assistant’s own Messages switch defines everything software with Full Disk Access can technically read. Meta maintained its two-setting position.

The practical distinction is easier to see with an ordinary example. Imagine giving a helper a key to a filing cabinet, then asking them to read only one folder. The instruction matters. The key still opens the cabinet. That comparison explains the permission question, rather than resolving what happened on Aten’s Mac.

A connector is an app’s connection to a service. Full Disk Access is a broader system permission. Review them separately, then look at how the developer explains their relationship.

Put the task into words before approving access

Take a hypothetical assistant asked to summarize a selected project brief. Write the task down in those terms. Then ask which information is necessary to complete it. The brief is easy to identify. A whole message history needs a separate explanation.

Now change the task. Suppose the assistant must find project decisions distributed across correspondence. That wider job may justify different access, but the relationship should still be understandable. A more ambitious task does not make every available source relevant by default.

This is the principle of least privilege in everyday terms: give software the access its job needs. The useful question is not whether an assistant could do more with more information. It is whether the access fits the work you have chosen.

Before granting it, ask:

  • What information does this task need?
  • Why does the app need broad access rather than a selected file, folder or service?
  • Where can I review, change or remove that access afterward?

The OpenShell and Sentry article explores a related idea: a restriction enforced outside the agent’s own stated intention. Our Muse connected-devices coverage follows the question into actions an assistant can perform through another device.

Make room for useful Mac software too

Matthew Allard’s Newsshooter coverage brought Apple’s notice to a creative-work readership. A Mac holding client correspondence, drafts and personal files makes the stakes tangible. Those are examples of information worth considering, not reports of a particular project being exposed.

Jake Peterson’s Lifehacker article considered the consumer setup problem. Its suggestions about future warnings and settings were interpretation, rather than an interface Apple had shown in the October notice.

John Voorhees’ MacStories response raised another useful concern. Legitimate Mac utilities also use Full Disk Access, and he challenged a framing centered on backups.

A backup app and an assistant can request the same permission for different reasons. Good consent should help a person understand those reasons, including the useful work that may stop if access is removed. The explanation needs to be specific enough to support a decision.

Start with one app in System Settings, under Privacy & Security. Check its relevant permissions using Apple’s guide, then review any connections inside the app. If the developer’s explanation leaves a gap between the task and the requested access, pause the setup and investigate that gap.

One document is a concrete request. Broad access should come with an equally concrete reason.

FAQ

Is Full Disk Access the same as an assistant’s Messages connector?

No. Full Disk Access is a macOS permission. The connector is an app setting. Review both and how the developer says they interact.

Does granting Full Disk Access automatically send every file away?

No. It grants broad access. What the app does with that access depends on its behavior and design.

What should I check before granting an AI assistant access?

Identify the task, the information it needs and the reason for each requested permission. Use Apple’s guidance for your macOS version, and check how to change or remove access.