Salesforce org-health assessment
Turn Salesforce org findings into a prioritized backlog.
Assess org health, rank issues by impact, and create actionable Jira work items.
Assess→Prioritize→Act
Free, read-only assessments in Chrome’s side panel. No Salesforce package installation required. Analysis runs locally, with no OrgTriage server or telemetry.
Choose how you work
OrgTriage for Chrome
Assess ten areas of org health from Chrome’s side panel. Review prioritized findings and export a remediation plan with effort estimates.
Chrome Web Store listing pending.
Claude Code skills
Assess an org through the Salesforce CLI and build the same prioritized backlog. A second skill takes one item and does the work in a Salesforce project, on a branch, with a pull request for review.
Published with the source repository.
In-org app
Review findings and coordinate remediation with your team inside Salesforce, kept over time rather than read from one admin’s browser.
Release timing to be announced.
What it checks
Ten areas, each scored on its own and combined into one org-health grade. Every rule cites the documentation behind it — Salesforce’s, or the open-source linter the rule came from — and says plainly when a threshold is our recommendation rather than a Salesforce limit.
- ApexOrg-wide and per-class test coverage against the 75% deployment gate, triggers without coverage, stale API versions, failing and stale test runs.
- Apex code qualitySource-level patterns in your own classes: empty catch blocks, hard-coded ids, unbounded queries, oversized classes.
- FlowsDML and queries inside loops, missing fault paths, run-order collisions, old API versions, version clutter, never-activated flows, Process Builder and workflow rules still in place.
- Reports & dashboardsReports with no filters, unindexed filters, long-text filters that silently truncate, dashboards that never refresh or point at reports the scan cannot find.
- Layouts & SLDSField-heavy layouts against Salesforce's own recommendation, Lightning page component counts, and stylesheet checks for retired SLDS patterns.
- Field usageCustom fields nothing references, fields with no description, validation rules carrying ids that will not survive a deployment.
- Access & permissionsDormant admins, Modify All Data holders, passwords set never to expire, unassigned permission sets, idle licences.
- Security settingsYour Health Check score and the settings that sit below Salesforce's baseline, read from the same API the Setup page uses.
- OperationsScheduled jobs in error, orphaned jobs, paused flow interviews, stuck approvals, release updates due, hard-coded URLs in buttons.
- Limits & storageData and file storage, the rolling 24-hour API allowance, debug-log volume, and every org limit with little headroom left.
From finding to backlog
A finding is not a to-do. Each one becomes a backlog item with a priority, the components it touches, step-by-step remediation, acceptance criteria and an estimate in hours and points. The plan exports to Markdown, to CSV for any tracker, and to a Jira import that creates Bugs for behaviour that is wrong and Tasks for maintenance and cleanup.
Understand the scan
- Read-only. It reads configuration, metadata and Apex source. It never writes to your org, never executes a report, and never reads business records — no accounts, contacts, leads or custom data.
- Your session, in your browser. API calls go from the extension’s service worker straight to your own Salesforce org. The session id is used only to authenticate those calls and reaches nothing else.
- No backend, no telemetry. There is no OrgTriage server. Scan results live in your browser’s local storage and nowhere else, and you choose when to export a plan.
- Costed. Every area shows the API calls it spent, and the footer shows what OrgTriage has used against your org’s rolling 24-hour allowance. Nothing scans on its own.
- Honest about scope. An area that could not be checked says so rather than scoring clean. Managed-package components are excluded by default and counted when they are.
The full detail is in the privacy policy, including the limited user information the access and operations checks read, and the permissions explainer. Both are written against the code and kept exact.
Use it with judgement
OrgTriage is a diagnostic tool, not an adviser, and it is provided as is. Every finding is a recommendation. A high score is not a statement that your org is secure or correctly configured, and an area that could not be checked says so rather than scoring clean.
Have an experienced Salesforce administrator or developer review any change before it is made, test it outside production, and deploy it the way you deploy everything else. The terms of use say this in full.
Help improve OrgTriage
Mail mike@everythingvirtually.com. A rule that judged your org wrongly is the most useful thing you can send: every rule cites its source, and a bad call is a bug in ours.
See OrgTriage in action
Screenshots use Northwind Trading, the built-in sample org — a fixture, not a customer.
