This is a really old topic, but could I add my name to those who complain about what seems like an arbitrary distinction between other categories and login categories? At present, there is a rather clumsy (and still uni-directional by default) way of linking, say, a Rewards item with the Login item to go to the Rewards site. The reason for having a Rewards category is that it pre-defines a number of useful fields, which I would have to define every time I create a new Login item. Why not just apply the templates directly to Login items, instead of treating the Rewards category as a completely different type, i.e., treat the Rewards category as a sub-class of the Login category? If it contains a URL and a password, then it should be possible to login. My impression is that this was a design decision made many, many years ago, but I believe it has long outlasted its usefulness and should be updated in the way that many users have requested over the years. There may be categories (Documents, Drivers Licenses, Passports?) that should not be a sub-class of the Login category, but these days virtually every interaction involves logging into to website. Please make it simpler.
P.S. if there is some good programmatic reason that I don't understand for keeping the current Rewards category separate, please consider adding a way of applying templates to existing Login items. It would end up being the same thing.
1Password Version: 7.6
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided