Auto Clicker Greyed Out in macOS Accessibility? Permission Fix for Sequoia, Sonoma, Ventura
I install the auto clicker, drag it to /Applications, hit Cmd+Comma to grant permissions. System Settings opens to Privacy and Security, Accessibility. The app is right there in the list. The checkbox is right there. It’s greyed out. I click it 30 times. Nothing happens.
I’ve hit this on three Macs in the last year, an M2 Air on Sequoia 15.3, my M1 Pro on Sonoma, and a 2019 Intel mini on Ventura. The fix was different on all three. The symptom looks identical but the cause varies with macOS version, account type, and whether the Mac is managed.
This is the diagnostic tree I wish I’d had on day one. Seven fixes ranked by likelihood, plus a myth-bust on the SIP advice that keeps showing up on Stack Exchange.
TL;DR: Click the lock icon at the bottom of the pane (Sonoma and earlier) or authenticate when Sequoia prompts. If still greyed, drag the app fresh from /Applications into the list. If still greyed, click the minus to remove the existing entry, quit System Settings completely, reopen, and drag the app back in. If still greyed, run tccutil reset Accessibility com.autoclicker-mac.app in Terminal.
If you’re on a work or school Mac, the toggle won’t flip no matter what you do. That’s an MDM configuration profile blocking it, and only IT can whitelist the app. Don’t disable SIP, that’s not the cause.
Why Does macOS Grey Out the Accessibility Checkbox?
The greyed-out toggle isn’t a single bug, it’s a symptom with five upstream causes. Knowing which one you’re hitting saves you the “try every fix” tour.
Under the hood, every Privacy and Security toggle is a row in a SQLite database called TCC (Transparency, Consent, Control) at ~/Library/Application Support/com.apple.TCC/TCC.db. The toggle’s state, the granted timestamp, the bundle ID, and a hash of the app’s code signature all live in that file. When the toggle is greyed, one of these is wrong:
1. TCC database state mismatch
The row exists but the consent record is in a weird intermediate state, usually because of a partial grant attempt that crashed mid-flow.
2. Code signing changed
The app was updated and its code signature hash no longer matches what TCC has cached. macOS refuses to flip the toggle until the entry’s revalidated.
3. The pane itself is locked
Sonoma and earlier hide a padlock at the bottom that has to be clicked first. Sequoia removed the lock visual but still requires authentication on first toggle attempt.
4. MDM configuration profile
Work and school Macs run a Privacy Preferences Policy Control profile that allowlists which apps can request Accessibility. Anything outside the list is locked.
5. Screen Time / parental controls
Family-shared Macs with content restrictions can block third-party Accessibility apps without warning. Looks identical to MDM lock from the user side.
SIP isn’t on this list. It gets suggested on Stack Exchange and it’s wrong, more on that in fix 7. If you’re new to Mac permissions, our walkthrough on how to grant Accessibility permission to an auto clicker on Mac covers the happy-path flow.
Fix 1: Click the Lock Icon to Unlock the Panel
The most common cause is that the pane itself isn’t unlocked. Sonoma and Ventura show a padlock at the bottom-left of the list. If it’s locked, every toggle is greyed by design. Sequoia hides the padlock but the underlying authentication still gates everything.
- Open System Settings, Privacy and Security, Accessibility.
- On Sonoma 14 or Ventura 13: Click the small padlock at the bottom-left (“Click the lock to make changes”).
- On Sequoia 15: No padlock. Click the toggle next to your auto clicker, macOS pops a sheet asking for Touch ID or your admin password.
- Standard accounts can’t grant Accessibility, you’ll need an admin to authenticate at the prompt.
- Once authenticated, the toggle flips to blue.
Sequoia note: Subsequent toggles in the same session usually don’t re-prompt for about 5 minutes. After that you’ll authenticate again. I’ve watched friends miss this for 15 minutes because Sequoia hides the lock state, no padlock, no banner, just a greyed toggle until you click it.
Fix 2: Drag the App Fresh into the List
If the panel is unlocked and the toggle is still greyed, the existing entry is probably stale. The fix is to drag a fresh copy of the app icon into the Accessibility list, which forces macOS to create a new authoritative entry that supersedes the broken one.
- Open Finder, /Applications (Cmd+Shift+A).
- Find the auto clicker icon. Don’t open it.
- Open System Settings, Privacy and Security, Accessibility. Position both windows side by side.
- Drag the auto clicker icon from Finder into the Accessibility list. The cursor shows a green plus when you hover over the right area.
- Drop. macOS adds a new entry with toggle on by default. If a duplicate exists, click minus on the old one.
- Authenticate if prompted. Done.
Why this works: Drag-and-drop into TCC creates a fresh database row keyed against the current signature of the app on disk. Stale signature hashes or partial consent states get bypassed. Cleanest non-destructive fix and the one I try second every time.
Fix 3: Remove and Re-Add the Entry
Sometimes drag-and-drop adds a duplicate instead of replacing the broken entry. The explicit remove-and-re-add cycle handles that:
- Click the greyed-out entry to highlight it.
- Click the minus (−) button below the list. The entry disappears.
- Press Cmd+Q to fully quit System Settings (not just close the window). This flushes the in-memory TCC cache.
- Wait 5 seconds. Reopen System Settings, Privacy and Security, Accessibility.
- Drag the clicker from /Applications into the list. The new entry has a working toggle.
- Toggle on, authenticate if prompted.
The “fully quit Settings” step matters more than it sounds. Skip it and the in-memory TCC cache rewrites the broken state on re-add. I’ve debugged this where re-dragging three times changed nothing, until we Cmd+Q’d and reopened.
Fix 4: Reset TCC for the App (Last Resort Before Reinstall)
If GUI fixes all fail, drop to Terminal and reset the TCC entry directly. The command is tccutil, Apple’s official TCC tool since Mavericks.
- Open Terminal (Spotlight, type Terminal, Enter).
- Run:
tccutil reset Accessibility com.autoclicker-mac.app - You’ll see
Successfully reset Accessibility approval status for com.autoclicker-mac.app. No output means the bundle ID didn’t match TCC; run the clicker once first to register it. - Quit and relaunch the clicker from /Applications.
- Click Start. macOS pops the “would like to control this computer” dialog. Click Open System Settings, authenticate if prompted.
Critical: Always include the bundle ID. Running tccutil reset Accessibility without an argument resets every app’s Accessibility consent on your Mac. That means BetterTouchTool, Karabiner-Elements, Loop, Apple Mail’s automation features, every screen reader extension, all of it. You’ll spend an hour re-granting permission across your whole setup. The targeted form (with bundle ID) is safe and what I run.
To find a bundle ID for any app, run codesign -dv /Applications/Auto\ Clicker.app 2>&1 | grep Identifier. Our app’s bundle ID is com.autoclicker-mac.app.
Fix 5: Apple Silicon Code Signature Mismatch (Reinstall)
Specific to M-series Macs (M1, M2, M3, M4), this shows up after the clicker self-updates or after a macOS update. The signature changes, TCC’s cached signature doesn’t update, the toggle locks. tccutil sometimes clears it; sometimes you reinstall.
Heads up: If you just updated to Sequoia 15.4 from Sonoma, or just installed a clicker update on M-series, this is your most likely cause. Intel hits this 1 in 20 cases; Apple Silicon hits it 1 in 5 after major updates because ARM64 codesigning is stricter about signature integrity.
- Quit the clicker. Cmd+Tab to confirm it’s not running.
- Drag from /Applications to Trash, Empty Trash.
- Run
tccutil reset Accessibility com.autoclicker-mac.appto clear the stale entry. - Grab the latest DMG fresh from the free Mac auto clicker download page.
- Open DMG, drag into /Applications, eject.
- Launch, click Start, accept the Accessibility prompt. Toggle flips first try.
Our deeper guide on how to reinstall after a macOS update covers the full clean-install flow if a basic reinstall doesn’t clear it.
Fix 6: MDM or Parental Controls Profile Is Blocking It
On work, school, or family-managed Macs, no amount of tccutil resetting will fix it. A configuration profile is blocking the app and re-enforces itself any time you try to override.
- Open System Settings, scroll the sidebar all the way down to Profiles (only appears if a profile is installed).
- Look for a payload titled with your company or school name, or “Privacy Preferences Policy Control.”
- Expand the profile. A Privacy or PPPC section listing Accessibility services is your block.
- If removable, click minus. Warning: on managed devices this un-enrolls you. On a personal Mac with a stray profile, it’s safe.
- If “Cannot be removed by user,” contact IT and ask them to whitelist
com.autoclicker-mac.appin the PPPC payload.
Reality check: Most corporate IT departments will say no to whitelisting an auto clicker because the same APIs can script around productivity monitoring. The practical answer on managed Macs is “use the clicker on a personal Mac.”
For Family Sharing Macs, the equivalent is Screen Time. Settings, Family, the kid’s account, Content and Privacy, Allowed Apps. Toggle the clicker on there or relax the restriction.
Fix 7: SIP Is Not the Cause (Myth-Bust)
Search “auto clicker greyed accessibility mac” on Stack Exchange or a few of the older forum threads, and you’ll find people suggesting you boot into Recovery and run csrutil disable to turn off System Integrity Protection. Don’t.
SIP and TCC are separate subsystems. SIP protects /System and /usr from modification. TCC governs Accessibility, Input Monitoring, Screen Recording, Camera, and Microphone consent. Disabling SIP does nothing to TCC. The toggle stays greyed and your Mac is less secure.
The myth comes from pre-Mojave where Accessibility was lumped under Privacy and did interact with some SIP rules. Apple split TCC out in 10.14. If you’ve already disabled SIP, boot into Recovery, run csrutil enable, reboot.
Diagnosis: Which Fix Matches Your Symptom?
Use this table to skip to the right fix instead of running the full ladder. Built from the cases I see most in our support email.
| Symptom | Most Likely Cause | Best Fix |
|---|---|---|
| Toggle is greyed, no padlock visible (Sequoia) | Authentication needed on click | Fix 1: Just click the toggle, authenticate |
| Padlock at bottom is closed (Sonoma/Ventura) | Pane is locked | Fix 1: Click padlock, authenticate |
| Pane unlocked, toggle still greyed, app updated recently | Stale code signature in TCC | Fix 2: Drag fresh from /Applications |
| Drag-and-drop doesn’t replace the broken entry | TCC cache holding stale row | Fix 3: Remove, quit Settings, re-add |
| Multiple GUI fixes failed, no MDM profile | TCC database desync | Fix 4: tccutil reset (targeted) |
| Apple Silicon Mac, toggle greyed after macOS update | Signature cache mismatch | Fix 5: Reinstall the app fresh |
| Work or school Mac, toggle won’t move at all | MDM PPPC profile | Fix 6: Contact IT for whitelist |
| Family Mac, kid’s account, toggle greyed | Screen Time content restriction | Fix 6: Allow app in Content and Privacy |
| Toggle on but clicker still doesn’t click | TCC desync between UI and DB | Toggle off, quit Settings, toggle on again, or Fix 4 |
Roughly 60% of cases are Fix 1, 25% are Fixes 2 and 3 combined, and the remaining 15% split between tccutil reset, Apple Silicon signature issues, and MDM blocks. Start at Fix 1 and work down.
What If the Auto Clicker Isn’t Even in the List?
Same root, different surface: the list is empty or the clicker isn’t on it. The fix is making the app actually request the permission so macOS adds it.
- Open the clicker from /Applications.
- Click Start. Don’t change any settings, just hit Start.
- The first event-tap attempt triggers a dialog: “Auto Clicker would like to control this computer using accessibility features.”
- Click Open System Settings. The Accessibility pane opens with a new entry, toggle ready.
- Authenticate (Touch ID or password). Toggle flips on, clicks fire on next Start press.
If clicking Start doesn’t trigger the dialog, the app may be silently failing. Our guide on what to do when the auto clicker won’t open on Sequoia covers Gatekeeper blocks and quarantine flags. If Start works but the global hotkey doesn’t, that’s Input Monitoring rather than Accessibility, and our hotkey not working walkthrough has the targeted fix.
FAQ
Why does my work Mac not let me enable Accessibility?
Managed Macs through MDM (Jamf, Kandji, Mosyle, Intune) run a Privacy Preferences Policy Control profile that locks Accessibility to an allowlist. Check System Settings, Privacy and Security, scroll to Profiles for a PPPC payload. You’ll need IT to whitelist com.autoclicker-mac.app; there’s no end-user override and tccutil won’t bypass it.
Will tccutil reset Accessibility break Apple Mail or other apps?
Running tccutil reset Accessibility with no app argument resets every app’s Accessibility consent, so Mail’s automation, BetterTouchTool, Karabiner, Loop, and any clicker all need re-granting. Always scope it: tccutil reset Accessibility com.autoclicker-mac.app only resets that one bundle. The targeted form is safe and what I use 99% of the time.
What’s different about Sequoia versus Sonoma here?
Sequoia removed the visible padlock at the bottom of the pane. Authentication now triggers the moment you click a toggle, not unlocked up-front. Sonoma and Ventura still show the padlock visual. Sequoia also added a weekly re-prompt for Screen Recording, but Accessibility is still grant-once. The fix steps are identical, just authenticate when Sequoia asks instead of unlocking first.
Does this affect Input Monitoring permission too?
Yes, the same TCC database governs Accessibility, Input Monitoring, Screen Recording, Camera, and Microphone. If your hotkeys also stop working, run tccutil reset ListenEvent com.autoclicker-mac.app for Input Monitoring specifically. Same greyed-out symptom, same fix, different pane in System Settings. Don’t reset both at once or you’ll have to re-grant twice.
Apple Silicon vs Intel, does the fix differ?
The fixes work identically, but Apple Silicon Macs cache stale code signatures more aggressively after updates than Intel. On M1 through M4, reinstall first if drag-in fails. On Intel, jump straight to tccutil reset because the signature cache problem is rare.
Can I script the TCC reset for multiple apps?
Yes: for id in com.autoclicker-mac.app com.example.other; do tccutil reset Accessibility $id; done. I keep this in a shell function for fresh setups. Don’t pipe every TCC service or you’ll wipe consent for apps you forgot. Scope by service and bundle ID.
The toggle is on but the clicker still doesn’t work, what now?
TCC sometimes shows the toggle as on while the underlying row is corrupt. Toggle off, quit System Settings (Cmd+Q), reopen, toggle back on. If that fails, run tccutil reset Accessibility com.autoclicker-mac.app and re-grant. About 5% of cases I’ve debugged are TCC desync; the reset clears it.
Why is the auto clicker not even showing in the Accessibility list?
macOS only adds an app after it actually requests Accessibility access. Launch the clicker and click Start once. The event tap request triggers a permission dialog. Accept it and the entry shows up. Without that initial request, the list stays blank.
Will disabling SIP fix this?
No. SIP and TCC are separate systems. Disabling SIP weakens security and changes nothing about the greyed Accessibility toggle. Advice telling you to run csrutil disable for this is pre-Mojave-era and no longer applies.
Does parental controls block Accessibility on a kid’s account?
Screen Time can block third-party Accessibility apps if Allowed Apps is filtered. Check Settings, Family, your child’s account, Content and Privacy, Allowed Apps. Toggle the clicker on or relax the restriction. Family-shared Macs hit this often after a default-restrictive Setup Wizard.
After macOS update the toggle is greyed again, why?
Major updates (Ventura to Sonoma, Sonoma to Sequoia) sometimes invalidate cached TCC entries because the app needs re-validation against the new system. Reinstalling the auto clicker after a macOS update is the cleanest fix. Our reinstall after a macOS update guide walks through the full re-permission cycle that follows.
How do I know if it’s TCC corruption versus an MDM block?
Run tccutil reset Accessibility com.autoclicker-mac.app. If TCC’s the cause, the app reappears with a clean toggle. If MDM is the cause, the toggle stays greyed because the profile re-locks it instantly. Check Settings, Privacy and Security, Profiles for any payloads.
Related Guides
For broader options if our app isn’t right for you, our roundup of the best Mac auto clickers covers the alternatives I’ve tested through Sequoia.