73 investigations · Six families · No installation
Start with a question.
Follow the evidence.
Choose an investigation, run its queries in an approved Salesforce tool, and bring back JSON or CSV results. Analyse and compare exports entirely in this browser tab.
No Salesforce connection, account or data upload. Samples are fictional. Some investigations require Tooling API or specific Salesforce features.
New here? Try a five-minute walkthrough →
Looking into a user’s field access? Start with the dedicated checker ↗Follow a workflow
Choose the checks relevant to your question. Each investigation keeps its own parameters and exports; start a pack to save check summaries and download one combined report. No queries run automatically.
No investigation matches. Try an object, a question or a family.
Set the context
Labels describe your exports; they do not verify org identity. Use equivalent filters and time windows for comparison. Parameter values and imported data never enter the page URL.
Evidence summary
Compare the exports
Comparisons describe selected exported values, not complete org parity. Missing or uncompleted steps cannot be compared.
Report a problem with this investigation · Request a probe. GitHub submissions are public. Use fictional examples; no investigation data is attached.
Follow-up checks
Related investigations
Reports include labels, parameters, observations and your notes. They exclude raw result rows. Review before sharing.
How to run queries and prepare exports
Use a query tool approved by your organisation. Salesforce Developer Console has a Query Editor; set “Use Tooling API” to match the badge on each step. If your tool cannot export JSON or CSV, ask an administrator to provide the result files. Keep all selected columns and export every result page.
Run each step with the displayed query. Accepting a result unlocks dependent steps. Replacing a prior result clears all later imports on that side. An unavailable step blocks its dependants but does not prevent independent checks.
Queries can have result limits. Reaching a limit is flagged and does not establish that all matching records are present. Exports cannot independently prove the query was run, which org it came from, or whether it is current.
Privacy and analysis limits
Files and pasted results are processed locally in this tab, not uploaded or stored in browser storage. Clearing or reloading discards the investigation. Downloaded reports remain on your device. Standard hosting logs can record page visits, but not your pasted exports.
Source and configuration columns marked for hashing are compared using SHA-256 fingerprints of exact exported content. This does not assess semantics. CSV has no type metadata: known boolean and numeric columns are normalised, but other CSV fields stay text. Prefer the same export format on both sides.
The observations describe supplied evidence. Empty results, inactive flags and changed metadata do not by themselves establish absence, effective access, execution or root cause.