Skip to content

macOS permissions

Permissions are required only for live capture features

Section titled “Permissions are required only for live capture features”

Importing an existing media file, converting audio, and transcribing it do not request microphone or Screen Recording permission. Synthezia requests these permissions for live recording features.

Permission Why Synthezia requests it Result if unavailable
Microphone Capture your microphone for a live recording or voice-input workflow. The microphone capture path cannot start.
Screen Recording Capture macOS system audio for live meeting recording through ScreenCaptureKit. Synthezia can continue as microphone-only recording when that fallback is available.
  1. Open System Settings on macOS.
  2. Open Privacy & Security.
  3. Select Microphone or Screen Recording.
  4. Allow Synthezia for the capability you intend to use.
  5. Quit and reopen Synthezia after changing Screen Recording access.

Synthezia can open the corresponding System Settings panes and asks macOS for access when the capability is first needed. The operating system, not Synthezia, makes the final authorization decision.

Synthezia includes a macOS-only command that resets its Microphone and Screen Recording privacy entries so macOS re-evaluates them on the next use. This does not delete recordings, sessions, models, or exports. It is useful when an ad-hoc development build has changed code signature and macOS has retained a stale denial result.

  • If Microphone is denied or restricted, enable it in System Settings and reopen the application before recording again.
  • If Screen Recording is not granted, Synthezia warns that it will record microphone-only audio instead of other participants’ system audio.
  • A Screen Recording preflight check can appear denied in ad-hoc-signed builds even when the recorded path can probe access at start time; verify with the actual recording workflow.