Overview
When a review task is created, it’s sent to configured channels where reviewers can make decisions.Decision Types
Approve
Request meets requirements and can proceed
Decline
Request should not proceed
Request Changes
Request needs modifications
Making Decisions by Channel
| Channel | How to Decide |
|---|---|
| Web Dashboard | Click Approve, Decline, or Request Changes buttons |
| Slack | Click interactive buttons or use reactions |
Reply with APPROVE, DECLINE, or CHANGES followed by reason | |
| Microsoft Teams | Click buttons in the adaptive card |
| SMS | Reply with A, D, or C |
Information Available
Reviewers see:| Info | Description |
|---|---|
| Trace Details | Function name, arguments, metadata |
| Session Context | Other traces in the same session |
| Assessments | Policy results with risk levels and reasons |
| Workflow Info | Why this task was created |
| Previous Decisions | If multi-approver, what others decided |
Decision Factors
Consider when reviewing:- Policy Compliance - Does the trace meet requirements?
- Risk Level - Is the risk acceptable?
- Context - What is the session showing?
- Business Need - Is there valid justification?
Multi-Approver Workflows
When multiple approvals are needed:| Scenario | Result |
|---|---|
| All approve | Task approved |
| One declines | Task rejected |
| Mixed (some approve, some request changes) | Depends on workflow configuration |
Decision Recording
Every decision captures:| Field | Description |
|---|---|
| Type | Approve, Decline, or Change Requested |
| Reviewer | Who made the decision |
| Channel | Where it was made |
| Reason | Optional explanation |
| Requested Changes | If changes requested, what’s needed |
| Timestamp | When decided |
After Decision
| Decision | What Happens |
|---|---|
| Approved | Workflow continues. Trace marked Completed. Calling system notified. |
| Declined | Workflow continues through Declined path. Trace typically Rejected. |
| Changes Requested | Workflow continues through Change path. Feedback returned to caller. |