How it works
Sentry inspects content submitted through supported client paths. Defined detector classes cover identifiers, payment data and secret patterns.
Policy and control
The policy engine combines matches with the subject and destination context to resolve warning, blocking or logging actions. Approved exceptions follow their configured scope and effective window.
Deployment and operations
Decision records preserve the outcome and applicable references. Configure destinations, client paths and actions with the deployment team, then validate the agreed workflow.
How to read this
| Review | Product context | Operating decision |
|---|---|---|
| Policy | Customer-defined rules and actions | Assign policy ownership |
| Records | Decisions with policy references | Define review access |
| Deployment | Supported clients and data paths | Validate configuration |