Login sorting using the 1Password extension

Hi, @pcmbab. Thanks for your post. I'm very sorry for the delayed response.

If you look at the URLs for these Logins, do they all share the same fully qualified domain name, e.g. accounts.google.com or discussions.agilebits.com rather than just google.com or agilebits.com? By default, 1Password sorts Logins that match the full website host over those that only match the root domain name when on a given web page. Does that get to the heart of the mystery? If that doesn't pan out, let us know and we'll see what else we can think of. ;)

--
Jamie Phelps
Code Wrangler @ AgileBits

Hello @JuliaA (and @pcmbab),

Here is an explanation of how the ordering currently works. It assumes that the option Allow filling on pages that closely match saved websites in the Browsers tab of 1Password's preference is disabled which I believe is the default.

When you ask 1Password to fill a login page the first thing it has to do is see which Login items match. The first thing it does is it collects all the items with the correct domain so let's say we're talking about Google's login page. The domain is google so we take all sites that match this. Then we take this selection and group them by the subdomain. This means www.google.com is different from accounts.google.com or even just google.com. We limit showing you the precise matches so if you have two or more Login items that match accounts.google.com we show these as that is the actual address you're visiting when you try to log in and we hide the rest behind the button. We then take all the accounts.google.com Login items and we split them into two groups, favourites and non-favourites and then we finally order each of these groups alphabetically by title. We actually do this for each subdomain but for the most part you really only care about the visible ones. This is why though you can have a favourite item hidden if the Fully Qualified Domain Name (FQDN) doesn't match because we only show the exact matches when there's a mixture.

The following example may help. What I did was set up a bunch of Login items for Amazon. Four correctly patch the actual domain where you log into Amazon and the rest use fictitious subdomains with titles to help identify.

So first I would see

and then if I click on the Show 6 more items menu option I would see

You'll see how the favourites are at the top of each group so they bypass the alphabetical ordering but we still only show the precise matches first.

So if you alter all your Google Login items to use the same URL in the website field you should find that 1Password will show all of them in what seems like a more logical order. Once they are all grouped together because they all match on the domain you can then use a combination of alphabetical ordering and the favourite flag to have them show in a particular order.

Does that help?

Hi @JuliaA,

I'm glad we could help explain how this works. This particular feature/behaviour seems to confuse the heck out of most people so you're not alone at all, there are a few of us here at AgileBits that struggle to wrap our heads round it. We may very well end up altering how things work if we can make it more intuitive but at least you can now bend 1Password to your will :lol:

Thanks so much for the kind words, @JuliaA! To add to your bag of tricks, I'll also mention that if you have Logins that you need to keep around but you don't need to actually sign in to often (such as credentials for a family member's account that you manage), you can edit that Login and set the Display attribute to Never. This will keep it around in 1Password but not show it in the list of Logins when you're using the browser extension or 1Password mini.

@JuliaA We don't have a single place where these get aggregated, but being in the forums, reading our blog, and our YouTube channel are great places to catch some of these. But having more advanced content is indeed something that has been on my mind lately, so perhaps we will see something useful come of it in the future.