APIv4 - Proper ACLs for relationship entity #27183
Merged
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
Improves v4 Relationship api to use fine-grained ACLs instead of coarse-grained permission check which was too restrictive.
Before
APIv3 and v4 require 'edit all contacts' to create/update/delete relationships. Users without that permission cannot save or delete any relationship even if they have ACL permission for the related contacts.
After
APIv3 unchanged, but v4 uses ACLs instead and eliminates the overly-restrictive permission check.