Secure AI for Salesforce

Security is the most consistent concern organizations raise when evaluating AI for Salesforce. CRM data is not generic information — it includes customer relationships, deal terms, internal communications, and financial data that organizations have clear obligations to protect. This article covers what a secure AI implementation looks like in practice and how AI Engine approaches data governance.

The Real Risk: Uncontrolled External AI Use

The security conversation around AI and Salesforce often focuses on the wrong risk. Organizations worry about whether a Salesforce-native AI tool is safe, while overlooking the more immediate problem: without a governed option, users will use ungoverned alternatives.

When there is no sanctioned way to use AI with Salesforce data, sales reps and service agents find their own. They copy account details, deal terms, and customer emails into external AI chatbots. This creates exactly the risk organizations are trying to avoid — CRM data being shared externally with no visibility, no auditability, and no control over how it is retained.

A Salesforce-native AI integration with clear admin controls is a security improvement over the status quo, not a security risk.

Admin-Controlled Object and Field Access

The foundation of a secure Salesforce AI integration is admin control over what data the AI can access. AI Engine implements this through its configuration panel, where admins select:

• Which Salesforce objects are available for AI actions (Leads, Accounts, Opportunities, Cases, custom objects)
• Which fields within those objects can be included in AI prompts
• Which fields are explicitly excluded regardless of user request

This means fields containing sensitive financial terms, personal data governed by privacy regulations, or internal notes that should not leave the organization can be excluded from AI processing entirely. The field-level exclusion happens at the configuration layer, not the user layer — users cannot override it.

Prompt Templates and Consistent Governance

Allowing users to write free-form AI prompts introduces governance risks. If a user can instruct the AI to summarize anything and send it anywhere, the field-level restrictions become less meaningful.

AI Engine uses admin-defined prompt templates. Users trigger AI actions from a selection of templates that the admin has configured and approved. The templates define what the AI is instructed to do, what data it receives, and how the output is formatted. Users cannot modify the underlying prompt or request data outside the configured scope.

This creates a consistent, auditable AI behavior across the team rather than a free-form AI interface that varies by user.

Named Credential Security for API Keys

API keys for OpenAI, Claude, or Azure OpenAI are managed through Salesforce Named Credentials — Salesforce's built-in mechanism for storing and managing external service credentials securely. This means:

• API keys are not visible to end users
• Keys can be rotated from the admin panel without reconfiguring templates
• Access to the credential management is controlled by Salesforce permission sets

Permission Set Controls

AI Engine uses Salesforce Permission Sets to control which users can access which AI actions. Admins can enable AI functionality for specific teams, roles, or individual users — keeping AI access aligned with the organization's existing user management practices rather than introducing a separate permission system.

Data Residency and Provider Choice

Some organizations have data residency requirements that affect which AI provider they can use. For organizations subject to European data protection regulations or sector-specific compliance frameworks, Azure OpenAI provides an alternative to the standard OpenAI API with different data processing commitments and the option to specify data residency regions.

AI Engine supports OpenAI, Anthropic Claude, and Azure OpenAI. The provider is configured by the admin using a Named Credential, and the prompt templates work consistently across providers. Organizations can migrate between providers without rebuilding their AI action configurations.

What AI Engine Does Not Do

To be specific about the security architecture: AI Engine does not store Salesforce field data externally, does not maintain a separate database of CRM records, and does not create persistent API connections that run without user-triggered actions. Each AI action is a point-in-time API call using the field data configured for that template, triggered by a specific user on a specific record. The output is returned to Salesforce and displayed to the user.

Frequently Asked Questions