ClairaClaira Help Desk
Administration

Opt-in controls for sensitive cases

Voir en français

How Claira's opt-in design at the case and user-group level lets administrators keep restricted matters out of AI processing entirely.

Opt-in controls for sensitive cases

Claira is opt-in only at both the case level and the user-group level. Portal administrators and case administrators control whether Claira is enabled in a case and which user groups can use it. Data is only sent to Claira when a reviewer takes a manual action to scan a document in a case where Claira has been enabled. For any case where your organization's privacy or security policies would prevent data from being sent to the cloud or processed with AI, the answer is straightforward: do not enable Claira on that case, and no data flows to the cloud.

By applying this practice, your team enforces a security control where Claira cannot access data it is not supposed to.

Why opt-in matters

Some clients hold data that should never be sent to AI or to the cloud:

  • Government clients may handle protected or classified material that must stay on on-premises servers.
  • Large institutional clients may hold customer data, regulated records, or other information that internal policy forbids from AI processing.

Most organizations maintain a hierarchy of confidentiality levels, where some matters are more sensitive than others. If your organization already has a policy that restricts how its most confidential cases can be handled, the corresponding control in Claira is simple: do not run Claira on those cases. The basic principle is — as long as your team does not turn Claira on for a case, you do not need to worry about data from that case being processed by AI.

Who controls activation

Two roles together decide whether Claira can run on a case:

Portal administrators

A portal administrator installs Claira as a UI Extension at the portal level and activates it on each case where it should be available. Until the portal admin activates the case, Claira does not appear in Case Setup and cannot be enabled by a case admin. See Setting up Claira for the portal-level install steps.

Case administrators

Once a case has been activated at the portal level, a case administrator decides whether Claira is enabled on that case and which user groups have access. If no user group has Claira enabled, no reviewer on that case can run a scan. See Installing in a case and Users and permissions for how case admins gate access by group.

How leaving Claira off enforces the policy

When Claira is not enabled on a case, there is no path for data from that case to reach AI processing:

  • The Claira pane does not appear in workspace layouts on that case.
  • Single scans and bulk scans cannot be initiated from that case.
  • No document text, source file, or case metadata is transmitted to Claira's services from that case.

Because data is only sent in response to a manual scan action by an authorized user inside an enabled case, leaving Claira off is a hard control. It is not a setting a reviewer can override, and it is not something the system performs in the background.

If you need to revoke access on a case where Claira is already enabled, a case administrator can disable Claira in Case Setup at any time. Once disabled, the Claira pane stops appearing for reviewers and no new scans can be run on that case.

For organizations that handle a mix of confidentiality levels, we recommend the following:

  1. Classify your cases. Identify the matters where AI processing is not allowed — government-protected data, regulated customer records, or anything covered by client restrictions or internal policy.
  2. Do not enable Claira on those cases. Either leave the case unactivated at the portal level, or leave Claira disabled in Case Setup if the case must remain on the portal-level allowlist for other reasons.
  3. Train your team. Make sure case administrators understand which cases are eligible for Claira and which are not. The decision happens at activation time, not at scan time.
  4. Document the decision. Record which cases are excluded and why, so the policy is auditable.

Need help? Contact us at support@claira.to.

Was this page helpful?