disambiguating alternate logins across vaults
Something I'd find very useful (for Teams and Families equally)...
I often have multiple logins for a single site, but more so with Teams/Families where different individuals may have shared their credentials for a site I also have access to. Before Teams/Families, I managed this by appending a username or identifier to the entry name, for example (using a family example): "American Express - Gina's Card" vs "American Express - my card". Shared vaults seem to offer a better alternative.
Here's an example... my son has an account on Khan Academy, and I have a parent account as his coach/parent:
I'd like to be able to disambiguate these logins without explicitly renaming them to include an added identifier, since they are in different vaults. For example, I could now name both "Khan Academy", and I could rollover each to see they are indeed in different vaults:
But that's slow, especially if I have more than a couple such logins. What I'd really like is for the vault name to be indicated in menubar search results, eg, in a different typeface or in brackets, if multiple identical entries are found. As an example, Xcode does this in its File > Open Recent menu... notice I have two "Reflex.xcodeproj", but I can tell which is each at a glance:
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
Hi, @danherman, and welcome to our forum!
You're not going to believe this, but we just added this feature in 1Password for Mac 6.1, which was released today. :)
0 -
@danherman I see you actually were asking to see the name of the vault next to the item, rather than the username. I hope today's improvement with the username works for you, though!
0 -
Hah, that's pretty good even so... are you sure you didn't just implement it quickly following my suggestion? :-)
I'd still suggest as a future enhancement that the vault name might be the better identifier, since usernames can be pretty arbitrary and might not uniquely disambiguate items in different vaults, while presumably the vault name is unique and carefully chosen.
Thanks Rob! Good stuff.
Dan0 -
@danherman: I'm not sure how we'd do it without making it cluttered, but I think that there's a case to be made both for username and vault name.
But just to play devil's advocate, if you're a member of multiple Teams/Families, you'll find that the vault names often aren't particularly helpful (I have 3 "Personal" vaults)... ;)
0 -
Perhaps it needs to be "best disambiguator"...
0 -
@danherman I don't know if there's a way to automate that and pick the best one. Why do you prefer to have a vault disambiguated rather than the username? I'm just trying to envision the use case here, since I personally find it easy to skim a list of emails. :) I'm curious to hear what you have in mind.
0 -
I'm only thinking that usernames might not be something I get to pick... or there might not even be a username. But there's always a vault name, and I get to pick that. So I might have a login to some system whose username isn't personally meaningful to me ("someone-signed-up-for-this-three-years-ago@mycompany.com") but I would only pick a sensible vault name ("Marketing Dept"). When I see "Amazon S3 - Marketing Dept", it really should make sense to me.
I can see arguments being made both ways though....
0 -
I'm only thinking that usernames might not be something I get to pick...
@danherman: This is a great point! I didn't think of that. Most of the time I get to choose my username...but of course in cases where the username is my email address, that's something I chose long ago, and it will be the same for each login like that.
But there's always a vault name, and I get to pick that. So I might have a login to some system whose username isn't personally meaningful to me ("someone-signed-up-for-this-three-years-ago@mycompany.com") but I would only pick a sensible vault name ("Marketing Dept"). When I see "Amazon S3 - Marketing Dept", it really should make sense to me.
This is fascinating, because it's very different from how I do things...
I can see arguments being made both ways though....
Agreed. I guess what it comes down to is that we each kind of have our own system of organization within 1Password's own organizational structure. Since in many ways 1Password is pretty flexible (vaults, folders, tags, titles, etc.) and it's been around for so long, some of us probably have really particular ways of doing things that can actually clash with new features (like showing the username in the extension) that would otherwise be an unmitigated awesomeness, had they come along before we'd already established our own habits. Crazy!
We'll keep working on solutions to these problems; please continue to give us your feedback! :chuffed:
0
