Marco. Polo. Found. Click any component in Setup and see everywhere it's used — flows, Apex, reports, layouts, validation rules.
Users
14
−3 in 30 days
Rating
5.0 / 5
unchanged in 30 days
Ratings
4
0 in 30 days
Store rank
#170K
#142K among extensions
Version
1.0.8
updated 25 Aug 2026
Users
monthly, 2 months
Latest, 17 Oct 2026:14 usersMove the mouse over the chart for any month
Ratings count
monthly, 2 months
Latest, 17 Oct 2026:4 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Marco — Where Used for Salesforce
Marco. Polo. Found.
Marco answers the question every Salesforce admin, architect, and developer
asks a dozen times a day: "if I change this, what breaks?"
Click any component in Setup — a field, flow, Apex class, validation rule,
layout, LWC — and Marco's side panel shows every dependency, both directions,
grouped and clickable, with Setup links straight into Lightning.
WHAT MARCO DOES
• Interactive dependency graph — uses on the left, used-by on the right,
click any node to re-walk from there, breadcrumb trail for backtracking
• Explore in 3D — your entire org schema as a navigable universe: every
object is a star, every relationship a line, each managed package its own
galaxy — and standard objects group into cloud galaxies too (Sales,
Service, Field Service, Health, Public Sector, and more, adapting to
whatever your org runs). Warp-search any object, show/hide galaxies or
individual objects, tune the map with spacing and grouping sliders, and
focus any star for an Object Manager-style detail card (fields,
validation rules, layouts, triggers — every row deep-links into Setup)
• API-name overlay on record pages — a toggle drops the API name under every
field label; click a custom field's chip to inspect it in Marco
• Standard-field where-used — Marco's own metadata scan (page layouts,
validation rules, active flows) covers what MetadataComponentDependency
can't see
• Flow read/write differentiator — flows are labeled with whether they READ
or WRITE the focused field, resolved through variables and $Record
• Access tab — profiles and permission sets that grant read/edit,
with user-count per perm set
• Search — find any component by name via Tooling SOQL, without navigating
Setup first (works from any tab in your org)
• Impact report — a printable, shareable document you can attach to a
change-request ticket, generated in one click
• Export the graph as a Mermaid diagram or PNG image
• Feed Your Admin — keep your org documented and watch your pixel admin
grow from egg to superhero: a documentation-coverage score, an
impact-sorted queue of undocumented components, and one-click description
editing (sandbox and Developer Edition orgs only — production stays
read-only, respecting your deployment pipeline)
• Guided first-run tours in the panel and the Universe — and a ? button to
replay them anytime
PRIVACY BY DESIGN
Marco reuses your existing Salesforce session — the same pattern Salesforce
Inspector uses. Your org's metadata never leaves your browser. There are no
Marco servers, no telemetry, and no accounts to create. The Chrome cookies
permission is used only to read your Salesforce session cookie, for the
origin of the tab you're currently on. Nothing else.
REQUIRES
The "API Enabled" user permission on your Salesforce profile — the same
permission Salesforce Inspector and Workbench need. If you can query Tooling
API from Workbench, Marco works.
FREE AND PRO
Everything above is free except three PRO features — Impact report, the
Access tab, and Explore in 3D — which unlock with a one-time license key
(no subscription, no account). Activation sends only your key and a random
install id to Marco's license server; your org's metadata never leaves your
browser, licensed or not. Feedback: marco@creedysolutions.com
What's new (1.0.3 → 1.0.7)
1.0.7 — Feed Your Admin grew manners
The big change: Feed Your Admin is now opt-in. Fresh installs get a clean, complete where-used panel with no pixel admin in sight. When you're curious, the tilted "Feed your admin!" text in the header opens a walkthrough that covers what it does, what it can write (a component's description text — nothing else, ever), where it works (sandboxes and Developer Edition orgs; production is always read-only), and how to use it. One confirm button turns it on; the same spot turns it off. Nothing is scanned and nothing appears until you say so.
Also in 1.0.7:
Warping into an object in the 3D Universe now hides the galaxy labels that have no connection to what you're looking at — no more names floating over ghosted galaxies.
The little admin reliably shows up on his perch the moment you opt in (he was occasionally invisible until you switched components).
1.0.6 — refunds bite faster
Licenses now re-check the server every 24 hours instead of every 3 days, so a refunded key locks within a day. The 14-day offline grace is unchanged — Marco still works on a plane.
1.0.5 — checkout, for real
The Get a key link now lands on the live checkout. Buying a PRO key, getting it by email, activating it, and — should you ever want it — the refund path have all been tested end to end with a real card. My card, twice. You're welcome.
1.0.3 — Marco went dark
The panel got a full dark theme — blue-black, keyed to the Universe, dark by default. The ◐ button in the header cycles dark, light, or follow-system. The Impact report stays white on purpose: it's paper. A pile of small fixes rode along: the theme toast pops next to the button you clicked instead of the far bottom, and the feeding queue's buttons are readable in the dark.
(1.0.2 brought trackpad navigation to the Universe — two-finger swipe to orbit, pinch to zoom — and 1.0.1 introduced the 7-day free PRO trial: no card, no email, no account.)