Case workflow
The case status tells operators what must happen next. Status changes require a reason and are retained in the case timeline.
| Status | Meaning |
|---|---|
DRAFT | Initial record that has not entered the operational queue |
OPEN | Investigation is available for assignment and review |
IN_REVIEW | An analyst is actively investigating the case |
PENDING_INFORMATION | Work is waiting for evidence or information outside the current review |
ESCALATED | The case requires senior, MLRO, fraud, legal, or another approved review |
RESOLVED | The investigation has a disposition and resolution narrative |
CLOSED | Final operational closure after resolution |
OneView permits only explicit transitions. For example, a draft can move to open, but it cannot move directly to closed. A closed case can be reopened only into open status, which creates a new timeline event while preserving the prior resolution history.
Resolving and closing
A resolution requires:
- Every required task to be completed or cancelled under an approved exception.
- An active disposition selected from the controlled disposition catalogue.
- A resolution narrative that explains the finding and decision.
- A reason for the status transition.
Closing a case also requires the retained disposition and narrative. OneView does not delete or rewrite the original investigation when a case is reopened.
Assignment and teams
Every case is owned by exactly one team and one individual assignee — there is no unassigned, team-only, or
user-only ownership state. Teams are installation-wide organizational groups of local users, managed under
Settings → Teams (teams:read/teams:manage), separate from Case Management settings, roles, and licensing.
Team membership never grants permissions by itself: joining a team does not grant cases:read, cases:manage,
cases:evidence:read, or any source-module permission, and a restricted case still requires
cases:restricted:read even when it is assigned to the user's own team.
For a case that is not RESOLVED or CLOSED, both the owning team and the assignee must be active, and the
assignee must be an active member of that team. Reassigning a case to a different team requires choosing an eligible
assignee for the destination team in the same change; the current assignee can only be kept when they are already an
active member of the destination team. cases:assign is required to change either.
Every assignment change stores the previous and new team, previous and new assignee, the assigning user, a required reason, and a timestamp. Assignment history is append-only. Resolved and closed cases keep their last owning team and assignee as a historical record even if that team or user later becomes inactive.