{"id":3069,"date":"2026-09-16T07:30:20","date_gmt":"2026-09-16T07:30:20","guid":{"rendered":"https:\/\/dmarketertayeeb.com\/blog\/salesforce-aiforce-access-interfaces-controls\/"},"modified":"2026-09-16T07:31:04","modified_gmt":"2026-09-16T07:31:04","slug":"salesforce-aiforce-access-interfaces-controls","status":"publish","type":"post","link":"https:\/\/dmarketertayeeb.com\/blog\/salesforce-aiforce-access-interfaces-controls\/","title":{"rendered":"Salesforce AIforce: Access, Interfaces, Controls and What Buyers Need to Verify"},"content":{"rendered":"\n

Short answer:<\/strong> Salesforce AIforce is a live interface layer, not a new AI model. Salesforce says it brings its data, workflows, business logic, identity, permissions and governance into the places where people and agents already work. The launch names Claudeforce, Slackforce and Agentforce Coworker as ready-to-use experiences, while the Headless Toolkit supplies MCP servers, APIs, plug-ins, skills and developer tools for custom experiences.<\/p>\n\n\n\n

That makes AIforce a buyer and access question rather than a model-selection question. The announcement does not publish one AIforce model ID or a standalone price. It says availability can vary by region and customer agreement. The practical way to evaluate it is to identify the exact interface, org configuration, license, data path and action authority your team will use, then test a read-only workflow before allowing writes.<\/p>\n\n\n\n

This guide separates Salesforce\u2019s umbrella language from the concrete interfaces and developer surfaces underneath it. It also keeps vendor promises\u2014such as zero data retention and \u201cday one\u201d access\u2014separate from the controls an administrator must verify in a real org.<\/p>\n\n\n\n

What AIforce is\u2014and what it is not<\/h2>\n\n\n\n

Salesforce\u2019s AIforce announcement<\/a> describes AIforce as a \u201clive interface layer\u201d that lets people and agents use Salesforce from Claude, Slack, Lightning and other surfaces. The current AIforce product page<\/a> uses the same framing: AIforce dynamically brings together the Salesforce data, apps, workflows and business context already in an organization.<\/p>\n\n\n\n

\n\n
Term<\/th>Documented meaning<\/th>Do not assume<\/th><\/tr><\/thead>\n
AIforce<\/strong><\/td>The live interface layer and umbrella experience that carries Salesforce context and actions into other interfaces.<\/td>A single foundation model, downloadable weights, public anonymous chatbot or universal license.<\/td><\/tr>\n
Headless Toolkit<\/strong><\/td>The underlying architecture using Salesforce MCPs, APIs, plug-ins, skills and developer tools.<\/td>A separate model provider or a promise that every capability is enabled in every org.<\/td><\/tr>\n
Headless 360 MCP Server<\/strong><\/td>A specific Salesforce-hosted MCP server, currently documented as a Beta service, with four tool types and org authentication requirements.<\/td>Another name for all of AIforce or a no-setup public endpoint.<\/td><\/tr>\n
Claudeforce<\/strong><\/td>The Salesforce\u2013Anthropic partnership; Salesforce in Claude is the initial seller-focused experience.<\/td>Proof that every Claude account or Salesforce org has the same access state.<\/td><\/tr>\n
Slackforce<\/strong><\/td>Salesforce context and live interactive Surfaces in Slack, with Slackbot, Slack CRM and Slack Code described in the launch material.<\/td>A new Slack plan, price or feature entitlement that has been published for all customers.<\/td><\/tr>\n
Agentforce Coworker<\/strong><\/td>An AI teammate that runs in Salesforce\u2019s Lightning experience and can call specialized Agentforce agents.<\/td>A guarantee that every user, object and action is available without license or permission review.<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n

Salesforce\u2019s regional Newsroom story is dated September 15, 2026, while its Singapore press-release page is dated September 16. Both describe the Dreamforce launch and were current when checked on September 16. That date difference does not change the access rule: use the current org and customer agreement, not a launch headline, as the availability source.<\/p>\n\n\n\n

Which interfaces launch with AIforce?<\/h2>\n\n\n\n

The launch is a collection of surfaces with different maturity and setup paths. The status column below preserves Salesforce\u2019s own wording where the pages disagree or remain conditional.<\/p>\n\n\n\n

\n\n
Surface<\/th>What Salesforce documents<\/th>Safe access interpretation<\/th><\/tr><\/thead>\n
Salesforce in Claude \/ Claudeforce<\/strong><\/td>A prebuilt Salesforce MCP server and 37 sales skills covering work such as prospecting and pipeline hygiene. The launch release says it is available to all customers in beta.<\/td>The dedicated Claudeforce page simultaneously says selected pilot customers are live and open beta is planned for September 2026. Treat it as pilot\/beta until the exact Salesforce and Claude accounts show access.<\/td><\/tr>\n
Slackforce<\/strong><\/td>Slackforce Surfaces can present live Salesforce, Slack and other-tool context in interactive views. The launch also describes Slackbot, Slack CRM and Slack Code workflows.<\/td>Salesforce names it as launching with AIforce, but the cited launch material does not give a universal price, region matrix or org-by-org entitlement.<\/td><\/tr>\n
Agentforce Coworker<\/strong><\/td>The launch and product page describe an AI teammate that reasons across accounts, activity and history, surfaces insights and takes action within Salesforce permissions and business rules.<\/td>Salesforce says customers can activate it, but the actual org still needs the applicable product, license, permissions and data configuration. Confirm the button and entitlement in Setup.<\/td><\/tr>\n
Custom Headless Toolkit experience<\/strong><\/td>Developers can use Salesforce MCP, APIs, plug-ins, skills and developer tools to extend existing interfaces or build a custom one.<\/td>This is an implementation surface. \u201cOpen by design\u201d does not mean unauthenticated, unrestricted or free of API, OAuth, license and governance requirements.<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n

Do not collapse the surfaces into one product demo. A seller asking Claude for a pipeline review, a team exploring a Slack Surface and an admin activating Coworker may touch the same Salesforce foundation but have different contracts, clients, permissions and measured outcomes.<\/p>\n\n\n\n

AIforce access in practice: the four checks<\/h2>\n\n\n\n

For a custom or developer-led path, Salesforce\u2019s Headless 360 MCP reference<\/a> is the most concrete access document available. It identifies a production server URL and a sandbox\/scratch URL, but the server is a Beta service and requires org-side setup.<\/p>\n\n\n\n

    \n
  1. Confirm the org and API version.<\/strong> The Headless 360 reference lists API version v67.0 and later. Check the actual org, edition, release and feature availability before designing around it.<\/li>\n
  2. Activate the service.<\/strong> In Salesforce Setup, find MCP Servers and activate headless-360<\/code> if it is available to the org. Activation is not the same as granting every action.<\/li>\n
  3. Create the authenticated client.<\/strong> Salesforce documents an External Client App configured with the mcp_api<\/code> scope and an MCP client configured with OAuth. A custom client should keep credentials server-side and use the minimum scope the workflow needs.<\/li>\n
  4. Test with the right tool order.<\/strong> The server exposes Discover, Describe, Dispatch and Dispatch (Read-Only). Start with discovery and description, then use read-only dispatch against a sandbox or Developer org before permitting a write dispatch.<\/li>\n<\/ol>\n\n\n\n

    Salesforce\u2019s Try Headless 360 quick start<\/a> describes a Developer Edition org, Salesforce Hosted MCP activation, an External Client App, OAuth and a Claude connector that reads records through an MCP server. That is a source-checked setup path, not a completed test in this article. No credentials or live org were used here.<\/p>\n\n\n\n

    There is a small tension between the product promise and the technical path. Salesforce markets AIforce experiences as requiring no migration or custom integration work, while the custom Headless 360 reference requires activation, an app, an OAuth client and permissions. Read the promise as applying to a supported ready-made experience after an admin connects it; read the developer reference as the setup contract for a custom or hosted-MCP path.<\/p>\n\n\n\n

    What the four Headless 360 tools actually control<\/h2>\n\n\n\n
    \n\n
    Tool<\/th>Purpose<\/th>Control to require<\/th><\/tr><\/thead>\n
    discover<\/code><\/td>Finds candidate Salesforce operations from the agent\u2019s interpretation of a request.<\/td>Review the returned operation instead of allowing a model to choose a write action blindly.<\/td><\/tr>\n
    describe<\/code><\/td>Returns an operation\u2019s APIs, parameters, dependencies and ordered steps.<\/td>Check fields, dependencies, side effects and input validation before dispatch.<\/td><\/tr>\n
    dispatch_readonly<\/code><\/td>Runs an operation in read-only mode and does not change data or configuration.<\/td>Use it first for data mapping, stale-record checks and pilot evidence.<\/td><\/tr>\n
    dispatch<\/code><\/td>Invokes the selected operation through the access guard.<\/td>Require explicit human approval for record changes, user administration, named credentials, deployments or other irreversible actions.<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n

    Salesforce says each Hosted MCP transaction runs as the authenticated user. Object permissions, field-level security, sharing rules, profile permissions and permission sets apply, and the audit trail attributes the action to that user. This is a strong boundary, but it is not a substitute for least privilege: an agent inheriting an overpowered user can still be overpowered.<\/p>\n\n\n\n

    Salesforce specifically recommends client-level tool restrictions and approval before a tool changes org configuration or alters or deletes data. Use a sandbox or Developer org for configuration changes first. Keep the user\u2019s intent, the selected operation, the fields changed, the approval and the final result in an audit record that a reviewer can understand.<\/p>\n\n\n\n

    AIforce, Agentforce and the trust boundary<\/h2>\n\n\n\n

    AIforce sits above Salesforce\u2019s existing Data 360, Customer 360 and Agentforce layers. The launch says every request runs through existing permissions and business rules, every agent sees only what the requesting person can see, and actions route back through Salesforce. The product page similarly presents identity, permissions, trust and governance as capabilities carried into each interface.<\/p>\n\n\n\n

    Salesforce also describes AIforce as having Zero Data Retention<\/strong>: business data is used to answer the question and is not retained by the model provider. Treat that as Salesforce\u2019s contractual\/product assurance about the external model-provider boundary, not as \u201cnothing is ever stored anywhere.\u201d The Trust and Agentforce reference<\/a> says prompts and responses are not stored or used for training by third-party LLMs, while audit and feedback data can be logged in Data 360 and other Salesforce features can store data.<\/p>\n\n\n\n

    The same Trust reference says data masking through the Einstein Trust Layer is disabled for agents. That makes data minimization an application responsibility: pass only the fields required for the task, enforce sharing and field-level security, and do not assume that a generic \u201ctrust layer\u201d makes a broad record dump safe.<\/p>\n\n\n\n

    For MCP specifically, Salesforce documents that the same Agentforce security and compliance controls apply, including the Trust Layer and zero-data-retention policy. A team should still document which third-party MCP servers, plug-ins or AI interfaces sit outside Salesforce and apply zero-trust review to those connections.<\/p>\n\n\n\n

    Pricing and licensing: what is actually published?<\/h2>\n\n\n\n

    There is no AIforce price card in the AIforce announcement or product page. Salesforce says pricing and packaging are subject to change, availability may vary by region, and customer agreements govern the final commercial terms. The current Agentforce pricing page<\/a> is useful adjacent context, but it does not say that every AIforce or Headless Toolkit capability is included at the listed price.<\/p>\n\n\n\n

    \n\n
    Published adjacent item<\/th>Current page shows<\/th>Buyer warning<\/th><\/tr><\/thead>\n
    Salesforce Foundations<\/td>$0 and includes Agentforce Builder, Prompt Builder, Agent Script, Agentforce Coworker and Agentforce Vibes.<\/td>This is the Agentforce pricing page\u2019s bundle; it is not a standalone AIforce contract or proof that every interface is enabled.<\/td><\/tr>\n
    Flex Credits<\/td>$500 per 100,000 credits on the US page; the page describes action-based consumption and Digital Wallet monitoring.<\/td>Do not apply this rate to AIforce without the exact order form, usage type, action multiplier and required products.<\/td><\/tr>\n
    Conversations<\/td>$2 per conversation on the US page.<\/td>The page says this is a customer-facing Agentforce consumption option; it does not price all AIforce surfaces.<\/td><\/tr>\n
    Agentforce add-ons<\/td>$125 per user\/month for listed Sales, Service, Field Service and Operations add-ons; $150 for Industries add-ons.<\/td>These are named Agentforce add-ons and may have edition, contract and region conditions.<\/td><\/tr>\n
    Agentforce 1 Editions and User License<\/td>From $550 per user\/month for listed Agentforce 1 Editions; $5 per user\/month for the Agentforce User License, which requires Flex Credits.<\/td>These are not a published AIforce price. Match the exact SKU, included credits, limits and unmetered scope to the quote.<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n

    The Agentforce FAQ says customers should contact their Account Executive for current contract status and pricing, and that Data 360 must be enabled to view credit consumption in Digital Wallet. For a buyer, the quote should name the exact interface\u2014Salesforce in Claude, Slackforce, Coworker or custom Headless\u2014plus the org, users, region, billing unit, included usage, overage treatment, data services and support\/SLA.<\/p>\n\n\n\n

    Do not use the pricing figures above to estimate ROI. They are dated public list-price inputs for related Agentforce offerings, not a complete AIforce commercial model. The Salesforce edition and buying checklist<\/a> covers edition arithmetic and quote reconciliation as a separate reader job.<\/p>\n\n\n\n

    Beta, rollout and region boundaries<\/h2>\n\n\n\n

    Several current Salesforce pages use different status labels:<\/p>\n\n\n\n