-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Encrypted fields visibility for Non-Admins #15366
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
Thanks @snipe for the quick reply. You are right, I should have double checked. Then I am afraid it is a bug report. Users with those permissions enabled can view the encrypted fields and copy them, but they cannot edit them. When editing an asset, the value is showed in the corresponding field. Though if they modify and save, no error is shown, but the field is not updated. |
Steps to reproduce
|
Shall I close and reopen as bug report? |
Can confirm on pulled newest master. If user isn't set as admin, his edits of encrypted fields doesn't save. In debug mode could find errors or warnings. |
Signed-off-by: snipe <[email protected]>
Fixed #15366 use the non-admin edit encrypted custom fields permissions
Thanks again! :) Looking forward for next release! |
Signed-off-by: snipe <[email protected]>
Is your feature request related to a problem? Please describe.
Currently encrypted fields are only viewable and editable by users with admin role.
Nonetheless, granting admin role will also grant all other permissions.
Describe the solution you'd like
A better granularity would be desirable, so managers could for example add new assets (filling also encrypted fields) but cannot edit Users.
A possible solution would be to add additional permissions for encrypted fields, similar to "Custom fields"
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: