ORGanizer for Salesforce

Install it

ORGanizer exists to take the repetitive work out of a Salesforce admin's or developer's day:

• logging in to a long list of ORGs;
• telling apart the ORGs you already have open;
• reaching a frequently used setup page in one keystroke;
• running a query or a piece of Apex without opening the Developer Console;
• checking the health of an ORG, and who has access to what.

The same build runs on Chrome, Firefox and Microsoft Edge — and on any other browser that installs from those stores, Opera and the other Chromium-based ones included. Pick yours:

Chrome Chrome Web Store Firefox Mozilla Add-ons Edge Microsoft Add-ons

Opening the popup

Once installed, click the new icon in the browser toolbar:

Or use the keyboard: CTRL + SHIFT + K (CMD + SHIFT + K on macOS).

The browser-level shortcut can conflict with another extension. To change it, right-click the extension icon and choose Manage Extensions:

Scroll to the bottom of the page and open Keyboard shortcuts:

… then type the combination you prefer:

First run: granting access to your ORGs

Logins

The Logins tab lists the Salesforce users you have stored (logins here means Salesforce users, not ORGs). Open it with CTRL + SHIFT + A — see the Options page to change any shortcut.

From this panel you can:

• reorder groups by dragging the group panels up and down;
• reorder logins inside a group by dragging them;
• search with the quick search box (CTRL + F);
• create, edit and delete a login;
• star a login to keep it at the top.

Creating and editing a login

Use the New button, or the pencil next to an existing login. CTRL + SHIFT + C opens the creation panel directly.

Opening a login

• New tab
• New tab with Developer Console
• New window
• Incognito / private window (has to be enabled for the extension first)
• Show password and security token — for signing in from an external client

Clicking the username copies it to the clipboard.

To allow incognito mode, open your browser's extensions page (chrome://extensions, edge://extensions or about:addons) and enable it for ORGanizer:

To delete a login, open it with the pencil and use the Delete button:

Save as stores the login currently being edited as a new one.

ORGs

An ORG configuration gives one Salesforce organization a label and a colour. Every browser tab logged into that ORG then carries that title and a matching favicon — which is what stops you from running a data fix in production because it looked like the sandbox.

In the popup: the ORGs you are logged into

Open it with CTRL + SHIFT + O. Every ORG with a live session in the browser is listed, with six actions:

The pencil next to a live ORG edits just its label and colour, in a modal. The ORG Id is shown read-only, with an icon that takes you to the full editor in the Options page; a Configured ORGs button at the bottom of the tab does the same.

In the Options page: every ORG you configured

Options → ORGs holds the real list. Every field is editable whether or not the ORG has a live session, so you can prepare a configuration before ever logging in.

The list also gives you a filter box, a checkbox per row and a header checkbox, so a batch of ORGs can be deleted in one confirmation.

All ORG configurations are synced. There is no way to keep one local only. After saving, an open tab can take up to ten seconds to pick up the new icon and title.

The pencil on a row opens the editor, where the four fields above are set:

Domain permissions

Permissions granted at install time

Plus a small set of hosts, which are ORGanizer's own backend — never Salesforce:

• https://api.organizer.solutions/* — licence validation and promo codes;
• https://organizer.solutions/* — this site, for the in-popup messages and the change log.

Salesforce domains: optional, and per ORG

Salesforce domains are declared as optional host permissions. The declaration is a broad wildcard, but that is only the ceiling of what ORGanizer may ever ask for — it is never requested as such. What is actually requested is the specific set of origins belonging to the ORG you just opened. For acme.my.salesforce.com, that is:

https://acme.my.salesforce.com/*
https://acme.lightning.force.com/*
https://acme.vf.force.com/*
https://acme.file.force.com/*
https://acme.my.salesforce-setup.com/*

Sandboxes, developer and scratch ORGs get the same set with their own partition segment (.sandbox., .develop., .scratch.). All five are requested in a single browser prompt, because each request needs its own click.

login.salesforce.com, test.salesforce.com and welcome.salesforce.com — the last one serves the email-based login flow — are not My Domains, so they are separate origins. The popup offers to pre-authorise them the first time you use it — without them a stored login cannot be opened until its ORG's own domain has been granted, which makes for a confusing first run. You can decline, and tick don't ask again.

api.status.salesforce.com is optional too, and requested only when you open the Health Monitor, which reads instance status from it.

Reviewing and revoking

Options → Permissions lists everything you granted, grouped by My Domain. Each group can be revoked on its own, and you can also grant a domain manually before visiting it. Revoking takes effect immediately: the content scripts are unregistered from those origins.

For the deeper security picture — threat model, cryptography, backend — see the Security Statement and the Privacy Policy.

Encryption

ORGanizer stores Salesforce passwords and security tokens. Encryption is what stands between those and anyone with access to your browser profile. Turn it on from Options → Encryption and pick a master password.

The consequence of that last row is the one you will notice: the derived key never leaves the background worker and is never written anywhere. When the browser closes, the extension reloads or the worker goes idle, the key is gone and ORGanizer asks for your master password again the next time it needs to decrypt something. Every password and token is encrypted individually, so one value can be revealed without unlocking the rest.

Migrating an existing vault

If you were already using encryption, the popup shows a banner pointing at a guided migration page. It re-encrypts your stored credentials with the new scheme after you enter your existing password. On a second device that syncs the migrated data, ORGanizer detects the new format and migrates the local copy automatically once you unlock it.

Mixed states are handled: a device still running an older build can keep working while another has already migrated, and nothing is overwritten in a way that would strand the other device.

Quick Links

Quick Links is a command palette for Salesforce. Open it with CTRL + SHIFT + SPACE on any Salesforce page, or from the ORGanizer button:

Type to search. Pressing ENTER without picking anything opens the first suggestion. Type @ to list every command:

The @ command character is configurable (see the Options page); pick a non-alphanumeric character so it cannot collide with what you are searching for. The order of the commands is configurable too.

Your own links

The two are told apart by a badge everywhere they appear: in the palette and in the Options list. A link takes a label, a URL or relative path, and its scope. The list has a filter box, a “global only / ORG only” filter, and bulk delete.

Adding one on the fly still works: the @add command inside the palette creates a link from the page you are on.

The pencil on a row opens the link editor, where the label, the path and the ORGs it is offered on are set:

Commands

@links — standard setup and custom page links

Every standard setup link (Classic and Lightning, depending on the ORG) plus your custom pages.

@history — temporary links

A scratch list for the thing you are working on right now, useful when you keep going back and forth between the same handful of pages. Add an entry with @add and an optional description.

History items are stored locally only, never synced, and capped at 20 per ORG — the oldest drops off as you add new ones.

@objects — object setup pages

Jump straight to the setup page of any standard or custom object.

/ — a relative path

Start the search with / to open any path on the current ORG directly.

@search — global search

Runs Salesforce global search with whatever you typed.

Metadata search

Search these component types directly:

• Apex Classes @classes
• Apex Triggers @triggers
• Visualforce Pages @pages
• Visualforce Components @components
• Custom Labels @labels
• Static Resources @static resources
• Profiles @profiles
• Workflow Rules @workflow rules
• Validation Rules @validation rules

Tab actions

With the focus on a Salesforce tab, these open the corresponding page in a new tab. All of them are configurable in the Options page.

On macOS, CMD replaces CTRL.

ORGanizer button

The ORGanizer button appears on every Salesforce page you granted access to. Expand it to reach the tools without a shortcut: Quick Links, Quick Console, Health Monitor, Access Lens, Profiles Chamber and the Options page.

The whole button can be turned off from the Options page if you would rather work with the keyboard only.

Quick Login

Quick Login attaches ORGanizer to the Salesforce login pages, so you can sign in with a stored login without going back to the popup.

It hooks the username field and suggests the stored logins that match what you type.

If you sign in with a username and password ORGanizer does not know, it offers to store them.

The email-based login flow new in 1.0

Salesforce is moving production and sandbox sign-in to an email-first experience served by welcome.salesforce.com: you give an email address, pick the environment out of a switcher, and type the password on a third screen. The classic login page has a Log In with Email button that leads there. Quick Login follows that flow from end to end.

A login is offered here only if it carries a Login email (the login's settings). That flow asks for the email of the Salesforce account, which is not the ORG username, and ORGanizer does not guess one from the other: a login without it stays on the classic page. The picker says as much when none of your logins has one.

It also needs the welcome.salesforce.com domain, which the popup offers to grant alongside login and test the first time you use it, and which you can grant at any point in Options → Permissions.

Enable or disable the feature in the Options page — one switch covers both the classic page and the email-based flow.

Enhanced Formula

Enhanced Formula replaces the plain Salesforce formula textarea with a real editor — syntax highlighting, indentation and autocomplete — on custom fields, validation rules and workflow conditions.

• CTRL + I re-indents the formula.
• CTRL + SPACE autocompletes functions and fields.
• The editor can be resized from its bottom-right corner; the tab size is set in the Options page.

Enable or disable the feature in the Options page.

Hidden features

A handful of small improvements that ORGanizer injects into Salesforce setup pages without you having to ask. They are marked with the ORGanizer style, so you can always tell what is Salesforce and what is not.

Apex coverage on the class and trigger pages

The code coverage percentage, shown where Salesforce does not show it.

Whitelist all IPs

A one-click plugin on the Network Access setup page — useful on a scratch or dev ORG.

Select-all checkboxes

On the last step of the custom lookup wizard:

On the field-level security editor of an object:

And on record type assignment and FLS in the advanced profile view:

Change set list helpers

When the Change Set Helper is not in open mode, ORGanizer still adds a quick filter box, an expand the component list link and an Add to Change Set and add again button:

Quick Console

The Quick Console is a set of plugins that open over the Salesforce page you are on. Open it with CTRL + SHIFT + V or from the ORGanizer button:

Jump straight to a plugin with CTRL + SHIFT + [index]. The index of each plugin is shown on the Plugins tab:

Some plugins also have a quick action: CTRL + ALT + [index] runs the plugin's main action without opening the console at all. This is available for SObject fields (index 4), Replace API names (index 6) and Salesforce ID converter (index 7). Every shortcut can be changed in the Options page.

In its own tab

Two things behave differently in the dedicated tab, by design: there is no close button (it is a tab — close the tab), and Replace API names is disabled, because it rewrites a Salesforce page and there is no Salesforce page underneath.

Home

The landing plugin: everything about the ORG you are in.

• Organization Id
• Server domain
• Session Id
• ORG info (REST API)
• User info (SOAP API)
• Apex test coverage

Quick Query

SOQL, SOSL and Tooling API queries, including parent references and subqueries:

• Results are sortable and searchable locally, and downloadable as JSON.
• The last 50 queries per ORG are kept in a history you can pick from.
• CTRL + SPACE autocompletes SOQL keywords, custom fields, relationships and objects. The * wildcard expands to all, all custom or all standard fields.
• The Tooling API button switches the query to the Tooling endpoint.
• Typing a plain search term runs a SOSL search, with results grouped by object.
• The editor resizes from its bottom-right corner.

Queries worth keeping go into Very Important Queries (V.I.Q.), named and shared across ORGs.

Execute Anonymous

Run anonymous Apex without opening the Developer Console:

• Pick the debug level per category; Download log saves the generated log.
• The last 50 scripts per ORG are kept.
• CTRL + I re-indents the code.
• The editor resizes from its bottom-right corner.

Scripts worth keeping go into Very Important Scripts (V.I.S.), same as V.I.Q.:

SObject fields

Query every field of one record. Type a Salesforce Id, or let ORGanizer take it from the current page URL (it also picks up an id query-string parameter):

Every updatable field is editable inline, with a rollback button, and saved individually:

The quick action CTRL + ALT + 4 opens the plugin and runs the query straight away.

Quick ORG Describe

Describe the ORG's objects:

… and every field of each one:

Replace API names

Swap every custom field label on the page for its API name. Works on the Classic and Lightning standard layouts, the field set editor and the page layout editor:

Salesforce ID converter

Convert 15-character Salesforce Ids to their 18-character form, in bulk:

The quick action CTRL + ALT + 7 turns it into a URL clipper: the Id of the record you are looking at goes straight to the clipboard.

Login As…

Log in as another internal user. Search by name or username, then open the user's detail page, log in on a new tab, or log in in a private window (if ORGanizer is allowed there):

Field Usage new in 1.0

The question every long-lived ORG ends up asking: which of these fields is anybody actually filling in? Pick an object and Field Usage goes through its fields one by one, counting how many records carry a value and what share of the object that is — the quickest way to tell a field that is doing work from one that has been empty since the day it was created, before a clean-up, a migration or a page layout review:

Health Monitor new in 1.0

The Health Monitor is an ORG health dashboard: seventeen sections of analysis across nine tabs, rolled up into a single Health Score, plus a live limits monitor and two export formats. Open it from the ORGanizer button or from the Health Monitor action next to a live ORG in the popup.

What it looks at

The Health Score

A 0–100 weighted average of eleven sub-scores, grouped exactly like the tab bar so a low overall number leads you straight to the section responsible. Sections that cannot be scored fairly are deliberately left out of the average rather than given a made-up value.

Every threshold the dashboard judges by — the usage bands, the score bands, the API version lag, the coverage gates, the automation penalties — lives in one registry, and the Methodology page renders that registry as a readable document: each number with the reasoning behind it. It is a genuinely static page: no session, no API call, safe to read before you ever run an analysis.

Live Monitor

Polls the ORG's limits endpoint on an interval and charts the result, so you can watch API consumption or async capacity while a data load or a deployment runs. Pick the metric, navigate the snapshots, hover the chart for exact values. It warns you before you close the tab while it holds data.

Exporting a report

• Print Report — a self-contained printable page with every section, its explanation, KPIs, charts and tables.
• Export ZIP — the same report as report.html, plus metadata.json, the methodology as Markdown, and the raw API responses per section under raw/.
• Most sections also export their own table as CSV.

Neither export queries the ORG: they describe what is already on screen, and both refuse to run before the first analysis rather than producing empty sections.

Access Lens new in 1.0

Access Lens answers two questions Salesforce makes surprisingly hard: what can this user actually do? and where does that access come from? Open it from the ORGanizer button or from the Access Lens action next to a live ORG in the popup.

Effective access

Search for any active user and get their combined effective permissions, OR-merged across their profile, permission sets and permission set groups:

• Object permissions — Read, Create, Edit, Delete, View All, Modify All, per object
• Field permissions — Read and Edit, per field
• Entity access — Apex classes, Visualforce pages, connected apps and the other setup entities
• System permissions — every system permission the ORG defines, discovered from the object describe rather than a hardcoded list, so a new Salesforce release does not leave a gap

Every row shows which assignments grant it, tracked per individual permission rather than per object — so you can see that Read comes from the profile while Delete comes from one specific permission set. Sources are colour-coded by type (profile, permission set, permission set group, muted) and the assignment tags above the table are clickable filters: click one to see only what it grants.

Elevated access

Security-sensitive permissions are highlighted automatically — an amber row, a shield badge and an Elevated filter chip. That covers ModifyAllData, ViewAllData, ManageUsers, AuthorApex, CustomizeApplication, ManageProfilesPermissionsets, ManageSandboxes, ResetPasswords, AssignPermissionSets and around two dozen more, plus View All and Modify All at the object level.

Compare mode

Pick any two permission sets, profiles or permission set groups and get a side-by-side diff: Added, Removed, Unchanged, or just the Diff. Scope (objects, fields, entities, system) and status filter independently, which is what makes a real comparison of two large profiles readable.

Export

Results export to CSV or JSON — for an access review, a compliance pack, or a diff you want to run somewhere else.

Change Set Helper

Salesforce gives outbound change sets almost no API surface, so the tedious parts — finding components, removing them one by one, rebuilding the same set of components for every release — stay manual. The Change Set Helper automates what can be automated from the page itself.

Working with a change set

Open an outbound change set. The helper attaches itself to the page:

Download components retrieves a ZIP of the components in the package. It works when there is only one outbound component with a given name.

Templates

A template is a reusable model of a change set: something you can import into another change set, browse, refine, or use to remove components from the current one.

Create Template walks the component table page by page, collecting every definition — on a change set with hundreds of components this takes a while. When it is done, name it and hit Save Template.

The Metadata Templates picklist lists everything you saved:

Because it is not obvious whether a component can be added, Compare Template walks the current change set looking for matches with the selected template. If part of the template is already there, you are asked to create a “subset” template holding only what is missing — which is what can be imported safely.

Remove Template deletes one from the list; Extract Template CSV downloads the current template as CSV (useful to attach to a bug report).

Selecting a template shows its components:

From here you can filter, and use Remove from Template to prune it, or Remove from Change Set to take a component out of the change set itself — which is close to instant in the current version.

On the Add page

Add Template inserts the current template. If everything can be inserted, the components are added and you are taken back to the change set. If some cannot (Person Account record types, untested types), a CSV of the leftovers downloads automatically so you know exactly what to add by hand — and you then press Add to Change Set yourself.

Since V2 you can also search across component types without leaving the page:

In Add Mode you can drop selected components on the fly, then push Add to changeset once for the whole batch. Remove Mode removes components quickly, searching by component type.

When the helper is not in open mode, it still adds three things to the standard page — see Hidden features: a quick filter, an expand the list link (up to the maximum Salesforce allows) and an Add to Change Set and add again button.

Remember what this is: not a change set manager — there is no API for that — but a helper that automates the parts you would otherwise do by hand.

Profiles Chamber

Profiles Chamber is for mass profile management. It opens as its own page, using the session of the ORG you launched it from — reach it from the ORGanizer button.

The setting it manages today is Login Hours, across as many profiles as you like at once:

Double-click a day cell to change a single day on a single profile:

Changed cells are marked in red until you apply them; Undo resets the profile:

Select several profiles and days to apply the same login hours to all of them:

The template section lets you:

• load a saved template (templates are per ORG);
• remove one from local storage;
• save over the current template;
• save the current configuration as a new, named template.

You can restrict a template to specific profiles and days before saving it.

Field History Helper 2.0 rebuilt in 1.0

Salesforce lets you track a limited number of fields per object, and then tells you nothing about which ones are worth tracking. The Field History Helper attaches to Object Manager → <Object> → Set History Tracking and answers the three questions you actually have in front of those checkboxes:

• Is this field used at all? — on how many records it is filled in, and how many different values it holds;
• Does it actually change? — how many history entries it recorded in the period you pick, by how many people, and when the last one was;
• Is there room for another one? — how much of the per-object tracking limit is already spent.

The panel

The helper adds a page block of its own above the tracking page, so the native Save and Cancel flow is untouched. Nothing is queried when the page loads: the slot meter renders immediately and follows the checkboxes live, and the ORG is asked only when you press Analyze fields. Refresh analysis runs it again without reloading the page.

• Tracking slots — how many fields are ticked against the per-object limit, and how many slots are left. No API this extension can reach reports the real limit, so the default of 20 is an assumption: the meter says so in its tooltip, and raises itself if the object turns out to allow more.
• Search matches the label and the API name.
• Filters — tracked, not tracked, no changes in the period, coverage below 25%, analysis unavailable. Search and filters hide fields on the Salesforce page itself, without shifting the columns around them.
• A sortable results table inside the panel, which never reorders the Salesforce page: filter to the tracked fields, sort by changes ascending and read the quiet ones off the top of the table, while the configuration page you are about to save stays exactly as it was.
• History period — the last 30, 90 or 365 days.

Every field on the page also carries its API name and its own metrics next to the checkbox. The period, the filter and the sort you leave the panel in are remembered for the next time.

What it measures

An untracked field that still has history rows is shown with its count and a not tracked now chip — a fact read off the history table, not a guess about what happened before.

What changed in 2.0

The previous helper downloaded the most recent 1,000 records of the object and derived two percentages from them, and it never looked at the field history at all — so it could not answer the one question that page is about. 2.0 asks the ORG for exact numbers instead, and downloads no record:

Reading the numbers

The helper reports, it does not advise: it will not tell you to stop tracking a field. The numbers are facts about the ORG, the decision is yours. Colour carries a meaning only on the slot meter, where the text says the same thing anyway.

• Zero changes reads as no history changes found in the selected period, and it means exactly that: the window you picked, your ORG's history retention, the date tracking was switched on and your own permissions all feed that number.
• An object with no records shows an em dash rather than 0% — nothing to measure is not the same as everything empty.
• A field your permissions hide, or one the ORG cannot aggregate (compound, encrypted, and the like), is reported as analysis unavailable with the reason, instead of being counted as zero. The rest of the analysis carries on around it.
• An object without a history table gets no change activity, while coverage and distinct values are still reported.
• Person Account fields (__pc) are deliberately left out: whether each of them can be aggregated on every ORG has never been verified, and counting them as zero would be worse than saying nothing.

Enable or disable the feature in the Options page.

Notifications

The popup carries a bell for messages from the extension author — release notes, surveys, the occasional promotion. A dot on the bell means there is something you have not read; opening the panel clears it.

Options page

The Options page is where everything is configured. Reach it from your browser's extension settings, from the Options button in the popup header, or from the ORGanizer button on any Salesforce page.

Features

Turn the content features on and off, in two groups.

Shortcuts

Every in-page shortcut is rebindable here: the popup tabs, the tab actions, Quick Links, the Quick Console and each of its plugins, the plugin quick actions, and the autocomplete key. The browser-level shortcut that opens the popup is set in the browser, not here.

ORGs and Quick Links

Permissions

The Salesforce domains you have granted, grouped by My Domain, each revocable on its own — plus a way to grant one before you first visit it. See Domain permissions.

Encryption

Turn encryption on or off and change your master password. The scheme was rebuilt in 1.0 — see Encryption for what it does and how to migrate an existing vault.

Sync and local quota

Import / Export

Export everything — logins (synced or not), ORG configurations, quick links, V.I.Q.s and V.I.S.s — and import it back somewhere else. A login carries its Login email and Description through the file as well.

The file looks like this:

{
  "accounts": [
    {
      "g":  "Group name",
      "n":  "Login label",
      "u":  "[email protected]",
      "p":  "password (in clear)",
      "e":  "[email protected]",
      "ds": "A note about this login",
      "r":  "https://login.salesforce.com",
      "s":  true,
      "lt": false,
      "lo": false,
      "lp": "/apex/MyCustomPage",
      "t":  "SECURITY_TOKEN",
      "f":  true
    }
  ],
  "orgs": [
    {
      "oid": "00D0000000000AA",
      "n":   "MYDOMAIN",
      "l":   "Tab label",
      "c":   "#ff0000"
    }
  ],
  "global_quicklinks": [
    { "l": "Deployment Status", "p": "/changemgmt/monitorDeployment.apexp", "orgs": [] },
    { "l": "Acme wizard",       "p": "/apex/AcmeWizard", "orgs": ["00D0000000000AA"] }
  ],
  "queries": [ { "name": "My first query",  "body": "SELECT Id FROM Account" } ],
  "scripts": [ { "name": "My first script", "body": "System.debug('Hello');" } ]
}

Advanced

Pro licensing

Every feature of ORGanizer for Salesforce is free to use. What a PRO license changes is the number of logins you can store and sync, and whether you see advertisements — in the extension's pages, in the Quick Console, and as an occasional message after a number of actions.

To get one: press GET A LICENSE, or go to gumroad.com/organizer, pick a subscription and complete the purchase. The license code arrives with the confirmation email; apply it with the Apply promo code button.

For a wrong purchase, or anything else about payments, use the support form.

Bulk promo codes

Bulk promo codes deliver the Pro features to a company buying a number of licenses at once, or as a trial coupon. A promo code is bound to one email address and has an expiration date — it is not a subscription, and it stops working on that date. Child codes are handed out and revoked from the bulk license management page. Contact support if you are interested in buying them.

Licenses

Your license sets the storage limits shown in the Options page. Every feature works on every plan; what changes is how many logins you can keep, how many of them sync, and whether you see ads.

The full comparison, the number of active clients per license and current prices are on the pricing page. Bulk licenses are administered from the bulk license management page.