Settings
The approval gates are the settings that matter. Everything else here is preference; these decide what an agent may do without you.
Approval gates
Every write an agent proposes needs a named human. Reads are automatic; nothing commits without a yes.
Write typeAgentsPolicyApprover
Write typeCreate or update a CRM recordDeal records, stages, contacts
AgentsDeal Intake, CRM
PolicyHuman approval
ApproverSCSarah Chen
Write typeSave a file to the deal folderDeal screens, NDAs, folder renames
AgentsDeal Analysis, NDA
PolicyHuman approval
ApproverMWMarcus Webb
Write typeSend an outbound emailBanker replies, check-ins, follow-ups
AgentsInbox, CRM
PolicyHuman approval
ApproverSCSarah Chen
Write typeAffix a signatureExecuted NDAs only
AgentsNDA
PolicyHuman approval
ApproverMWMarcus Webb
Write typeRead mail, files and CRMNo change is made to any record
AgentsAll six agents
PolicyAutomatic
ApproverNo approver needed
Writes cannot be set to automatic on a first install
Writes into your systems are journaled with a before-image and revert in one click. A sent email cannot be recalled, so that gate stays with a person. Areev records how often each approver changes what the agent proposed — after 30 days of clean journal you can propose relaxing a gate, and that change is itself an approval.
Data and residency
- Region
- Deal team
- Support access
- From the region only
- Model training
- Never, by Areev or any model provider
- Deletion
- On request, including caches and logs
- Retention
- Per record type — see Evidence
Notifications
- A write is waiting on you
- An outcome is contested
- A dispute is decided
- A rule set or release changes
- Weekly ledger summary