The Deconfliction module is under development. Follow this article to receive an email when step-by-step instructions are released!
OWL separates automated match detection from notification and disclosure controls. This ensures investigative awareness while preserving agency security, role-based permissions, and administrative restrictions.
There are three core layers:
- Auto-Deconfliction — Detection engine. Identifies potential overlaps across records.
- Deconfliction — Notification and coordination controls. Determines whether and how users are notified.
- Security & Collaboration Rights — Visibility and disclosure governance. Determines what record details, if any, are visible and who must be contacted for coordination.
These layers work together but function independently, enabling investigative awareness while protecting operational security and confidentiality.
Auto-Deconfliction: Automated Match Detection
Auto-Deconfliction continuously evaluates configured attributes across records, including Cases, Subjects, Evidence, and other record types.
It:
• Runs in the background
• Detects overlapping attributes
• Logs potential matches
• Operates regardless of user notification settings
Auto-Deconfliction does not automatically expose record details, trigger disclosures, or merge/edit any records. It performs detection only.
Deconfliction: Notification & Coordination Controls
Deconfliction governs how detected matches are surfaced and managed.
Depending on organizational settings, Deconfliction may:
• Notify record owners of a match
• Require coordination before proceeding
• Escalate matches to supervisors
• Mask identity details
• Allow identity disclosure
• Suppress notifications entirely
Detection and notification are separate processes. A match may exist even if no notification is issued.
Record Blocking & Administrative Controls
Administrators may apply additional security restrictions to specific records.
Blocked or restricted records may:
• Suppress match notifications
• Prevent identity disclosure
• Restrict collaboration visibility
• Override standard Deconfliction display rules
Auto-Deconfliction may still evaluate attributes internally, but disclosure is governed by administrative security policy.
Visibility Levels When a Match Is Found
When a match is detected, visibility is determined by collaboration rights and record-level permissions.
Depending on policy and user role, one of the following outcomes will occur:
Full Disclosure - User can view the complete record details.
Limited Disclosure - User can see basic metadata such as:
• Record type
• Owning agency or team
• Case or record identifier
• Matched attributes
Sensitive fields remain hidden.
Masked Awareness with Contact Routing - User is informed that an overlapping investigation exists, but record details are not shown.
- The notification will include coordination guidance such as “For additional information, contact: [Agency / Department / Supervisor / Designated Role].”
- This allows operational coordination without revealing restricted investigative information.
Important Clarification
A match notification indicates investigative overlap. It does not grant access to another record.
Access to record details is always governed by:
• Role-based access control
• Record-level permissions
• Collaboration policies
• Administrative restrictions
Detection ensures awareness. Disclosure is controlled.