macOS Permissions Explained

Tenali desktop requires specific macOS permissions to deliver real-time assistance during active meetings.

Required Permissions

• Microphone: capture meeting audio context for live transcript + answer generation.
• Screen Recording: detect active call window context and meeting state.
• Accessibility: support stable in-call overlay interactions.

Guided Setup Flow

You don't have to locate each setting yourself. Tenali walks you through the permissions in order:

1. Start with the microphone. After you allow it, Tenali automatically opens System Settings and brings it to the front.
2. Grant the remaining permissions one at a time. Tenali guides you through Screen Recording, then Accessibility, with inline instructions like "Find Tenali in the list and turn it on."
3. The flow advances on its own. As you grant each permission, Tenali moves to the next one automatically and finishes when everything is enabled.

Whenever a permission is needed, click Open Settings — it shows Opening… while it brings the correct System Settings page to the front. Tenali waits up to a few minutes for you to complete each step.

Security Principles

• Permissions are explicit and user-approved at OS level.
• Access should be granted only to trusted signed desktop builds.
• Permission state must be reviewed after OS upgrades or endpoint policy changes.

Enterprise Admin Guidance

1. Document permission expectations in onboarding SOP.
2. Verify endpoint policy tools do not silently block required scopes.
3. Revalidate permissions after macOS major version updates.
4. Include permission troubleshooting in help desk runbooks.

Common Break Conditions

• Permission revoked after device migration
• Endpoint policy conflict from MDM rules
• Input device restrictions at OS level

If permissions are correct and transcript is still empty, move to Desktop App Issues.