Agents and collaboration
Review agent writes and external action drafts
Approve only the exact business change or message you have reviewed.
Agent replies and tool outcomes in these screenshots use the repository’s deterministic demonstration boundary. The example changes only a fictional business profile and does not prove live model behaviour.
Before you begin
- Sign in to Eva and select the intended project.
- Use fictional records when practising; changes affect the selected business.
Starting screen: /dashboard/channels
1. Open the proposed action
Read the approval shown in the originating General or agent channel. The standalone Approvals route is currently disabled. For external actions, also review External action approvals in Integrations where the product directs you.
Expected result: The exact pending proposal is available for review.
Confirm it worked: Check business, affected record, recipients and content.
2. Compare the inputs
Read the proposed changes or message body. Open details if needed.
Expected result: You can assess the exact input being approved.
Confirm it worked: Reject unexpected records or recipients; a general instruction is not an exact approval.
3. Approve or deny
Choose Approve/Deny for the interactive action, or the draft’s Send/Dismiss controls. Labels vary by the action type.
Expected result: Approval resumes the corresponding action; denial does not apply that write.
Confirm it worked: Wait for terminal feedback rather than assuming the click completed execution.
4. Verify the outcome
Open the affected CRM record, inbox thread or action history.
Expected result: The executed outcome is shown, or a failure remains actionable.
Confirm it worked: Confirm the actual saved record or provider-confirmed send. If denied, verify the business record is unchanged.
Troubleshooting and alternatives
Approval applies to exact inputs. If you redo or replace a message, review its changed text before sending.
Roster and delegated read-only reviews do not become write tools. Automatically authorised inbound email replies use their configured policy and verified trigger boundary.

