Learn one feature at a time
A random page of the ORGanizer documentation, so you pick up something new without reading all of it at once.
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.
New in 1.0
Quick Login now also works on the username-only login pages — the ones that ask for the username first and the password on a second screen, which is what My Domain and identity-provider setups increasingly use — and on Salesforce's new email-based login flow.
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.
| Step | What ORGanizer does |
|---|---|
| The email address | draws the same login picker under the field; pick one and it fills the email in and moves on |
| The verification code, when Salesforce asks for one | stands aside and says so — only you can read that email. The flow picks itself back up on its own once you are through |
| The environment switcher | matches your login against the tiles and opens the right one, filtering to production or sandboxes first |
| The password | fills it in and submits |
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.
Where it stops by itself
Nothing runs until you pick a login. If two environments match your login equally well, or none does, ORGanizer leaves the choice to you and waits at the password step rather than opening the wrong ORG. If that step names an account other than the one you picked, the password is not filled in. A flow that stalls is abandoned, and the password it was holding goes with it. When you arrive at a password screen with no flow running and ORGanizer recognises the account, it offers to fill the password in — an offer, which submits nothing.
With encryption enabled, Quick Login needs an unlocked session. If the background worker has been restarted, ORGanizer asks for your master password before filling anything in.
Enable or disable the feature in the Options page — one switch covers both the classic page and the email-based flow.
Show me another one