Skip to content
Sanitized AI Help Center

Exceptions

Sometimes a guardrail is right for the organization and wrong for one team. The legal team reviews contracts full of client names. The billing team works with account numbers all day. Weakening the guardrail for everyone is the wrong fix.

An exception exempts exactly who you choose, from which guardrails, on which AI tools, and for how long, with a reason attached. Admins manage exceptions on the Exceptions page.

What an exception does

While an exception applies, the covered guardrails switch to silent monitoring for that person: their prompts are sent without a warning, and the event is still recorded.

That last part matters. An exception relaxes enforcement without creating a blind spot. Your Events page and reports still show what was caught, so if an auditor asks what happened to some data, you still have the answer.

Create an exception

  1. On the Exceptions page, click New Exception.
  2. In Applies to, choose A specific user or A department, and then choose the person or department. A department exception covers everyone whose profile has that department, whatever the capitalization.
  3. In Guardrails, keep All guardrails or choose specific ones.
  4. In AI tools, keep All AI tools or choose specific ones. This is useful when a team needs an exemption on your approved enterprise tool but not everywhere.
  5. In Expiry, choose a date, or select Permanent (no expiry). The date starts 30 days out, because an exception that expires forces a deliberate renewal instead of living on quietly.
  6. In Reason, explain why. A reason is required, and it’s what makes the exception defensible six months later.
  7. Click Create Exception.

Each exception shows who created it and when.

Keep exceptions under control

The top of the Exceptions page counts Active exceptions, exceptions Expiring within 7 days, and Expired ones. Exceptions that expire soon are marked in the table, so they don’t lapse without you noticing.

Expired exceptions stop applying on their own, and full enforcement resumes. There’s nothing to clean up. They stay in the list for the record.

To end an exception early, click Revoke in its row. Full enforcement resumes immediately.

Exceptions also appear on each person’s activity page, under Exceptions for this person. A record that looks unusually clean is often explained there.

Exception or guardrail change?

  • Create an exception when the guardrail is right, but a specific group has a legitimate need.
  • Change the guardrail when it fires on data that isn’t sensitive. In that case the guardrail is wrong for everyone, and an exception would only hide the problem for one team.

The Overrides card on the Events page helps you tell the difference. If everyone overrides a guardrail, it needs fixing, not exempting.