Overview#
A complex financial crime investigation may involve dozens of concurrent objectives: interviewing witnesses, tracing asset flows, securing digital evidence, and coordinating with foreign partners. The Mission domain gives teams the structure to manage those objectives. Each mission is a discrete, assignable task inside an investigation, with its own status, priority, event links, and ownership.
Key Features#
- Mission creation and management with assignment tracking
- Status lifecycle management: active, pending, completed, cancelled, on hold, and blocked
- Priority levels from low to critical with appropriate response times
- Event linking to associate relevant activities with missions
- Investigation-scoped mission organisation
- Reassignment and delegation capabilities
Use Cases#
Relevant sectors include law enforcement, intelligence agencies, and defence.
- Assigning and tracking discrete investigative objectives within a case
- Managing field operation tasks with status and priority tracking
- Linking events and evidence activities to mission objectives
- Coordinating team member assignments across investigation workflows
Integration#
The Mission domain integrates with Investigation for case context, Event for linked activities, User for assignment targets, Notification for status updates, and Timeline for activity tracking.
Open Standards#
- GraphQL (June 2018 specification): all Mission create, read, update, and delete operations are exposed exclusively through a typed GraphQL API using queries and mutations, enabling strongly typed, self-documenting access for clients.
- JSON Web Token (RFC 7519) / Bearer Token (RFC 6750): every API call is authenticated by validating an RS256-signed JWT against the platform JWKS endpoint; the bearer scheme defined in RFC 6750 is used to convey the token on each request.
- UUID Version 4 (RFC 4122): mission, investigation, and event-link identifiers are random UUIDs generated at creation time, ensuring globally unique, collision-resistant keys across tenants.
- ISO 8601 / UTC timestamps: all created-at and updated-at fields are stored and returned as UTC-aware datetimes, providing unambiguous temporal ordering across time zones.
- Role-Based Access Control (NIST RBAC, INCITS 359-2012): the service layer enforces tenant-scoped RBAC on every operation, granting superusers unrestricted access while restricting regular users to their permitted tenants.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14