Skip to content
InPolicy InPolicy Docs

Pause the extension or exclude a site

The extension can be paused entirely from the popup, or excluded from a specific URL by an administrator. The per-site toggle that lives directly in the popup isn’t shipped yet — pausing is the closest user-facing equivalent.

Why you might want to

Section titled “Why you might want to”
  • Custom editors that break under observation. Some rich-text editors (older CMSes, certain in-house tools) re-render aggressively enough that the extension’s underlines flicker or the editor slows down noticeably.
  • Sites that are irrelevant to policy checking. If your team has no policies that would ever apply to what you’re doing on a given site, there’s no reason to scan there.
  • Sites with strict content security policies. Most CSP-protected sites work fine because the extension bypasses page CSP, but a handful have extra defenses that cause rendering issues.

Pause the extension globally

Section titled “Pause the extension globally”

The popup has a single Extension Active / Paused toggle. Click the InPolicy icon in the toolbar and flip the switch — every site stops being scanned until you flip it back. This is the right answer when an editor is misbehaving and you need a quick out.

The pause state is stored locally in the browser, so it carries across browser restarts on the same Chrome profile.

Exclude a specific URL

Section titled “Exclude a specific URL”

Per-URL exclusion is plumbed at the API level — there’s an endpoint at /api/disabled-urls that accepts a URL and stores it for your account — but the popup UI to call it isn’t shipped yet. To exclude a domain today:

  • End users: ask your admin to add the URL on your behalf.
  • Admins: call the API directly, or contact support and supply the domain.

When the URL appears on your account’s disabled list, the extension’s content script still loads on those pages but stops scanning text and drawing underlines. Sign-in state and other sites are unaffected.

How admins can exclude sites fleet-wide

Section titled “How admins can exclude sites fleet-wide”

Admins can maintain a tenant-wide exclusion list using the same admin API. This is useful for:

  • Internal apps where detection is unnecessary.
  • Payment processors or other sensitive sites where an extension observing the DOM is a compliance concern.
  • Legacy systems that break under the observer.

A dedicated admin UI is on the roadmap. Until it ships, ask support to seed the list for you.

What pausing or excluding does not do

Section titled “What pausing or excluding does not do”
  • It does not uninstall the extension. To uninstall, see Install the extension.
  • It does not sign you out.
  • It does not affect the Mac app, which runs independently of the browser.
Section titled “Related”