CRM access pattern
A customer-owned AI agent reads accounts, summarizes opportunities, updates pipeline fields, and drafts follow-up messages.
Agent asks to reach
What can go wrong
- Overwrites customer records with wrong values
- Exposes contact data to the wrong audience
- Sends unauthorized messages from a rep's identity
- Silently changes pipeline ownership
How Anubis controls it
- Write access restricted to declared fields
- Ownership and stage changes require approval
- Outbound email held for review
- Every CRM action recorded against the agent
Where Anubis draws the line
- Read accounts and opportunities, allowed
- Update a contact field, restricted
- Reassign account owner, needs approval