Logins vs Other Categories -- what if it is both?

waxwing1

Anyone else struggle with items that belong in two categories? I tend to use the Login category as the default but it kind of irks me to have all my bank account information in a Bank Account record but then need to store login info for that bank account somewhere else. Just about every membership, credit card, financial account, etc. has both detailed information that should be stored with it that is not considered login info but it also has a web-site with login info. So, how do most people approach this? What are some best practices?

Thanks.

hawkmoth

I think this is inconvenient too, but I've been living with it long enough that I tend to forget about. One way to tie the multiple entries for the same data would be to use tags, so the account information and the logins can be found together that way.

I haven't thought hard about what could be done about this. Maybe allow login fields in any sort of record.

BobAllison

Like you I have many many items with a corresponding entry in the login section. Examples are: my bank account and credit card entries each have a web page to login for online banking and account maintenance; my email entries have a web mail login; my wireless router has a login; and so on for my memberships, reward programs, etc.

I think as part of adding new sections and fields to items - should be able to add login sections and information to any item in the database.
i.e. Information that would automatically load fields on a website and login to a site it automatically.

khad

It has a lot to do with form filling in the browser.

If you have a Login item for your bank that also includes your debit card and address associated with the account it would be a bit confusing trying to figure out if you are attempting to fill the item as a Login, Credit Card, or Identity. Keeping them separate makes it very easy for you to make your intention clear, and the data needs to be formatted a certain way for 1Password to fill it properly. That's why custom fields you create cannot be filled by 1Password.

It's already pretty tricky to successfully fill on all of the trillions of pages on the Internet even with strict guidelines for the fields. For example, 1Password looks for more than just a field named "address" when attempting to fill the address in an Identity item. There are loads of possible matches (including other languages). It would be quite a chore for folks to specify all possible such matches themselves, and the UI for that would probably be a nightmare. I can't imagine trying to fill fields that don't have any heuristics at all.

Thanks for letting us know you are interested in this, though. We are always improving 1Password, and it helps to know what folks are looking for, how they use the current version, and what they feel are limitations.

For now, you could create a Login item (which will actually "learn" all the form fields on a site's login page if you save it via the browser extension as we always recommend). Then you will have a useful Login item for properly filling your credentials to which you can also add an unlimited number of custom fields including credit card or address information if you prefer to forego the form filling afforded by Credit Card and Identity items. If you wish to just add more information that you don't need filled in the browser for you, custom fields are an even better fit.

I hope that helps. Please let me know and keep the great feedback coming. :)

hawkmoth

@khad, thanks for that perspective. It makes good sense to me, although I clearly hadn't thought of it that way before.