Portal Access Concerns

I have some concerns with the User Portal changes in v2.47, specifically around password visibility and permissions.

First, passwords stored in a client's root folder appear to be accessible to portal users by default. From a security standpoint, I'd prefer a default-deny approach that follows the principle of least privilege. Access should be explicitly granted rather than requiring administrators to take additional steps to restrict it.

This is particularly concerning for existing passwords that may have been created without any expectation of being accessible through the User Portal. We shouldn't have to reorganize credentials into subfolders or modify individual records simply to maintain their existing level of access.

Second, relying primarily on folder-based permissions creates unnecessary complexity. For example, if John needs access to Password 1 and Password 2, but Janet only needs Password 2, we now have to create separate folders to accommodate those permissions. Since a password can only reside in one folder, this also forces us to organize credentials around access requirements rather than their logical purpose.

I understand the goal was to move away from the previous portal's permission model, and I can appreciate the benefits of folder-based permissions for managing access in bulk. However, I think there should still be an option to restrict access by default and grant permissions at the individual password level.

Ultimately, I'd like to see folder-based permissions and individual record sharing coexist. That would provide flexibility without compromising least privilege or creating unnecessary administrative overhead.