Request to keep credit card and login details in the same item
Comments
-
This content has been removed.
-
Hi @JamesHenderson,
Thanks for taking the time to post your request! I hope you don't mind, but since your suggestion is a bit different than the one in the previous thread, I've moved your post to a new discussion.
I can send your request to our developers, but I'd also like to explain a bit about why Login and Credit Card items are separate (aside from the fact that not all website logins are associated with credit cards, and vice versa). In a nutshell, it's because they are used to fill two different types of web forms. Login items are used for filling out website login forms (usually a username and password), and each website login form is unique (i.e. you would typically use a different username & password for each site, so each site needs its own Login item). Credit Card items are used for filling out credit card forms, which are fairly standard, and one Credit Card item in 1Password can be used for any number of sites.
Also, website accounts and credit card accounts are really two very different kinds of accounts, even if they happen to be associated with the same bank. Credit Card items don't have a username field because that isn't something you would find on an actual credit card, and isn't part of a credit card form on a website. Login items don't have fields for credit card data, because each one is created to fill a specific web form that normally includes a username and password, but not the details from your credit card.
Now, if you really want to store website login info in a Credit Card item, you can add custom fields for that. However, custom fields aren't used for filling forms on websites, so you would still need to have a separate Login item for that.
I hope that helps to explain why there are separate items for things that are otherwise associated with each other. But we definitely appreciate your suggestion, and we've heard similar requests from other customers in the past, so like I said, I can let our developers know you'd like that too. If you need anything else, please let us know! :)
0 -
This content has been removed.
-
Thanks @JamesHenderson! Like I said, I can certainly pass your suggestion along to our developers. I just wanted to give some explanation for why it currently works the way it does.
We're always happy to help, so please let us know if you need anything else! :)
0 -
@JamesHenderson: If it helps, I like to think of different item types based on their use. For example, you'll want a Login item to fill in login credential on websites, whereas a Credit Card item is exclusively for filling payment information.
Just think of the Frankenstein monster with two legs of differing lengths (and owners — /shudder). Maybe one used to belong to a marathon runner. But if the other had come from a figure skater...well, good old Frankenstein probably isn't going to be much good in either case. Likewise, a weird Login-Card hybrid item would not be good at filling either type of information.
Now, it may be that in the future we'l be able to make 1Password unfathomably smart about this and it won't be a problem, but currently 1Password depends on these item types to know what it's supposed to be trying to fill. I hope this helps. Happy Halloween! :sick:
0 -
This content has been removed.
-
OK. forget credit-cards for the minute (they were only an example). Let's take Reward-cards instead; I have a reward-card entry that has no function, and also a login entry for that reward-card account. Would be cool if these were one entry that could both login and provide the non-login information
@JamesHenderson: Sorry if I was a bit dense about that. Thanks for the example. That certainly makes more sense! Do you think maybe some ability to link items would be useful? It's certainly a feature we can consider adding in the future. Let me know! :)
0 -
This content has been removed.
-
I am personally mainly interested in duplicate info (one set of which could be out of date). I guess a super-group (of linked entries) that shows the non-login "master" entry at the top and the rest of the associated login entries below (like a stack or a scroll) could be a work around?
@JamesHenderson: Hmm. Possibly...or perhaps something like 'Frankenstein items': items which are composed of a Login section, Card section, etc., which are used to fill the appropriate information when selected.
Now, that sounds pretty cool, but it does pose some significant challenges. First off, it would require a fundamental reworking of how 1Password items function. But also you'd need to have a way to select the type of filling, since the item types would be blurred. It kind of turns everything on its head, but it's a unique idea to explore. :eh:
One of the problems for me is that the only way to find these is through search as they never naturally show themselves together (as one is a login-entry and one is not). Therefore managing multiple-associated entries is difficult.
Indeed. I've experienced this myself. I guess the takeaway is that, as our vaults grow ever larger, we'll need better ways of dealing with the data in general. We'll definitely continue working on this problem! :)
0 -
This content has been removed.
-
As long as the Frankenstein entry is not a category by itself.
@JamesHenderson: I certainly hope not! Whew! :lol:
I know I'm doing a terrible job of explaining what I'm conceptualizing here, so I'll have to think about this a while so I can get my point across when discussing these sorts of category-blurring features in the future. I'm glad you made me think about this from a new perspective. Hopefully we'll be able to come up with a cool, intuitive solution to this problem. Cheers! :)
0 -
This content has been removed.
-
:+1: :)
0 -
This content has been removed.
-
Hi @JamesHenderson,
I think the same question has been asked in a different way here
That thread is about linking items to each other in 1Password, and that's actually something that is now possible in our new 1Password for Teams and 1Password for Families services. The 'Related Items' feature allows you to link items to each other so that when you view one, you can easily jump to the other by clicking the link in the item details. It's really helpful for when you have multiple items that are somehow related to each other!
More and more, I am finding myself copying all the relevant info from the non login category across to the login category (for the same item) to keep the info in one item only (e.g.: I have a "email account" and a "login" for the same email account).
As long as that's helpful for you, no problem! :)
One thing to keep in mind is that websites sometimes make small/internal changes to their sign-in forms that can cause a Login item in 1Password to stop working correctly. When that happens, the fix is to save a new Login item for that site so 1Password learns how to fill the updated form. But if you added extra information to the original Login item, you'd need to copy all that to the new Login item. It probably wouldn't happen too often, but might be inconvenient for you if/when it does, so I thought I should mention that.
We're here for you if you have more questions about that! :)
0 -
This content has been removed.
-
Thanks @JamesHenderson! And please know that I completely understand your original post and that you'd prefer to have everything in a single item. I just wanted to let you know about the "Related Items" feature since you had mentioned the other thread about linking items to each other. I also wanted to explain about the possibility of having to save a new Login item for a website in the future, to hopefully help avoid what might have been an unwelcome surprise.
Again, we certainly appreciate your feedback about all that! :)
0 -
This content has been removed.
-
:+1: :)
0 -
I appreciate Drew explaining things better than I probably could have. ;)
For me, being rather particular when it comes to organizing things, I can absolutely understand the impulse to "simplify, man!" and use a single item for a single "thing" (conceptually, anyway). But with 1Password it very much pays to be pragmatic: separate Credit Card and Login items will produce much better (and therefore less frustrating) filling results, so I've come to accept this for the sake of my own sanity. :lol:
0
