Salesforce Agent Registration and Agentic Identity

Salesforce Agentic Identity is the upcoming registration step for AI agents: each agent gets its own identity and a narrower permission set, instead of working under a person's login. Use of any Salesforce MCP (Model Context Protocol) server requires registration within three months of Salesforce's notice that it is available (Salesforce Help 005360285, 17 Sep 2026). The article says Salesforce is "targeting November". No date was published and no notice was out in Help as of 12 November 2026. If Salesforce publishes the notice, the three-month clock starts that day.

What has Salesforce said about registering AI agents?

Almost everything public sits in one Help article, Understand AIforce Impact, published 17 September 2026. AIforce was announced at TDX 2026 as "Headless 360", and Headless Toolkit is the feature set behind it. The article makes four points:

• Salesforce says it is targeting November 2026 for a set of security controls, agent registration and a new billing model. No date was published as of 12 Nov 2026.
• Admins register agents on the platform. Each agent gets "a discrete identity" instead of working under the identity of the person it assists, and admins can give that identity a narrower permission set than a human user.
• Every successful call by a registered agent, over MCP or the API, counts as a Headless Platform Interaction (HPI) and is tracked in Digital Wallet against Flex Credits.
• Traditional integrations keep their current pricing and security options. The new model is for agent traffic.

Salesforce's own metaphor is a badge: the agent gets its own, rather than borrowing an employee's. That matches how most teams use AI clients today, which is the problem. A rep connects Claude or Cursor to the org with their own login, and every action the agent takes looks like the rep.

When does the three-month window start, and who does it cover?

It starts when Salesforce tells customers that Agentic Identity is available. It does not start on a calendar date. The article gives three different rules depending on who you are:

So the MCP rule is the one with no escape hatch. An existing customer can wait for renewal for API agents. Nobody gets that for a Salesforce MCP server.

What changes when you register an agent?

Salesforce lists four steps. The first one is about billing (Salesforce Help 005360285).

1. Make sure the org can use Flex Credits. The article says that means buying Salesforce Foundations, "currently available at $0", or another SKU that enables Flex Credit usage (Salesforce Help 005360285).
2. Register each agent with the new Agentic Identity feature. This is where it gets its identity and its scoped permissions.
3. Change each MCP client and each API agent to present the new OAuth credentials tied to the registered agent. This is the step that lets Salesforce classify the connecting app as an agent.
4. Reconnect. The agent then works as before, and each successful call is recorded as an HPI.

HPIs are metered only in active production orgs. Sandboxes, scratch orgs and Developer Edition orgs do not draw down Flex Credits, so you can build and test there. Metering is also not switched on. The multiplier is listed as "TBA", and Salesforce says it will give 30 days' notice when a number is added (Salesforce Help 005360285).

What is still unknown?

Quite a lot, and it matters for planning. These points are still open in the Help article and in the Winter '27 material Salesforce has published:

• The date of the "Agentic Identity is available" notice, and so the date your three months end.
• The HPI multiplier, so nobody can price an agent call yet.
• What Salesforce counts as an agent when the caller is a third-party tool, a script that wraps the API, or an automation that calls an LLM. The article says "agents that use Salesforce APIs" and does not define the line.
• What happens at the end of the window to an unregistered MCP client. The article does not say.
• Whether registration is required in sandboxes. The article says sandboxes are not metered. It does not say they are exempt from registration.

Ask your Salesforce account executive about each of these in writing. The article itself says to contact them.

What should admins inventory now?

Start the list before the notice arrives. For most orgs it is a day's work.

1. AI clients people use against your org. Ask in the admin channel and in IT: who has connected Claude, Cursor, ChatGPT, Codex, VS Code or a CLI to a production login? Include the ones that run under a person's own user.
2. MCP servers. Salesforce's hosted servers you have activated, plus third-party and in-house servers. That includes ours: if you use the Clientell AI MCP server, put it on the list like any other. Salesforce's Winter '27 architect notes describe Security Center MCP Server Monitoring (Beta), which centralizes visibility into configured MCP servers, and API Catalog, where you register and activate the MCP servers and APIs your agents may call (Salesforce architect highlights, 5 Oct 2026). If your org has them, start there.
3. Connected apps and External Client Apps that an agent uses. In Setup, open App Manager and the External Client App Manager. Open Connected Apps OAuth Usage and note who authorized what. For a fast list of every authorized app per user, run SELECT AppName, User.Username, UseCount, LastUsedDate FROM OauthToken ORDER BY LastUsedDate DESC in the Developer Console. Each row is one grant. To remove one, open Setup, Users, the user, and click Revoke in the OAuth Apps section. Revoking signs that tool out until someone authorizes it again. The OAuth changes guide has the Login History filters.
4. Shared integration users. Any user that three tools log in as will need to be split, because the point of the new identity is one per agent. Write down which tool uses which user.
5. What each agent needs to do. For every agent on the list, write the objects it reads and writes. That becomes the permission set you hand to its identity. Start narrow. The permissions audit guide shows how to find over-broad access today.
6. An owner and a sandbox. Name one person per agent, and a sandbox where you can test the new credentials without spending Flex Credits.

An agent that signs in with the OAuth device flow has a second date to watch. The device flow is restricted to local External Client Apps from 30 November 2026 (Salesforce Help 005461287). Some CLI-based agent setups use it.

How do you test an agent without writing to production?

Use a sandbox and check the change before it is applied. AI Salesforce deployments from Clientell AI run pre-flight checks, take a snapshot before every deploy and ask for approval before anything reaches production. Do the same with any tool. Read the diff before you approve it.

Try it in Clientell AI: "List every connected app and integration user in my org, with the last time each logged in." Book a call with an expert, or start the 14-day trial, no card. Not ready? Run the free health check on your org. Clientell AI MCP is $249 a month and the Platform plan is $500 a month. See pricing.

Sources

Salesforce

• Understand AIforce Impact, Salesforce Help 005360285, 17 Sep 2026
• Winter '27 Release Architect Highlights, Salesforce, 5 Oct 2026
• Connected App and External Client App Security Requirement Updates, Salesforce Help 005461287, 14 Oct 2026

Last reviewed 12 November 2026