Skip to main content
Case Management > Assignment keeps four sections together: Routing rules, Teams, Review policies, and Case creation sources.

​
Routing rules

Rules are evaluated in priority order against the case source, priority and tags. The first matching active rule selects the review policy and, when configured, a review team. A manually selected assignee takes precedence over automatic assignment. Use Test routing to inspect which rule matches and why each reviewer is eligible or unavailable. A preview does not save the draft or reserve capacity. The actual assignment rechecks access, skills, availability and capacity when the case is created. If nobody qualifies, the case stays unassigned for review. Save draft preserves changes without affecting assignment. New rules remain unpublished and inactive until you choose Publish. Publication updates the rule for subsequent assignments and records its version. If another reviewer has changed the rule or its draft, the operation returns a conflict and preserves the newer work.

​
Teams

A review team lists the reviewers available for a rule, their expertise and their maximum active workload. Only active members with case access to the application can be selected. Capacity counts active cases across the organization. An unavailable reviewer is excluded from automatic assignment. The assignment API also accepts an availability start and end for each team member. Both timestamps are optional; when supplied, the end must be later than the start.

​
Policies and creation sources

Review policies define case content, checklist requirements, default deadlines and whether a second reviewer must approve a resolution. Case creation sources show which workflows, screening settings and transaction rules create cases for a selected policy. See Review policies and 4-eyes review for review requirements.