Support

Marco — Where Used for Salesforce

Fastest way to get help: email marco@creedysolutions.com. Include your Chrome version and, if it's a bug, what you clicked and what you expected — a screenshot of the side panel helps enormously. Real human, usually within a day.

Before anything else

Marco needs the API Enabled permission on your Salesforce profile — the same permission Salesforce Inspector and Workbench need. If those tools work for you, Marco will too.
After an extension update, Chrome sometimes needs a nudge: visit chrome://extensions, hit the ↻ on Marco's card, and reload your Salesforce tab.

Common questions

The panel says "No Salesforce session"

Open (or refresh) a tab where you're logged into the org, then click Marco's icon again. Marco reuses your existing login — it never asks for credentials.

The panel opens but stays empty

Marco activates on Salesforce Setup pages and record pages. Navigate to a field, flow, or Apex class in Setup — or use the search bar at the top of the panel to jump straight to any component by name.

Where do I enter my PRO license key?

Click the PRO chip in the panel header, paste your key (MARCO-XXXXX-XXXXX-XXXXX), and hit Activate. The three PRO features — Impact report, the Access tab, and Explore in 3D — unlock immediately. One key works on up to 8 browsers.

"This key has hit its install limit"

You can remove a license from a browser you no longer use (PRO chip → Remove from this browser), or just email us — we'll sort it out.

Does my org's data leave my browser?

No. All metadata queries run from your browser directly to your own Salesforce org, and caches live on your device. The only exception is PRO activation, which sends your license key (and nothing else) to Marco's license server. Full details in the privacy policy.

The 3D Universe looks tangled on my org

Open ✛ Layout in the Universe's top bar and drag the Spacing and Grouping sliders — every org's shape is different, and the settings are remembered per org. The Galaxies button can hide packages you don't care about.

Something in my org isn't showing as a dependency

Marco builds on Salesforce's dependency API, which is beta and has known blind spots (reports and email templates, notably). Marco supplements it with its own scans for page layouts, validation rules, flows, and compact layouts — but if you've found a miss, we genuinely want to hear about it: marco@creedysolutions.com.

Feature requests

Send them. The impact-sorted feeding queue, the layout sliders, and the cloud galaxies in the 3D view all started as user asks.