Search the Community
Showing results for tags 'category'.
Found 4 results
In the new version, the elements related to the category "login" are not visible. Only new entries are visible. When I export in JSON format, I see that the old entries have the category "login" and the new entries are assigned to the category "inicio de sesión"
I am a new user who is still learning the ins-and-outs and best practices of Enpass. I note that one can change the category of an item by dragging-and-dropping it from the list to the desired new category in the sidebar. However, it seems that the template for the item does not also change to match that of items originally created for the new category. To accomplish this requires deleting the item assigned to the original category and re-adding it assigned the new category. Is this correct? Does anyone else feel this is more than a minor inconvenience?
Hi and thanks for your work. When i create a new account in a website, the browser module ask me if i want to register the new account in Enpass. It's very good ! But if i want to add this account in a category, i must go in the application and move it after. I think it would be best to choose the category we want directly in the browser module. Can you add this feature please? Thanks in advance!
It would be nice to be able to create, change, edit the Types / Category Templates in Enpass. Currently I use mSecure, but am looking to make a switch. I really like that mSecure is more like a custom secure database builder than just a secure password saver, and I think Enpass has the potential to be better than mSecure, but being able to edit the Types / Category Templates is one thing Enpass desperately needs. I know you can add fields to each item when you create them, but I'd really like to set custom templates for items to use and get rid of the ones I don't want. Currently I have over 2000 items in mSecure, most of which use custom item templates. I would like to use Enpass to do the same. Unfortunately mSecure has become over-priced when using multiple platforms, and currently utilizes over 90% CPU usage in macOS 10.12 Sierra when sitting idle. I think it might also be lacking in support.