What is actually running in your Salesforce org, and what to fix first.

A free health check for the admin who got handed the org and the owner who pays for it. We read setup data and metadata only, revoke our access as soon as the scan ends, and email every finding in plain language, in the order we would fix them. Page one is a summary for whoever owns the org. No meeting needed to read any of it.

A System Administrator approves it on Salesforce's own screen. The scan takes about a minute.

What Salesforce's own tools leave out

Salesforce's Health Check gives you a score. This check tells you which integrations stop working on which Salesforce deadline, who can fix each item and in what order, with a link to the Setup page that shows each finding.

Every finding is free

Each one comes with its criticality, the Salesforce deadline where there is one, what to do and who can do it, so your own admin or developer can work through it. If you would rather we did the work, email us and we come back with a fixed price and a date.

Built so you can check us

Setup data and metadata only, never customer records. The only name and email we keep are those of the person who approves the check. The report prints when our access was revoked and what Salesforce answered, and tells you where in Setup to confirm it.

What the check looks at

  • Integrations on sign-in methods Salesforce is retiring, with the date each one stops: the Use Any API Auth permission for SOAP login() from 1 December 2026, password-based and browser-based OAuth sign-in from 20 February 2027, and SOAP login() on API versions 31 to 64 in Summer '27
  • Integrations that depend on one person's login, and integrations that keep failing to sign in
  • Admin access: whether passkeys (security keys, Touch ID, Windows Hello) are switched on, now that Salesforce requires them for admins, and how many people hold admin-level permissions
  • Outside apps that still hold access to your data, including ones nobody has used in six months or no admin approved
  • AI agents: whether generative AI is on, which agents are active, and whether any agent user holds admin-level permissions
  • Workflow Rules and Process Builder still running after Salesforce stopped fixing them, and flows with no error handling
  • Paid licenses with no login in 90 days, installed packages with no sign of use or on deprecated versions, and storage close to its limit
  • Your Security Health Check score and the high-risk settings behind it

Runs on Enterprise, Unlimited, Performance, Core, Advanced, Max, Agentforce 1, Nonprofit Cloud and Education Cloud orgs, and on Professional or Pro Suite orgs that have the Web Services API add-on. Starter Suite and Free Suite do not expose the API, so the check cannot run there.

Every report is reviewed by Mitesh Jain, founder of Meet The Mind Technologies, a registered Salesforce Consulting Partner.

We read

setup data and metadata, through the Metadata API, the Tooling API and setup objects

  • ·Workflow Rules, Process Builders and Flows: definitions and active flags, run through Lightning Flow Scanner
  • ·Connected apps: app names, installed state, last-used dates and use counts
  • ·Login History: login type, subtype, API type, API version, application and status, grouped by Salesforce user ID
  • ·Users: active flag, last login date, created date, license type and profile, as counts
  • ·Admin-level access: which active users hold Modify All Data, View All Data, Customize Application or Author Apex, by Salesforce user ID, with the profile or permission set that grants it
  • ·Security settings, including whether security keys and built-in authenticators are allowed, and whether Einstein generative AI is on
  • ·AI agents: each agent's name, type and active status, how many users can build agents, and which users are on an agent license
  • ·The Security Health Check score and its risk settings
  • ·Installed packages: versions, flags, licenses and seat counts, and signs of use as counts
  • ·Setup Audit Trail: counts of package install and upgrade events, from the action and date only, never the entry text
  • ·API request usage and storage against their limits

We never read

  • ·Customer records of any object: no Accounts, Contacts, Leads, Opportunities, Cases, custom object records, files or attachments
  • ·Token values
  • ·Names, usernames or email addresses of anyone except the person who approves the check
  • ·Report results, dashboards, email content, Chatter, site traffic or event logs

The api scope is what Salesforce offers for this work, and it permits writes. We use it to read, we write nothing, and we revoke our access when the scan finishes.

Object and field names, retention and sub-processors

How it works

  1. 1

    Click Run the free check. A System Administrator has to approve it; if that is not you, forward this page to your admin. Start and approve in the same browser, because a link forwarded halfway through will not start a check.

  2. 2

    Salesforce shows its own approval screen for "MTM Org Health Check", with the permission line "Manage user data via APIs (api)". That is Salesforce's wording. Click Allow. The screen appears every time, even for someone who approved it before.

  3. 3

    If Salesforce shows an "OAuth Error" page instead, with the code OAUTH_APPROVAL_ERROR_GENERIC, the org blocks apps nobody has installed yet, a Salesforce security change from September 2025. An admin can either give the person running the check the Approve Uninstalled Connected Apps permission through a permission set, or install MTM Org Health Check from Setup, Connected Apps OAuth Usage. Then open the link again. Stuck? Email partners@meethemind.com and we will walk you through it.

  4. 4

    The scan usually takes under a minute. When it finishes we revoke our access and record the time and Salesforce's answer.

  5. 5

    Mitesh reviews every report before it goes out. Once approved, the report link is emailed to the Salesforce user who approved the check, at the verified email address on their Salesforce user record; if Salesforce has not verified it, Mitesh sends the link by hand after confirming who asked. You get it within one working day. Reply to that email if any finding looks wrong and it is corrected.

If Salesforce answers API_DISABLED_FOR_ORG after Allow, the edition has no API access (Starter, Free Suite, or Professional without the Web Services API add-on). The page says so in plain words and the check stops there.

Send this to your admin

Only a System Administrator can approve the check. If you are the owner, president or head of operations, forward this page to whoever administers Salesforce and ask them to run it. Page one of the report is written for you, with the admin's fixes behind it. If nobody administers your Salesforce, write to partners@meethemind.com and Mitesh will tell you which login can run it.

Who this is for

  • The admin who inherited the org, with no documentation and automation the previous person never wrote down. The report is the inventory, and every headline number can be checked in Setup before anyone acts on it.
  • The solo admin with no developer to hand the migration to and no time to read Login History by hand.
  • The owner or head of operations at a company or small college where nobody owns Salesforce, who pays the invoice and has never seen what is inside. Page one is written for you: what we found, what to fix first, and by when.

Not for: data quality, duplicate records, report accuracy, user adoption or renewal negotiation. Those need records or your contract, and we read neither.

Frequently asked questions

You are asking me to approve an outside app after the Salesloft Drift incident. Why should I?

You should not take it on trust. The check reads setup data and metadata only and revokes its access when the scan finishes. The report prints the revoke time and Salesforce's answer, and tells you which Setup page shows our app and how to revoke it yourself, so the proof comes from Salesforce rather than from us. If Salesforce does not confirm the revoke, the report says so plainly and Mitesh follows up. One of the findings is the list of outside apps that still hold access to your org.

What does "access revoked" mean in practice?

When the scan finishes, we ask Salesforce to revoke our token and record the time and Salesforce's answer; the report prints both. After that the app cannot reach your org again unless someone approves it again. Setup, Connected Apps OAuth Usage keeps a line showing that you approved the app. That line is not access, and Revoke removes it.

Is this GDPR compliant, and will you sign a DPA?

We do not read your customers' personal data, because we do not read records. We do read setup data that includes Salesforce user IDs and login times, which count as personal data of your staff under UK and EU law, and we keep the name and email of the person who approves the check. The privacy notice and a data processing agreement are covered on the data and privacy page. UK and EU organisations can ask for the DPA to be signed before they approve the check.

Production or sandbox?

Production, because the findings are about what is running. A sandbox has different apps, login history and users. If your policy requires a sandbox first, run it there with the sandbox link, read the report, then run production.

Can I run it again after fixing things?

Yes. The same link works as many times as you like. Each run is a fresh check with a new report, so you can see what changed.

What happens after I get the report?

Mitesh may email you once to ask whether it was useful, and you can tell us to stop at any time. If you want the fixes done, write to partners@meethemind.com with the fix numbers and we come back with a fixed price and a date. If a finding is wrong, write and it gets corrected.

Does the report include a price?

No. The report tells you what to fix and in what order, so your own team can do it. If you want us to do it, email us with the fixes you care about and we quote a fixed price and a date.

Salesforce shows an OAuth Error, or says the API is off. Now what?

OAuth Error: see step 3 above. API off: Starter Suite and Free Suite have no API, and Professional and Pro Suite need the Web Services API add-on, so the check cannot run there.

See what is running in your org, and what to fix first.

A System Administrator approves it on Salesforce's own screen. The scan takes about a minute.