This would be a great idea.
Agreed on this one. Creative naming can get around this, but there's room for longer names, so I don't see any reason why this can't be tweaked to make use of that extra room.
(Doesn't appear to have changed since this idea was last updated in March)
(can't vote since I'm out of votes)
Sub-groups are supported, unless you wanted even deeper groups beyond the two levels supported now?
The Trash Can can be listed in the dropdown menu where the groups are and the "Oldest First" option.
(Ultimately, I'd like to see this dropdown menu become a bit more enhanced visually and functionally, but that's a separate suggestion)
Brian, to answer for Scott, yes that would be the same idea. Please combine these.
Not only websites, but other URLs, too. For example, we log into our servers via HTTPS or SSH, so having both URLs available would be very handy for us.
Labeling each would be very handy, too, even if that label was generated automatically from the protocol.
I would add to this that any fields expecting an email address should ideally use [type="email"] to get the most optimal keyboard displayed on mobile devices.
You stated that: "A user's master password is their key to decrypting passwords, so we can't swap that out without re-encrypting data for them."
But that doesn't make entire sense. If I, as one user, adds a record to TeamPassword, then my tech person logs in with his password, he has access to that record, as well. But how does he have access if my own password was used to encrypt the data?
Something isn't jiving with your explanation and team access to the stored data.
Does your system lookup the "owner" of the record being accessed and uses their password to decrypt that record? What if that person is removed from the system, then the key is lost as well. So I doubt that's how your system works. Please clarify.
Yes, I have a team member who has forgotten his password. #stuck
Yes, API access to TeamPassword would be absolutely outstanding!
Confirmed in a fresh browsing session in a second browser that had not yet been used with TeamPassword.
1) Cleared all cookies.
2) Logged into TeamPassword.
3) Was prompted for 2FA code. Entered it.
4) Checked "Remember This Device".
I actually logged in twice, first time not checking the option to Remember This Device. The same 11 cookies existed both times, so a separate cookie is not being used for that option. Likely, it's part of my account's settings, but no option is being exposed to undo that setting. Now I have two separate browsers (Safari and Chrome) that are not prompting me for 2FA no matter what I do. Can you elaborate on how this feature works?The Digital Orchard shared this idea ·