ghost
commented
1 year ago Definitely a good idea. This allows storing accounts with different privilege levels for the same host or service as the original request describes.
I find myself all too often doing gymnastics with the categories and "site" names as a workaround.
I manage my hardware security tokens from an isolated system using something to Qubes. In my case I have multiple credentials for the same service, sometimes for audit roles and administrative ones. This is not that uncommon a practice by good sysadmins, especially in corporate environments where Kerberos and co can be compromised and you don't use the same user while roaming.
Missing feature
Currently there are only four (4) categories available, which might make a proper separation of credentials difficult.
Examples:
A way to solve this, aside from raising the limit of 4 categories, is the addition of optional second-level categories.
Second-Level category example (click me)
- Services - Social Media - Gaming - Government - ... - Work - First Client - Second Client - Part Time Job - ... - Servers - Home Server - Remote Server - First Game Server - Second Game Server - ... - SecretLife - Government Servers - Fake Identities - ... - ...Justification
This would allow a proper separation of credentials, which becomes necessary once you have more than 20 of them. Especially, since sometimes a manual selection of credentials is necessary, like in the terminal, or a 3rd party device not connected to the Mooltipass.
Currently I have around 100 credentials, as shown in the first examples. A second level would allow faster browsing and a cleaner overview.
Workarounds
This could be accomplished by using service/website labels as subcategories, though this would interfere if you actually had multiple accounts on the same service.