Matching sub-domains [No plans for this]

As you noted, it's already possible to associate a Login with different websites by adding multiple URLs. That's not only very discoverable (as opposed to an unintuitive settings screen) but it also ensures that people aren't running into confusion (or phishing attacks) because of something wholly disassociated from the Login they're actually using which they'd set at some point. You can already accomplish what you're trying to do by adding the URLs you want to specific Logins. That ensures that you actually do want to have those specific login credentials (as opposed to any you save for a given URL ever — or those in a shared Login) are intended by you to be used across those sites. And it is easy for the user to change that URL list for a Login at any time right from within that Login, immediately before or after using it (and deciding a change is necessary), without having to search for obscure settings or as us where to find them. Pretty much anyone can do that, and as such that's a benefit to all 1Password users. It's possible we'll add more flexibility in the future, but we try to focus on working on things that benefit the most 1Password users without being to the exclusion of others.

@Telokis: As a nerd, I think both are interesting ideas, but I would hate for 1Password users to have to deal with something like that (apart from the few who would want to). When you say "URL rules", unless I'm misapprehending your meaning, that's what I was referring to here:

it also ensures that people aren't running into confusion (or phishing attacks) because of something wholly disassociated from the Login they're actually using which they'd set at some point.

It's settings that potentially impact the behaviour of all saved Logins which are completely divorced from the actual Login items. We've been trying to avoid and reduce stuff like that, like the old "Show logins which closely match the current web page" (or something — I can never remember the exact verbiage since we changed it so many times) which was removed in version 7, which caused untold confusion for users of all technical backgrounds, including us.

So I think it's important to take a step back and look at the problem trying to be solved, how it's affecting people, and just how big that impact is before tacking on options. Often they're not the answer, as they introduce more problems (bugs, confusion, etc.) Any option we add, people are going to use it whether or not they need to or even understand what it does. So that's absolutely something we need to consider as well.

@Telokis: Hey, I'm sorry for being so bad at making my point on this topic, and I appreciate you bearing with me while I try! :lol: I agree with you: what we have now isn't optimal either. I think there's definitely room for improvement. It's just really tricky because any change we make will impact millions of 1Password users, so we really need to think things through carefully. Perhaps the only thing worse than not having a feature you want is us giving it and then taking it away because we did not foresee a negative outcome. :scream: But perhaps we'll be able to come up with something that can help even more people in the future. :)

@Telokis: I think that's a fair summary. Thank you. :)

The old "lenient URL matching" option you referenced would have had the opposite effect to that being discussed here: it ignored subdomain completely and showed all matches for the domain as being equally relevant. Caused a lot of confusion, so we removed it. It's just one of many real world cases where having options in this area can be more trouble than it's worth to the vast majority of users. A lot of people checked that, forgot, and ran into a lot of confusion and frustration as a result. We could never find wording that made what it did crystal clear to everyone either, so that certainly didn't help. I'm glad it's gone, and we're going to be extra careful before introducing anything even remotely like that again.

I really appreciate the points you're making here in advocating for your use case (and ours as well, to an extent). URL rules, though obviously a different use case technically, really ends up in the same place with similar concerns. Rather than saying "no, never", we'd just make sure we're not putting something out there that we need to yank right back if and when we do something like this. :)

@Telokis: I'm not sure that the problem of you and I having too much data is something 1Password can help with (quite the contrary, perhaps!) but you're right that for the specific workflow you're describing there's room for improvement. We'll see if there's something we can do to make the flow more flexible in the future, without making it unnecessarily complex and more error prone. Thanks for the feedback!

Is there any way to make 1Password strictly match subdomains in the current version?

No.

How high priority would you say this is for the 1Password team?

Not high. It comes up only occasionally, and while there are certainly folks who would appreciate that functionality, we're squarely in the minority. Most users expect to be able to use a login across a domain. Many also expect to be able to use them across different domains, but that's a potential security risk, and they can set that up manually if they really want to.

@schmalli: You should be able to tell from my screenshot that I'm experiencing the same thing. ;) But you and I are squarely in the minority. If we can find a way to make it easier for our use case without negatively impacting the majority of users, I'm sure we will. :)

@sbarnea - no worries - we understand. If another solution better fits your needs, as long as it's not sticky notes on your monitor or reusing the same three or four passwords everywhere, we'll be happy you found something that works for you.

@sbarnea:

Thank you for taking the time to chime in! We would obviously be sad to see you go, so hopefully we will manage to find a solution that doesn't involve you coding anything yourself :)