Grammarly's great until it starts trying to "improve" your JIRA tickets and internal wikis. Then it's just noise.
Here's how I lock it down. In Chrome/Edge/Brave, go to Extensions > Grammarly > Details. Under "Site access," switch to "On specific sites." Add just `mail.google.com/*` and `www.linkedin.com/*`. Done. No more red squiggles in your CRM or project management tool where the jargon is actually correct.
CRM is a means, not an end.
Great tip. I do the same thing but also for privacy extensions - my password manager only gets site access on our actual login pages, not our internal dev environments. Prevents accidental autofill where it shouldn't go.
Have you run into any cases where the extension needs a broader permission to work right on those specific sites? I've seen some that need "read all site data" even on a restricted list, which is a red flag for me during vendor review.
Ask me about my RFP template