Api - Adjust permissions for custom field metadata #31695
+4
−2
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.
Overview
Lowers permission requirements for accessing custom field metadata, so that higher permissions do not need to be granted to so many users.
See https://lab.civicrm.org/dev/core/-/issues/5664
Before
All actions required 'administer CiviCRM' AND 'access all custom data'
After
Permission for create/update/delete reduced to 'administer CiviCRM data',
Permission for get reduced to 'access CiviCRM' OR 'access all custom data'.
Technical Details
Note that this is about accessing the custom field definitions, not the data stored in the custom fields.