# Know how healthy every Salesforce org really is.

> SyncOnAI 360 Org Health scores how well a Salesforce org is built from evidence in its own metadata and source. Health, confidence and coverage are kept as three separate numbers, Apex coverage comes from the org's last test run, and every point can be traced back to what produced it.

Source: https://synconai360.com/features/org-health

## Key facts

- **3**: Separate numbers: health, confidence and coverage
- **20+**: Metadata types read with their full source
- **6h**: Automatic refresh, or on demand at any time
- **75%**: Apex coverage threshold flagged class by class

## Why a single health number can mislead you

Most org health scores are one number from a scan of whatever the tool happened to reach. When part of the org was hidden or could not be read, the number goes up instead of down, and the people relying on it never find out.

- **Hidden parts count as healthy.** Managed package code that Salesforce hides cannot be analysed. A score that ignores it treats the unknown as fine, so the orgs with the most package code look healthiest.
- **Coverage that says 0% when nothing ran.** An org with no recorded Apex test run is not an org with no coverage. Reporting it as 0% sends teams chasing a problem that is really a missing test run.
- **No trail from score to cause.** When a score drops, nobody can say which change caused it. Without evidence behind each point, the score starts arguments rather than ending them.
- **Snapshots that go stale.** A health check run once a year for an audit tells you nothing about the org you are changing today. Health needs to move as the org moves.

## Why does SyncOnAI 360 separate health, confidence and coverage?

Health says how well the org is built, from what could be measured. Confidence says how much of the org could be measured at all. Coverage says how much of the org's metadata has its full source available. Keeping them apart means an org Salesforce partly hides from view shows lower confidence, not a better health score.

Managed package code that its publisher hides is shown as hidden, never as missing and never as healthy. The score maps to a grade with a plain sentence beside it, from A, excellent and enterprise ready, to F, critical and needing immediate action.

- Health from what could be measured, never from what could not
- Confidence falls when package code is hidden; health does not rise
- Coverage shows how much metadata has full source
- A grade from A to F with a sentence anyone can read

## What does the health check actually read from the org?

Each sync reads objects, fields, record types, layouts and Lightning pages; Apex classes and triggers with their full source; every file of each Lightning Web Component; Flows, validation rules, permission sets and profiles; and email templates, value sets, approval processes, queues, reports, dashboards and sharing rules. It also reads Apex test coverage from the org's last test run.

It does not read your records. Accounts, contacts, cases and opportunities stay in Salesforce. The first sync of a large org can take several minutes; later syncs fetch only what changed, every org refreshes automatically every six hours, and you can refresh at any time.

- Full source for Apex, Flows and Lightning Web Components
- Configuration only, never CRM records
- Incremental syncs after the first, every six hours
- Progress by stage and by metadata type while it runs

## How is Apex test coverage measured?

Coverage comes from the org's own last Apex test run: the org-wide figure and every class below 75%, the bar Salesforce sets for production deploys. Managed package classes are left out, because they are not yours to test.

If the org has no test run recorded, the page says Not recorded rather than showing 0%. Run your tests in Salesforce, refresh, and the figure updates. That one distinction stops teams from treating a missing run as a coverage crisis.

- Org-wide coverage and every class under the threshold
- Managed package classes excluded
- Not recorded when there is no test run, never a false 0%

## Where do you go from the health score?

Everything about one org lives inside it, as lenses across the top of its health page. Lineage shows what uses a component and what it uses. Changes shows what moved and whether it came through SyncOnAI 360 or somewhere else. Technical debt ranks duplicates, unused metadata and legacy automation. The audit runs 55 checks with priced findings and a letter grade. Architecture describes how the org is built: automation style, layers, naming and sharing.

Across orgs, the Command Center shows every connected org with its score, so platform owners see where attention is needed. And any health report can be shared as a read-only link with a stakeholder or partner, then withdrawn whenever you choose.

- Lineage, Changes, Technical debt, Audit, Canvas and Architecture lenses
- Every org's score together in the Command Center
- Read-only report links you can withdraw at any time

## How the health check works

1. **Connect.** Authorise a sandbox or production org with Salesforce OAuth. Access is stored encrypted, under a key held in Google Cloud KMS.
2. **Sync.** The first sync reads the org's configuration and source. Close the tab if you like; it keeps going.
3. **Score.** Health, confidence and coverage are calculated, with Apex coverage from the last test run.
4. **Investigate.** Open any lens to see lineage, recent changes, technical debt or the full audit.
5. **Stay current.** Every org refreshes every six hours, and deploys from SyncOnAI 360 are read back straight away.

## Org health, with and without SyncOnAI 360

| Without | With SyncOnAI 360 |
|---|---|
| One number from whatever the scan reached | Health, confidence and coverage reported separately |
| Hidden package code treated as healthy | Hidden code lowers confidence, never inflates health |
| 0% coverage when no tests were run | Not recorded, until the org's tests actually run |
| A yearly snapshot | A refresh every six hours and on demand |
| A score nobody can explain | Every point traced to the evidence that produced it |

## Who uses org health

- **Salesforce admins.** See each org's grade, its weakest areas and what changed since the last review every time the org refreshes, with the evidence behind every score.
- **Consultancies.** Give every client org the same graded health view, compare them in one portfolio, and share a read-only report that proves progress between reviews.
- **Platform owners.** Watch health across the estate in the Command Center and see which orgs need attention first, without waiting for a quarterly review.
- **Salesforce architects.** Read the section scores alongside the findings that drive them, so design conversations start from the org's measured state.

## Frequently asked questions

### What is a Salesforce org health check?

A Salesforce org health check measures how well an org is built: its automation, code, configuration and the risks they carry. SyncOnAI 360 scores health from the org's own metadata and source, keeps confidence and coverage separate, and links every point to the evidence behind it.

### How is the health score different from the audit?

The health score summarises how well the org is built and how much of it could be measured. The audit is the detailed review behind it: 55 checks, each finding with evidence, an effort band, an estimated cost to fix and a letter grade.

### Does the health check read our customer data?

No. It reads configuration and code: objects, fields, automation, Apex, components and their relationships. Records such as accounts, contacts and cases stay in Salesforce.

### How long does the first health check take?

The first sync of a large org can take several minutes, and it continues in the background if you close the tab. Later syncs only fetch what changed and are much faster.

### Why is our confidence score lower than our health score?

Confidence reflects how much of the org could be measured. Managed package code hidden by its publisher, or a missing Apex test run, lowers confidence without changing health, so you can see exactly where the score is less certain.

### Why does Apex coverage say Not recorded?

Because the org has no Apex test run recorded. Run your tests in Salesforce, refresh the org in SyncOnAI 360 and the coverage figure will appear.

### How often is the score updated?

Every connected org refreshes automatically every six hours, and you can refresh at any time. Components deployed through SyncOnAI 360 are read back immediately after a successful deploy.

### Can we share a health report with leadership or a partner?

Yes. Create a read-only link to the health report and send it to anyone who needs it. Withdraw it whenever you want; the record that it existed is kept.

### Can we check sandboxes as well as production?

Yes. Connect sandboxes and production orgs alike. A sandbox linked to its production org does not count against your plan.

### Which Salesforce metadata does the health check read?

Objects, fields, record types, layouts and Lightning pages; Apex classes and triggers with full source; every Lightning Web Component file; Flows, validation rules, permission sets and profiles; and email templates, value sets, approval processes, queues, reports, dashboards and sharing rules, plus Apex coverage from the last test run.

### Does the health check slow our org down?

The scoring and the audit work from the copy SyncOnAI 360 keeps after each sync rather than querying the org again. After the first sync, later syncs only fetch what changed.

### Is the health check included on the free plan?

Every plan includes every feature. Free covers one user and one production org with its sandboxes, on your own Anthropic or OpenAI key, with no credit card and no time limit. Paid plans include AI and cover more people and production orgs.