Finding guide

Connected apps with full access

A connected app that asks for the 'full' OAuth scope can do anything its user can, so one leaked token gives that much access to whoever holds it. Most integrations need far less. Auditing connected apps means checking what each one can reach, whether it is still used, and where it can be used from.

By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 17, 2026.

Why it matters

  • A token for an app with the 'full' scope carries the full access of the user who authorized it, often an administrator.
  • Refresh tokens nobody has used in months are usually forgotten integrations whose access still works.
  • Without IP restrictions, a leaked token works from anywhere on the internet.
  • An app with no description can't be safely revoked in an incident, because nobody knows who owns it.

How to check your org by hand

  1. In Setup, open App Manager and review the OAuth scopes on each connected app.
  2. Open Connected Apps OAuth Usage to see which apps are in use and by how many users.
  3. On each app's policies, check the IP relaxation setting and the refresh token policy.
  4. Make sure each app has a description that names its owner and purpose.

How to fix it

  1. Replace 'full' with only the scopes the integration needs, such as 'api' and 'refresh_token'. Agree it with the app's owner and test in a sandbox first.
  2. Revoke and disable apps that nobody can account for.
  3. Enforce IP restrictions for integrations that call from known addresses.
  4. Add a description with the owning team and how to revoke it.

What VanguardOps flags

A scan checks this from metadata with fixed rules, never by reading records:

  • A connected app that requests the 'full' OAuth scope: critical.
  • A connected app with the refresh token scope that hasn't been used in 180 days: important.
  • A connected app with no IP restrictions: important.
  • A connected app with no description: minor.

Common questions

What does the 'full' OAuth scope allow in Salesforce?
Access to everything the signed-in user can reach. Salesforce's documentation describes it as all data accessible by the user. Most integrations only need 'api' and 'refresh_token'.
What scopes does VanguardOps itself ask for?
'api' and 'refresh_token' only. The 'api' scope could technically read records, so the metadata-only limit is enforced in VanguardOps code and checked by automated tests.