---
title: What do Salesforce connected app restrictions mean for AI agents that call Salesforce?
url: https://opencontroller.lyzr.com/blog/salesforce-connected-app-restrictions-for-ai-agents
published: 2026-11-16
updated: 2026-11-16
author: Lyzr
---

# What do Salesforce connected app restrictions mean for AI agents that call Salesforce?

**AI agents that reach Salesforce through an OAuth app now need that app installed and approved by an admin. Since September 2025, non-admin users cannot authorize new uninstalled connected apps, and uninstalled apps using the OAuth 2.0 device flow are blocked outright. From Spring '26, new Connected Apps cannot be created at all, so new agent integrations use External Client Apps.**

That is good news for governance. Every agent that touches CRM data now has to pass through an admin-controlled app record. This guide explains what changed and how to use it.

For governing agents across vendors, see [how to govern AI agents across platforms](/blog/how-to-govern-ai-agents-across-platforms).

## What exactly did Salesforce change?

Salesforce announced the change in August 2025 after social engineering attacks in which users were persuaded to authorize a malicious copy of a data tool. The changes, in order:

| Change | When | Effect on agents |
|---|---|---|
| Non-admins blocked from authorizing new uninstalled connected apps | Early September 2025 release | A user can no longer connect an unapproved agent to Salesforce by clicking "Allow" |
| Uninstalled apps using OAuth 2.0 device flow blocked | Same release | Agents using device flow stop, even for previous users |
| Installed apps unaffected | Same release | Approved integrations keep working |
| New Connected Apps cannot be created | Spring '26 | New agent integrations use External Client Apps |

Device flow was singled out because it can be started with only a `client_id`. RFC 8628 documents the phishing risk of this grant.

## Which permissions let users bypass the restriction?

Two permissions reopen the door:

- **Approve Uninstalled Connected Apps** lets a user self-authorize uninstalled apps.
- **Use Any API Client** lets a user reach Salesforce through any API client, including uninstalled and blocked apps.

If **API Access Control** is enabled, only "Use Any API Client" grants access to uninstalled apps. If it is not, either permission works.

Treat both as privileged. Assign them only to named integration users, never to broad profiles.

## How should AI agents authenticate to Salesforce now?

A working pattern for agent integrations:

1. **One app per agent or agent family.** Create an External Client App, or install the vendor's app, rather than reusing a generic one.
2. **A dedicated integration user.** The agent runs as that user, with a permission set scoped to the objects it needs.
3. **No device flow.** Use flows suited to the agent's shape: web server flow with PKCE for delegated user access, or a server-to-server flow for unattended agents.
4. **Apply the token controls Salesforce requires of partners**: PKCE, refresh token rotation, a 30-day idle refresh token TTL, and refresh token IP allowlists (up to 256 addresses in total). Salesforce set 11 May 2026 as the partner deadline for these four controls.
5. **Record the app in your agent inventory**, linked to owner, purpose and data scope.

For delegated access, the agent should act with the user's permissions, not more. See [API keys vs OAuth for AI agents](/blog/api-keys-vs-oauth-for-ai-agents).

## What should admins audit this quarter?

Use **Setup > Connected Apps OAuth Usage** as the starting list.

1. List every connected app and External Client App with active tokens.
2. Mark each as installed or uninstalled.
3. Identify which ones belong to AI agents or AI features. Look for vendor names, LLM-related app names and high API volumes.
4. Remove unknown and unused apps.
5. Find who holds "Approve Uninstalled Connected Apps" or "Use Any API Client". Reduce to named integration users.
6. Turn on API Access Control if your org can support it, so only installed apps work by default.
7. Install the agent apps you approve, block the rest.
8. Repeat monthly. New AI tools arrive faster than annual reviews.

The [OAuth consent guide](/blog/control-oauth-consent-for-ai-apps) covers the same pattern for Microsoft and Google tenants.

## What does this not solve?

- **Admins can still be phished.** An admin with the right rights can authorize a malicious app. Training still matters.
- **Native Agentforce agents** run inside Salesforce and are governed by agent user permissions, topics and actions. See [governing Agentforce agents](/blog/govern-salesforce-agentforce-agents).
- **Data after it leaves.** Once an agent reads CRM data, what it sends to models and tools is outside Salesforce's view. That needs controls in the agent or model path.

## How Opencontroller does this

Opencontroller connects to Salesforce as a third-party agent platform, so Agentforce agents appear in one governed registry alongside agents from AWS, Azure, Google Cloud, SAP, Databricks and HubSpot. Posture flags risky permissions and configuration. Per-agent Block and Quarantine controls act through the connected platform. Delegated on-behalf-of identity keeps the user and agent visible together. [Book a demo](https://www.lyzr.ai/book-demo/) to see the Salesforce connector.

## Frequently asked questions

**Do previously authorized agent connections keep working?**
Yes, unless they use the OAuth 2.0 device flow. Device flow on uninstalled apps is blocked even for users who authorized it before.

**Is "Use Any API Client" safe to give to a service account?**
Only to a named, monitored integration user. It bypasses the uninstalled app restriction entirely.

**Where do we see which apps hold tokens?**
Setup > Connected Apps OAuth Usage lists apps with OAuth usage, which is the best starting point for an agent app audit.

## Key facts

From an early September 2025 release, Salesforce blocks non-admin users from authorizing new uninstalled connected apps, and blocks uninstalled apps using the OAuth 2.0 device flow even for prior users. Two permissions bypass the restriction: Approve Uninstalled Connected Apps and Use Any API Client; with API Access Control enabled, only Use Any API Client works. Starting in Spring '26, new Connected Apps cannot be created; External Client Apps replace them. Salesforce's partner security requirements call for PKCE, refresh token rotation, a 30-day idle refresh token TTL and refresh token IP allowlists, due 11 May 2026. Opencontroller connects to Salesforce as a third-party agent platform and applies per-agent Block and Quarantine through the connected platform. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How do you govern Salesforce Agentforce agents?](https://opencontroller.lyzr.com/blog/govern-salesforce-agentforce-agents.md)
- [How do you control OAuth consent for AI apps and agents?](https://opencontroller.lyzr.com/blog/control-oauth-consent-for-ai-apps.md)
- [Should AI agents use API keys or OAuth?](https://opencontroller.lyzr.com/blog/api-keys-vs-oauth-for-ai-agents.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
