Home›Agents›Salesforce Agentforce

AgentenCode evidence profileEnterprise

✓ Editorially reviewedChecked: October 1, 2026

Agent profile · Enterprise

Salesforce Agentforce

Salesforce Agentforce is classified by AgentenCode as an enterprise agent platform from Salesforce. It belongs to the Enterprise category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

SalesforceEnterpriseOrganizations

View profile ↓Check sources ↓

AGENTENCODE RESEARCH

Multi-Agent Intelligence: Research & Architecture

How collaborating AI agents work: orchestration, delegation, external benchmarks and auditable evidence.

Explore the research guide → · Orchestration patterns · Studies & benchmarks · Evidence methodology

Enterpriseeditorial classification

Salesforceprovider

16 primary sourcessource status

October 1, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Salesforce Agentforce

Direct answer: AgentenCode currently documents 9 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access4 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control2 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability1 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Auth · Oauth

Yes — documented

Agent API access uses an OAuth client-credentials application flow.

Scope: agent_api_external_client_app · verified 2026-10-01 · Primary source ↗

High confidence

API · Rest

Yes — documented

A REST Agent API is available for supported Agentforce agent types.

Scope: supported_agent_types · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Approval · Pre Action

Yes — documented

When enabled, the agent must ask the user to confirm a record-changing action before it executes.

Scope: record_changing_custom_actions · verified 2026-10-03 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Agent action attribution is documented.

Scope: agent_actions · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Human approval

Yes — documented

Custom Agent Actions can require user confirmation for record-changing actions.

Scope: record_changing_custom_actions · verified 2026-10-03 · Primary source ↗

High confidence

Governance · Permission Sets

Yes — documented

Permission-set control is documented.

Scope: external_service_agents · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Agentforce access and agent capabilities are governed by Salesforce role/permission controls.

Scope: agentforce_salesforce_org_access · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Tracing

Yes — documented

Agentforce execution tracing is documented through Agent Platform Tracing.

Scope: agent_platform_tracing · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

Agentforce is offered on Salesforce-managed Hyperforce cloud infrastructure.

Scope: agentforce_on_hyperforce · verified 2026-10-01 · Primary source ↗

High confidence

Identity · Agent User

Yes — documented

Agent-user execution identity is documented.

Scope: external_service_agents · verified 2026-10-01 · Primary source ↗

High confidence

Memory · Session State

Yes — documented

Agent Script variables retain state across conversation turns and are accessible to subagents in the agent.

Scope: agent_script · verified 2026-10-03 · Primary source ↗

High confidence

Operations · Execution Timeout Seconds

120

Salesforce documents a 120-second timeout for Agent API calls.

Scope: agent_api · verified 2026-10-03 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Agentforce can use Hyperforce regional data-residency capabilities where available.

Scope: agentforce_on_hyperforce_supported_regions · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Hyperforce provides customer choice of supported geographic regions.

Scope: hyperforce_supported_regions · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

Agentforce can act as an MCP client.

Scope: agentforce_agents · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Registry

Yes — documented

Agentforce provides an MCP server registry and governed tool allowlisting.

Scope: agentforce_registry · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Remote

Yes — documented

Remote MCP integrations are documented.

Scope: externally_hosted_servers · verified 2026-10-01 · Primary source ↗

High confidence

Sdk · Python

Yes — documented

A first-party Agentforce Python SDK is documented in Salesforce's official repository.

Scope: agentforce_development · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Salesforce Agentforce?

Product-specific evidence for Salesforce Agentforce

This profile links 16 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Enterprise.

Data Residency

Yes · Scope: agentforce_on_hyperforce_supported_regions · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: hyperforce_supported_regions · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

Yes · Scope: agentforce_customer_data_on_hyperforce · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

Yes · Scope: agentforce_customer_data_on_hyperforce · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: einstein_platform_and_agentforce_on_hyperforce · verified 2026-10-01.

Primary source ↗

Pre-Action Approval

Yes · Scope: record_changing_custom_actions · verified 2026-10-03.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

21field-level evidence claims

9documented trust controls

4history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Salesforce Agentforce is documented under Enterprise and is associated with Salesforce. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 1, 2026.

Trust coverage

9 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Salesforce Agentforce

Salesforce Agentforce is classified as Enterprise Agent Platform from Salesforce. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Customer Service

This use case is part of the stored profile for Salesforce Agentforce. The related strength is “Tiefe Salesforce-Integration”. In a production evaluation, the practical boundary to verify is: CRM-Datenzugriffe nach Rolle begrenzen.

Sales

This use case is part of the stored profile for Salesforce Agentforce. The related strength is “CRM- und Datenkontext”. In a production evaluation, the practical boundary to verify is: Autonome Aktionen testen.

CRM-Automation

This use case is part of the stored profile for Salesforce Agentforce. The related strength is “Agent Builder und Governance”. In a production evaluation, the practical boundary to verify is: Kosten- und Verbrauchsmodell prüfen.

Mitarbeiterprozesse

This use case is part of the stored profile for Salesforce Agentforce. The related strength is “Breites Enterprise-Einsatzfeld”. In a production evaluation, the practical boundary to verify is: CRM-Datenzugriffe nach Rolle begrenzen.

What to verify before adoption

CRM-Datenzugriffe nach Rolle begrenzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Autonome Aktionen testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Kosten- und Verbrauchsmodell prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 1, 2026 · Source Maintenance
October 1, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 16 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Salesforce Agentforce?

Salesforce Agentforce is listed by AgentenCode as an enterprise agent or agentic product from Salesforce.

How much trust evidence is documented for Salesforce Agentforce?

The current trust layer documents 9 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.