doDev – Admin & Dev Toolkit for Salesforce
Salesforce dev superpowers for everyone
✅ Free · ✅ No server · ✅ No account · ✅ No connected app · ✅ Nothing installed in your org · ✅ Any org you're logged into
Website · How-to guides · Help · Privacy · Report a bug · Request a feature
Four toolboxes, one Salesforce login
| Tool | What you get |
|---|
| 🔎 | Find | Who has access to a field, object or permission – and why · Who can open a record – and why · Where a field, class or flow is used · Any metadata, one page each |
| ⚖️ | Compare | Profiles and permission sets · Two users – in one org or two · Apex, flows and metadata between orgs · Objects and org settings · Records, field by field |
| 🗂️ | Data | Query without writing SOQL · Start from a list view or a report · Export to Excel, CSV or JSON · Import, update or delete from CSV |
| ⏱️ | Monitor | Scheduled and batch Apex jobs · Failures in the last 7 days · What runs next · Any job by its Id or class |
[!TIP]
Press Ctrl + K to open any object, field, flow, Apex class, profile or permission set – one page each.
📚 How-to guides
All guides, step by step →
⚡ Setup vs. doDev
| The question | In Setup | With doDev |
|---|
| Who can edit this field? | Open every profile and permission set, one by one. | One list: every user, and the profile or permission set that gives it. |
| Who has Export Reports? | Check each profile and permission set. | Every user with it, and where it comes from. |
| Why can this user see this record? | Sharing settings, role hierarchy, teams, the Sharing button… | Every reason for every user, in one table. |
| What's different in production? | Two browser windows and a lot of scrolling. | Side by side: only in A, only in B, changed in both. |
| Can I delete this field? | Hope "Where is this used?" found everything. | Code, flows, formulas, layouts, reports and more – with the line. |
| Show me this data in Excel | Write SOQL, export, reformat. | Pick fields, run, Excel. |
🔒 Safe by design
[!NOTE]
Everything runs in your browser, using the Salesforce login you already have. Nothing is sent anywhere except to your own Salesforce org, and nothing is collected by us. Details: privacy policy.
- It only talks to Salesforce. doDev asks for one permission (
cookies) and access to Salesforce sites only. It cannot read or change any other website, and it adds nothing to the Salesforce pages you open.
- No server, no account, no tracking. Requests go straight from your browser to your own Salesforce org – and only to the org that login belongs to.
- Read-only unless you ask. The only tool that saves data is Data Import: it shows you what will change, and nothing is sent until you click its button.
- Nothing installed in Salesforce. No managed package, connected app or setup change in your org.
- Reviewed by Google. Every version is checked by the Chrome Web Store before it is published.
❓ FAQ
Yes. No account and no paid tier. Install it from the Chrome Web Store and open it from any Salesforce page.
Chrome shows this for extensions from publishers whose account is still new – Google trusts a publisher after a few months of following its policies. It isn't about what doDev does; you can safely choose Continue to install. Standard Chrome settings don't show the warning.
Any org you are logged into in Chrome – production, sandboxes and Developer Edition orgs. Log into two orgs to compare them.
The extension ID is agcjfjpmlmfbdbgfohficnccnknimhbd. What it accesses and how your data is protected are in the privacy policy.
🐞 Bugs and ideas
This repository is the public home of doDev: report bugs, request features and read the privacy policy here. The extension's source code is kept in a separate private repository.
[!WARNING]
Please don't post Salesforce data. Describe the problem and include screenshots without customer names, record data, usernames or org IDs.
doDev is free to use. It is not affiliated with or endorsed by Salesforce, Inc. Salesforce is a trademark of Salesforce, Inc.
