fix(fields): hide menu without config read rights#1084
Merged
Conversation
stonebuzz
approved these changes
Nov 13, 2025
Contributor
|
Please rebase |
Rom1-B
approved these changes
Nov 13, 2025
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
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.
Description
If a user profile does not have read access to the GLPI configuration, it should also not have access to the Fields plugin containers.
However, the user could still see the Fields menu in the Setup menu, even though they could not view its contents due to insufficient permissions.
This PR corrects this behavior by hiding the Fields menu when the user does not have the corresponding read permission.
Screenshots (if appropriate):