[IMP] vault: add User security group to control module access - #975
Open
jans23 wants to merge 1 commit into
Open
[IMP] vault: add User security group to control module access#975jans23 wants to merge 1 commit into
jans23 wants to merge 1 commit into
Conversation
jans23
force-pushed
the
18.0-imp-vault-user-group
branch
3 times, most recently
from
July 23, 2026 06:11
61e3baf to
50357ce
Compare
jans23
changed the title
Gate the module behind a new "User" group instead of base.group_user. Granted via base.default_user so all users keep access by default, but it can be removed from a user to deny access.
jans23
force-pushed
the
18.0-imp-vault-user-group
branch
from
July 23, 2026 06:48
50357ce to
4b4ed0d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a new visible User security group under a dedicated "Vault" category. The whole module (menus, model access and record rules) is now gated behind this group instead of base.group_user. The group is implied by base.group_user so every internal user keeps access by default; removing the group from a user denies access to the vault without touching their keys.