S
Integration · CRM
Govern your Salesforce agent.
Let agents read and update records in Salesforce — without handing them the keys to delete pipelines or export your customer list.
The risk
What can go wrong when an agent holds Salesforce.
A raw Salesforce token lets an agent do anything the token can — no boundary, no record. These are the actions you don't want it taking on its own.
- Bulk-deleting or overwriting opportunities and accounts
- Exporting full contact lists / PII
- Changing sharing rules and field-level security
- Mass-emailing leads from a connected agent
The HiveKey policy
Scope it. Guard it. Log it.
Give the agent a role with exactly the Salesforce actions it needs, then guard the rest in the path.
Scope — granted
- crm.account.read
- crm.contact.read
- crm.opportunity.update
Guard — enforced
- Deny crm.delete on any object
- Block exports over 100 rows
- Require approval to email > 25 contacts
The proof
Every Salesforce action — allowed or denied — on one trail.
salesforce-agent · action log live
crm_update opportunity#4821 stage scope: opportunity.update allow
crm_delete account#118 guard: no destructive deny
Put your Salesforce agent under one policy.
See HiveKey scope, guard, and log your Salesforce agent and the rest of your fleet.