All docs pages (49)
Org Intelligence
Count the Apex classes, active flows, permission sets, users and validation rules in an org, with a rule-based risk grade and up to five recommendations.
Updated 2026-11-09
Org Intelligence gives you a quick count of what is in an org (Apex classes, active flows, permission sets, users, objects, validation rules) and turns a few of those counts into a risk grade and a short list of recommendations. The recommendations come from fixed rules in the extension, not from AI. Open Develop → Org Intelligence.
How to use it
- Pick an org in the org list at the top right. It starts on the org you are connected to; the list shows the orgs the extension has a session for (Select org… if none is chosen).
- Click Scan Org. The button reads Scanning… while the counts load.
- Read the cards, the gauge and the Recommendations list. Click Scan Org again to read fresh counts.
Before the first scan the page shows No snapshot yet.
What you see
Count cards. Each card is one COUNT() query:
- Apex Classes: Apex classes with Status Active.
- Active Flows: flow definitions that have an active version.
- Permission Sets: permission set records with IsCustom = true.
- Active Users: users with IsActive = true.
- Custom Objects: in version 1.1.13, objects Salesforce marks as customizable (EntityDefinition IsCustomizable = true), which includes standard objects you can customize, not only
__cobjects. In the release after 1.1.13 it counts__cobjects only. - Validation Rules: active validation rules.
Score cards. Two scores out of 100, from simple formulas:
- Compliance Score starts at 100 and drops 15 points for each custom permission set that grants Modify All Data.
- Flow Health is 100 with no active flows, then drops 5 points for every 10 active flows, never below 30. It measures how many flows you have, not whether they work.
Cards turn green at 70 or more, amber at 40 to 69, red below 40.
Risk Score gauge. A number from 0 to 100 (higher is worse) and a grade from A to F, worked out from the compliance score, the flow score and the share of custom permission sets that grant Modify All Data. A is 20 or less, F is above 80.
Recommendations. Up to five, each with a priority (P1 to P5) and an impact (high, medium, low). The rules are:
- three or more custom permission sets grant Modify All Data: review them;
- more than 50 active flows: consider consolidating;
- more than 40% of custom permission sets grant Modify All Data: audit them;
- more than 200 active Apex classes: check test coverage;
- more than 100 active validation rules: audit them;
- none of the above and an overall score of 80 or more: "Org health is strong".
What it reads and writes
It runs eight COUNT() queries against the org: ApexClass, FlowDefinition, EntityDefinition and ValidationRule through the Tooling API, and PermissionSet (twice), User and Profile through the REST API. The Profile count is read but not shown.
It changes nothing in the org. The scan is kept only on the open page: leave the page and it is gone, and nothing is saved in your browser.
Limits
- In version 1.1.13, if a count query fails (for example, your user can't read that object), the card shows 0 and no error appears, so a 0 can mean "none" or "not read", and the scores can come out better than they should. In the release after 1.1.13 a failed count shows an error naming what couldn't be counted.
- The trend label under the gauge always reads stable in this version, because no earlier scan is kept to compare against.
- The scores are counts put through fixed formulas. They do not look at code quality, test coverage, flow errors or who has which permission.
- The recommendations have no buttons; they are text only.