Sentinel ID overview
National identity & operations
Sentinel ID integrations
Connections belong to this product’s deployment. Each source, device and external service needs the appropriate permission and commissioning.
Architecture and information flow
| Component | Purpose |
|---|---|
| Agency browser and field app | Authorised desktop and approved Android workflows. |
| Application services | Identity, evidence, cases, alerts and response. |
| Operational records | Configured database and protected evidence storage. |
| Connections | Scoped, authorised camera and partner integrations. |
Integration requirements
| Connection | Setup | Validation / limitation |
|---|---|---|
| Biometric inputs | Supported capture and enrolled records. | Candidates require quality review and independent validation. |
| Camera / plate feeds | Registered sources and configured processing. | Measure recognition and throughput on representative footage. |
| Android field app | Approved devices and appropriate roles. | Field connectivity and device policies apply. |
| Partner data | Scoped authorised APIs and source agreements. | No automatic access to external government or financial databases. |
| Optional assurance | Configured verifiers, signing and external archives. | Provider contracts, credentials and testing are required. |
Commissioning and acceptance
- Protected records reject unauthorised roles.
- Device and agency boundaries remain enforced.
- Matches and false matches receive review.
- Evidence retains source context.
- Field and alert workflows pass representative tests.
- Recovery and audit checks succeed.
A demonstration for your workflow
Discuss Sentinel ID with your team and agree the relevant scope, input sources, deployment, training and support.