Permissions & Security
How Real Bots is governed inside your Salesforce org.
Principles
- Real Bots runs inside your Salesforce org under your sharing and permission model.
- Outbound authentication is asymmetric — private signing keys never leave Salesforce.
- No shared static API secret is used between Salesforce and Real Intelligence.
- Every request is bound to your Salesforce Organization ID and resolved to your Real Intelligence tenant only.
Salesforce controls
| Control | Purpose |
|---|---|
| Permission sets | Grant access to Real Bots objects, Apex services, and admin actions |
| External Credential Principal Access | Grants a user the right to make authenticated callouts |
| Allowed Namespace for Callouts | Restricts Named Credential use to the ribot namespace |
| Certificate and Key Management | Stores the private signing key inside Salesforce |
| Field-level security | Restricts who can view or edit configuration fields such as the signing certificate KID |
Never export or share a Salesforce private key. Real Intelligence only ever needs the public X.509 certificate.
Data handling
Relationship Intelligence reads authorized metadata, not message bodies. See Relationship Intelligence → Security & Authentication for the full authentication and isolation model.
Recommended assignment model
- Create a permission set per capability (Meeting Automation, Relationship Intelligence, Bot Integration).
- Grant External Credential Principal Access only in the capability permission set that requires callouts.
- Assign to users through permission set groups rather than profiles.
Was this helpful?
Last updated 1 month ago