Workflow Actions
Workflow actions define what happens when a workflow is triggered.
They control how tasks are created, assigned, and completed for threat models within a collection.
Review Workflow Actions
Review workflows are used to request formal review of threat models.
How Review Workflows Function
When a threat model belongs to a collection with a Review workflow:
- A Submit for Review option becomes available
- Submitting the model creates a review task
- The task is assigned to one user from the workflow’s assignee pool
The workflow defines the rule that allows review tasks to be created.
Update Workflow Actions
Update workflows are used to request updates to threat models, often on a recurring or change-driven basis.
How Update Workflows Function
When a threat model belongs to a collection with an Update workflow:
- The system automatically creates update tasks
- The Update Model option becomes available in the workflow menu
- After completing changes, the user selects Complete Update
- The model is marked as updated
Assigning Workflow Actions to Users and Teams
Workflows support assigning:
- A single user
- Multiple users
- One or more teams
All assigned users and teams are pooled together.
Tasks are assigned using a round-robin approach, favoring users with the fewest active tasks.
Assignment Behavior
- Single user: That user receives all tasks
- Multiple users: Tasks go to the user with the fewest tasks
- Team assignment: Tasks are assigned to individual users within the team based on task load
Workflow Constraints
The current workflow system operates with the following constraints:
- Workflows are tied to a single collection
- One workflow per action type can be attached to a collection
- Each task is assigned to one user
- Users and teams are pooled for task assignment
These constraints ensure predictable task routing and clear ownership.