Quick answer: Salesforce API access for AI agents depends on the OAuth client and flow, the authenticated integration user and that user's effective Salesforce permissions. For new integrations, Salesforce recommends External Client Apps. Gazebo can manage retrieval of a separately stored credential, but does not replace Salesforce authorization or automatically manage its OAuth token lifecycle.
Define the task before configuring access
Start with the objects, fields, records and operations a workflow needs. A lead qualification agent may need to read selected Lead and Contact fields. A deal-desk workflow may need to update certain Opportunity fields. A reporting job may need a different record set without any writes.
Those are task requirements, not ready-made permission sets. Verify dependencies in the real workflow: relationships, automation and the chosen API can affect the permissions needed.
Record:
- The environment and data owner.
- Required reads and writes, including field and record boundaries.
- The principal and OAuth flow that will perform them.
- Which system enforces any business-specific restrictions.
- Allowed and denied tests.
- Who owns token storage, refresh and incident containment.
See agent permissions for a policy matrix that separates the intended rule from its enforcement point.
Use current OAuth client guidance
Salesforce's External Client App guidance states that new Connected App creation is restricted as of Spring 2026. Existing Connected Apps can continue; Salesforce recommends External Client Apps for new integrations.
Choose a flow suitable for the integration. A user's delegated grant and a machine-to-machine flow have different consent, principal and token-lifecycle properties. Not every flow issues a refresh token.
The OAuth client identifies an application, while the authenticated user and applicable Salesforce controls determine effective data access. A client ID is not a substitute for an integration-user permission review.
Use supported OAuth scopes appropriate to the API. Broad API access does not by itself grant every object or record, and scope labels should not be invented as a replacement for permission sets or custom business checks.
Separate users and clients deliberately
A distinct integration user can improve attribution and independent access management. Separate OAuth clients may also help when integrations need different settings, owners or lifecycles.
Neither means “one client and one user for every agent instance” is universally necessary. Consider licensing, administration, trust boundaries and how the selected flow identifies the user.
If several agents share an integration user and credential, Salesforce records may identify that shared principal rather than distinguish each agent. Separate Gazebo retrieval identities do not change the downstream Salesforce user associated with a shared token.
Conversely, different clients using the same broadly privileged user do not automatically create different object or field permissions.
Review effective permissions, not one permission set
Salesforce permissions are additive across applicable grants. Start from an appropriate minimal base for the user's license, then review profiles, permission sets, permission-set groups and other access mechanisms.
For each intended operation, consider:
- Object access: whether the user may read, create, edit or delete the object.
- Field-level security: which fields are readable or editable.
- Record access: sharing, ownership and applicable elevated permissions.
- Execution context: whether the chosen API, Apex or other execution path enforces the restrictions you expect.
- Business rules: restrictions such as an approval threshold may require a trusted application control rather than a generic API grant.
Read access to Contact does not automatically mean every field on every Contact is visible. Equally, removing a grant from one permission set may not remove access supplied elsewhere.
Test field and record boundaries
Use the actual API and integration principal in a sandbox with appropriate test data.
Confirm that permitted fields and records can be accessed, then try prohibited fields, unrelated records and denied writes. Do not infer safety from a field missing in a sample response: the query may not have requested it.
Test the execution path itself. A custom endpoint that runs in an elevated context may need explicit authorization checks even when a standard API request would enforce the expected boundary.
Avoid using real customer data merely to prove the workflow connects. The test should establish permission behaviour without creating a new disclosure path.
Refresh tokens need an explicit owner
For flows using refresh tokens, concurrent workers and rotation require careful handling.
Salesforce's 22 October 2026 notice states that refresh-token rotation is enabled and locked on newly created External Client Apps. Do not assume the same configuration for every existing Connected App, client or OAuth flow.
A runtime using rotating refresh tokens must securely persist replacements and coordinate refresh attempts according to supported provider behaviour. Otherwise, workers may attempt to reuse a retired token or overwrite newer state. Check the current flow-specific rules rather than assuming that exactly one concurrent request always succeeds.
Gazebo does not automatically refresh Salesforce tokens or serialize Salesforce refresh operations. If a team stores a Salesforce access token in Gazebo, its expiry and replacement remain an explicit operational responsibility. Storing a refresh token is not, by itself, a refresh implementation.
Keep refresh credentials out of agent prompts, repositories and ordinary logs. Prefer a supported integration component with a clearly owned lifecycle rather than implementing retries around unexplained authentication failures.
What Salesforce evidence can show
Salesforce provides several monitoring features whose coverage, licensing and retention differ. Check the actual org and event types rather than treating an edition label as a guarantee.
EventLogFile documentation describes delayed availability and completeness limitations. Daily files are not immediate alerts; hourly files can also take time and may omit data later available in daily files.
Available events may help correlate users, API activity and relevant identifiers. Do not promise that every call produces an immediate, durable record of every affected object and record. Protect exported evidence and minimise sensitive payloads.
Gazebo credential-access events answer a different question: which retrieval identity requested a stored credential and what the release outcome was. They do not show which Salesforce records were later read or changed.
Where Gazebo can add value
For several agent clients working across Salesforce and other services, Gazebo may simplify connection setup, approval of retrievable keys and central review of credential access. Its integration tooling provides a consistent retrieval path for supported clients and custom applications.
It does not import Salesforce permission sets, narrow a token's Salesforce privileges or proxy provider operations. Its declared HTTP method is retrieval-policy context only. Authorized retrieval returns the stored credential to the client runtime and host.
Use the credential lifecycle guide to assign ownership for copies, expiry and replacement before using this approach.
Removal and go-live checks
Test these separately:
- Disable an agent's retrieval identity and confirm new retrieval is denied.
- Use Salesforce's appropriate token/session/client/user controls to contain provider access, accounting for other consumers.
- Verify what happens to credentials and sessions already held by a runtime.
- Exercise refresh or expiry failure, permission denial and recovery without widening access.
- Confirm available monitoring arrives within its documented timing window.
Disabling an OAuth client or integration user can affect every consumer sharing it. Select the narrowest effective containment action and verify its effects rather than promising instantaneous isolation.
Expand access only after representative allowed/denied tests and a working incident path. There is no universal two-week staging period or one-afternoon setup that establishes production readiness.
Independent editorial post; not affiliated with or endorsed by Salesforce. Last reviewed: 8 November 2026. Verify current OAuth, licensing, permission and monitoring behaviour for the specific org and integration.