Linking passwords and seperate ssid type

Hello, I was wondering if it would possible to request a feature to support linking passwords/entries/types that are related, and support ssid’s as an seperate type. For example I have a entries for let’s say router (super-admin) passwords. I think it would be usefull if I could see which of the ssid credentionals that i can use when i pull up the login, or vice versa on the ssid that I’m intrested in what credentionals to use to administrator the router. That’s what I mean by related, information that is instrinstically linked with one another.

Right now, in order to group information together and avoid complex naming conventions, the closest thing are custom fields, but I feel it’s not really enough.

I often store the ssid’s in a secrets field, and ssid name as field label to keep it together with router information like make/model etc. However with a complex ssid that are not broadcasted it’s a bit problematic as you have to type over the label manually which isn’t really optimal on touch based devices like tables/phones etc.

So ideally, I’m thinking it would a lot nicer if you there could be an option on each type to basically include reference to another instances of a type. Maybe like a “reference field type“, this way for example a login type, could include an reference to an instance of an ssid type. Or if you have a service with different credentionals for different roles, you could link those together. I think it would improve to organize information better.

1 Like

@Morally9395 Welcome to the forum!

Feature requests are posted in the Feature Request section of the forum.

There are already a few existing feature requests that are relevant to what you are asking for, so I would suggest that you support one or more of those. After you have spent a little more time participating in the forum, your membership level will be promoted from “new user” to “basic user”, which will give you the ability to vote for feature requests. In the meantime, you can post comments in the existing feature request thread(s) to describe your use-case (i.e., why you want the feature and how you would use it).

Here are the relevant feature requests that I could find:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.