Skip to main content

On-Send Compliance Policy

Organisation admins can have Judicio check every email your team sends from Outlook — for personal data, privilege wording, unexpected external recipients, and risky attachments — before it leaves. This page covers configuring that policy. For what your team sees at send time, read the Outlook guide; Gmail users run the equivalent check manually with Check before sending.

At a glance
  • Who: organisation admins only
  • Where: app.judicio.aiSettings → Organisation, in the Add-ins section
  • Cost: the on-send check is free — it never consumes credits
  • Safety: the check fails open; a slow or unavailable check never stops your team's mail

Open the policy editor

  1. In the Judicio web app, go to Settings → Organisation (you'll need the admin role).
  2. Scroll to the Add-ins section. The compliance policy card holds every setting below.

Changes take effect for the whole organisation as your team's add-ins pick them up — there's nothing to redeploy.

The settings

Send mode

The master switch for the send-time check:

ModeBehaviour
OffNo send-time check runs
WarnFlagged sends show a prompt listing the issues; the sender can fix or send anyway
BlockA firmer prompt. Note that Outlook add-ins can never hard-stop a send — after seeing the warning, the sender can still proceed. Treat this as "warn, strongly" plus an audit trail

Jurisdictions

Pick which regimes' personal-data rules apply: India, EU, US. Each adds its own detection rules (for example Aadhaar/PAN patterns for India). Leave it empty to apply every jurisdiction's rules.

Allowed external domains

Recipients outside these domains are flagged as external recipients. Leave the list empty to allow any domain. Useful when your organisation routinely works with a fixed set of counterparty domains and wants anything else surfaced.

Privilege keywords and required markings

  • Privilege keywords — phrases that mark a message as privileged (for example "privileged & confidential"). Judicio flags privileged content heading to unexpected recipients.
  • Required markings — wording that must be present on certain messages; their absence is flagged.

Attachment rules

Block-lists by file extension and by content type. Only attachment names and types are checked at send time — attachment contents are not scanned.

AI audit (LLM review)

An optional AI review that catches subtler privilege and personal-data issues than the deterministic rules. With the toggle on, the AI audit runs as an advisory review after the send and is recorded for your organisation — it doesn't add latency to the send itself.

Default matter

The matter your team's add-ins pre-select when filing emails and documents. Leave it unset to let each member choose every time.

Good to know

  • Fail-open by design. If the check can't complete within its time budget, the email sends normally. Your team's mail never gets stuck because of a Judicio outage — the trade-off is that an unscanned send is possible in that moment.
  • Coverage. The automatic check runs in Outlook on desktop and the web. Outlook mobile doesn't support send-time checks, and Gmail's check is manual (the sender runs it from the compose window).
  • Deployment matters. The automatic check only arms when the Outlook add-in is deployed by your Microsoft 365 admin (centralised deployment), not when individuals self-install — and your Exchange admin must enable the on-send mailbox policy. Point your IT team at the Judicio deployment notes if prompts aren't appearing.
  • Platform kill switch. Judicio's operations team can disable the on-send check globally in an incident (for example, a latency problem). Because the check fails open, this never blocks mail — it only pauses scanning.