When a computer function works in another app, user account or port, keep the repair inside the failing context. For macOS app privacy permissions, first inspect Privacy & Security and test the app immediately after granting one permission.
What this covers
- macOS app privacy permissions with this exact failure state
- Diagnosis across system permission versus app selection, managed policy and relaunch requirement
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleName the failing app, user account, port or peripheral and one that still works. Expected behavior: grant the selected app only the camera, microphone, files, accessibility or screen access it needs.
Isolate the component boundary
ReversibleInspect Privacy & Security and test the app immediately after granting one permission. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. Boundary to separate: system permission versus app selection, managed policy and relaunch requirement.
Correct only the proven cause
ReversibleGrant the narrow permission and relaunch/update the app. Repair the isolated app, user profile, driver binding or physical path.
Verify and stop safely
ReversibleRetest both contexts after sign-in and one cold restart. Do not grant Full Disk Access or Accessibility to an untrusted app.
Evidence ledger
Sources behind this answer
Exact questions