ORG HEALTH CHECK
✓Request
✓Connect & scan
3Report
SAMPLE REPORT · EXAMPLE FIGURES
This is what your report looks like. The org and every figure below are fictional. Open any finding to see the fix steps and official Salesforce links you would get.
ORG HEALTH REPORT · SAMPLE
Northwind Logistics
Prepared for Alex Morgan on 14 September 2026
Download PDF report
ORG ID
00DXX0000000SAMPLE
EDITION
Enterprise Edition (production)
SCANNED
14 September 2026
CHECKS ASSESSED
13 of 13
ACCESS REVOKED · VERIFIEDAddonblue no longer has access to your org.
We revoked our access at Sep 14, 9:44 AM, as soon as the scan finished. We then tried the old token once more and Salesforce refused it, so it cannot be used again by anyone, including us.
Check it yourself in Salesforce
You don’t need to take our word for it. Any admin in your org can confirm it in a minute.
1
Setup → Connected Apps OAuth Usage
“AddonBlue Org Health Check” should not be listed: this page only shows apps that still hold an active token. If it is there, click Revoke All, or Block to stop it connecting again.
Salesforce Help: Manage Current OAuth Connected App Sessions ↗2
Your settings → Advanced User Details → OAuth Connected Apps
Signed in as admin@northwind.example: there should be no access listed for “AddonBlue Org Health Check”. Admins see the same list on any user’s detail page under OAuth Connected Apps.
Salesforce Help: Manage OAuth-Enabled Connected Apps Access to Your Data ↗3
Setup → Login History
You will see the sign-in through “AddonBlue Org Health Check” at Sep 14, 9:41 AM, and no new sign-ins from it after Sep 14, 9:44 AM.
Salesforce Help: Monitor Login History ↗OVERALL SCORE
53/100
AT RISKACTION NEEDED
4
TO REVIEW
4
HEALTHY
2
AREASCORE
Users & access20
Security73
Code quality33
Automation20
Limits80
Top priorities
1
Active users with no login in 90 days 46 users (22%)
Freeze or deactivate them, and add a quarterly licence review.
How to fix: Freeze or Unfreeze User Accounts ↗ACTION NEEDEDLow effort
2
Objects with more than one active trigger Opportunity (3), Account (2), Case (2), Shipment__c (2)
Consolidate to one trigger per object behind a handler framework.
How to fix: Apex Trigger Fundamentals and Best Practices (Trailhead) ↗ACTION NEEDEDMedium effort
3
Org-wide Apex test coverage 58%
Add tests with real assertions around your most-changed classes first.
How to fix: Testing and Code Coverage (Apex Developer Guide) ↗ACTION NEEDEDHigh effort
4
Process Builders and Workflow Rules 7 Process Builders, 79 Workflow Rules
Migrate to Flow, one object at a time, starting with the busiest objects.
How to fix: Workflow Rules & Process Builder End of Support ↗ACTION NEEDEDHigh effort
All findings
Select a finding for detail and recommendations.
Scores are based on settings, metadata and counts only. No record data was read or stored during this scan.
Talk the findings through with a Salesforce architect.
In 30 minutes we'll confirm what matters most for your team and map out the fixes.
Book a walkthroughRun my free health check