Search the Community

Request Enpass currently sorts entries by frequency, recency, title, creation date, and modification time. I propose adding "Last Interaction" and "Most Interaction" as additional sorting criteria. This change could be useful for users who primarily use Enpass on their (local) Host-System, to copy information to their guest systems (like remote desktops or virtualized and streamed computers). These users often rely on keyboard shortcuts and the Enpass Mini-App to copy logins, license keys, and passwords from the host system to the guest system. Currently, Enpass doesn't remember the last interacted item, which can be inconvenient when providing additional information like OTPs. By tracking the last and most frequent interactions within a 1-2 week period, Enpass could improve the user experience withthe two mentioned sort-criterias from aboth. Interactions could be counted, when the user confirming, copying content from, and editing an entry. Personal case/note: I'm developer, administrator and sometimes also a gamer. So I have a lot of remote-applications, virtualized environments and also playing games via Blade Shadow on a cloud computer. From my security perspective, I don't see any reason to install Enpass on the guest-environments. So I access it only via the global-hotkey of the host-operating-system. It's just a bummer, that it doesn't keeps last and most interacted items up in the list. Because it doesn't remembers my interaction (copying) with them. So most of the times I have always to repeat to search for the entry, before I can interact with it again.

I’ve set up a secondary vault for my adult son who has severe intellectual disability. He will never use this vault but his sibblings will need access. I want to also keep a copy of everything in this secondary vault into a folder in my own Primary Vault. I’ve not entered anything into his vault yet and need to know what’s the best way of achieving the above please?

New 6.20 dropped password copying while editing. I observed same change in macOS and Windows 10 store versions. Maybe this affects also iOS and Android versions. A typical workflow for changing an existing password is: Copy old password using Copy-button, old password is usually required during change Edit the entry Generate new password Click Show to reveal the newly generated password Copy the provisional new password from edit field Sometimes generated password isn't valid and manual editing is required. Reasons for this could be too long password containing invalid characters, etc. At this point old password is not yet lost. It is possible to cancel the change. On successful password change, Save the updated entry IMHO returning the previous functionality enabling editing and copying the password is absolutely necessary.