Passwork 7 RC

A release candidate is the last step before the official release of Passwork 7.

It is almost ready, but needs real-world testing to catch any last-minute issues and confirm everything works perfectly otherwise. Your feedback will make a direct impact on the update, ensuring a smooth launch.



We’ve completely revamped the code using more up-to-date methods. This will improve performance, make installing Passwork easier and allow for API-based integration and automatization for all processes. This code will serve as a foundation for the upcoming desktop apps and will help us release new Passwork features quicker.



We’ve updated Passwork UI and redesigned the key areas of the app based on your feedback. The UI update keeps the familiar workflow, while fixing a number of flaws and non-clear wording. For example, improved UI personalization now lets you set column width or move elements around.



The Status system has been changed. We’ve renamed Statuses to Roles, and now they include administrative rights and custom settings, which means you will be able to create an unlimited number of roles with customized rights and settings, instead of simply choosing between an Administrator or Member status.



What previously was Roles is now called Groups, which makes user management more intuitive and closer to commonly accepted standards, for example those used in Active Directory. Groups help tailor users' access to vaults based on set permission levels.



Vault structure has become simpler. Now there are no organization vaults, and all vaults created are private by default. A private vault becomes a shared one once you invite other users to it. At the same time, administrators don’t get automatic access to newly-created vaults.

The updated structure supports strong encryption and expands password management capabilities, making the process more convenient and safe.



Now, when you add regular or LDAP users into groups, they won’t automatically gain access to other users’ vaults. Instead, the vault’s administrator will have to confirm their access request. This adds another security layer by restricting unauthorized access to vault contents.



We’ve reworked the access level system and introduced a number of changes to some of them:





We’ve expanded the list of actions that are logged, updated their descriptions and completely reworked the notification system. Soon after the release we are going to introduce notification settings, which will add flexibility to keeping track of important changes and user actions.



In order to enhance security, we’ve made some changes to the way shortcuts work:



Now when you create or edit a password, you will be able to pick a tag from a list of already created ones. This has an added benefit of preventing creation of tags with the same name (sales ↔ Sales, etc.)



When you reset your authorization password, two-factor authentication now won’t be reset along with it. Users won’t be able to reset 2FA without a successful login, which increases security.



We’ve introduced an account locking feature. You will be able to set a limit on failed login attempts, timeframe for tracking the failed attempts and lockout duration.