🎨 [Frontend] Enh: Expose access rights when Sharing Study #7467
Conversation
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
odeimaiz
added
t:enhancement
odeimaiz
changed the title
odeimaiz
requested review from
GitHK,
alexpargon,
matusdrobuliak66,
pcrespov and
sanderegg
giancarloromeo
approved these changes
Apr 3, 2025
|
Member
Author
|
@Mergifyio queue |
Contributor
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 5b1d439 |
matusdrobuliak66
approved these changes
Apr 3, 2025
GitHK
approved these changes
Apr 3, 2025
This was referenced Apr 10, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What do these changes do?
As preparation for share-project-via-email, we want to expose the access rights given to the collaborators when sharing a resource. At the moment, when sharing a Study, collaborators get the defaulted
writeaccess rights (these defaults, which depend on the resource type, are hardcoded in the frontend). If that's not the access right the Sharer wants to give, after sharing they would need to go through the list of collaborators and update the permissions.With this PR, these two operations are handled at the same time, providing a better UX.
Bonus:
Rolesrelated data.Related issue/s
share_projectoperation (dev) and updates notifications-library #7431How to test
Dev-ops checklist