Block sites and exclude people from checking
Admins can control where the InPolicy browser extension runs, and who it checks, from Settings → Browser extension in the InPolicy dashboard. You don’t need Google Admin or Intune for this, and changes apply to everyone in your workspace.
You need the Admin role to see this page. It also has a Deploy to your company section with the Google Admin and Intune steps, and the values to paste ready to copy. The full walkthrough is in Deploy the extension (IT guide).
Block a site
Section titled “Block a site”InPolicy won’t check anything on a blocked site, for anyone in your workspace. Use this for internal tools, sites your policies don’t cover, or editors that misbehave under the extension.
- Go to Settings → Browser extension.
- Under Blocked sites, type the site and click Add:
hr.example.comblocks that site only.*.example.comblocksexample.comand every subdomain, such aswiki.example.com.
- Click Save changes.
If you paste a full address like https://hr.example.com/home, InPolicy keeps just the site (hr.example.com). You can block up to 100 sites.
Blocked sites need an up-to-date extension. Chrome and Edge update extensions on their own, usually within a few hours; until a browser does, its older extension keeps checking on blocked sites. Excluding someone doesn’t have this gap, because InPolicy’s servers also refuse to check their text.
Exclude someone from checking
Section titled “Exclude someone from checking”InPolicy checks nothing for an excluded person, on any site. That includes the policy check while drafting a policy in the dashboard, which finds nothing for them. They keep their InPolicy account and can still use the rest of the dashboard. Use this for people whose messages you don’t want checked, such as legal counsel.
- Go to Settings → Browser extension.
- Under Excluded from checking, search by name or email and tick each person to exclude. Everyone already excluded is listed at the top.
- Click Save changes.
The excluded person’s extension popup shows Off · Not checking, with a note that their organization turned checking off. InPolicy’s servers also refuse to check their text, so an older version of the extension can’t keep checking them.
To include someone again, untick them and save.
When changes take effect
Section titled “When changes take effect”Extensions pick up the new settings on their own, so nobody needs to reinstall anything:
- Someone using InPolicy gets them within seconds, the next time InPolicy checks their text.
- An extension that hasn’t checked anything recently gets them within 20 minutes.
- Including someone again can take up to 20 minutes, because their extension isn’t checking anything until it refreshes.
If a page was already open, InPolicy stops checking it once the change arrives.
Compared with Google Admin and Intune
Section titled “Compared with Google Admin and Intune”If you deploy the extension through Google Admin or Intune, those consoles can also keep it off sites (“Runtime blocked hosts”) and keep it from certain people (by leaving them out of the deployment). See Deploy the extension (IT guide).
The two work together. Use the console when IT manages the rollout and the browser should enforce the rule. Use this page when you want the setting in InPolicy, where admins can see and change it, and every change is recorded in Activity Logs.
Related
Section titled “Related”- Pause the extension or exclude a site: what employees see
- Users and roles
Cookie PreferencesDo Not Sell or Share My Personal Information