Q1. What is the problem that you are trying to solve?
Organizing passwords in groups is great. In our case we use groups to share passwords for our client projects. Any password, things like demo logins up to credentials used in production. The downside of sharing passwords with a group is, that I am not able to use further rules who is able to see which passwords. It’s all-or-nothing. Sure, I could introduce another group for more confidential passwords but that would ruin our naming schemes of the groups (which are the same in our org all over the place) as well as make navigating in Passbolt more complex as the users would need to check both groups for the password they are looking for.
Q2 - Who is impacted?
Q3 - Why is it important and/or urgent?
Q4 - What is your proposed solution? (optional)
I could imaging marking user accounts as being able to view “confidential” password entries and then also let the user mark password entries as “confidential”. This is kind of similar to a feature GitLab offers where they allow to mark issues as confidential.
Q5. Community support
People can vote for this idea to show traction:
- Must have: this is critical for me to have this
- Should have: this is important for me to have this
- Could have: this could be nice to have
- Won’t have: we should not schedule this (explain why)