Permissions

Fluent Onboarding - Accessibility Permissions

Fluent uses one core permission and several feature-specific permissions.

Accessibility is the only core permission. Everything else is requested only when the relevant feature is used.

Accessibility

Accessibility is required for:

  • Global shortcuts
  • Selected text capture
  • App context extraction

Open macOS Settings → Privacy & Security → Accessibility, enable Fluent, then restart the app.

If Fluent opens but cannot see selections, cannot react to the shortcut, or app context stays empty, check Accessibility first.

Automation

Automation permission is required when Fluent needs to control or read from other apps through Apple events.

Typical cases:

  • Browser automation
  • Notes workflows
  • Calendar workflows
  • Reminders workflows

macOS requests this permission when a workflow first needs it.

Browsers

For richer browser context and browser automation, browsers also need to allow JavaScript from Apple Events.

Setup:

  • Safari: Settings → Advanced → Show features for web developers
  • Safari: Settings → Developer → Allow JavaScript from Apple Events
  • Chrome-style browsers: View → Developer → Allow JavaScript from Apple Events

If browser context is incomplete, check this before changing other settings.

Calendar And Reminders

Calendar and Reminders permissions are requested only when those integrations are used.

If you never use those integrations, Fluent never needs those permissions.

Location

Location permission is required only for the Location integration or workflows that depend on current location.

For many users, this permission is optional.

Mail

Some Mail workflows require access to the local Mail storage so Fluent can extract thread context efficiently.

If you use those workflows, Fluent asks for that access when needed. If you do not use Mail workflows, you may never see this request.

Troubleshooting

If you never get permission request from Fluent, check if you are using the official Fluent. Cracked versions may often break the configuration or silently be blocked by Gatekeeper.

You can reset all the permissions with the following command:

text
tccutil reset All net.epicbits.FluentStandalone