feat(organization): restrict user management to organization form TASK-1315 #5314
Conversation
This file contains 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
- Make OrganizationUsers fields read-only in Organization form - Remove add/change OrganizationUsers from Organization users section - Remove Organization invitations section
noliveleger
changed the title
1 similar comment
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.
📣 Summary
Limit user management (add/edit) exclusively to the organization form in (Django) admin interface
📖 Description
This PR removes the ability to add or edit users outside the organization form. It ensures centralized and consistent user management within the organization.
Updated relevant components and endpoints to enforce this restriction.
💭 Notes
Organization invitations section has also been removed (until further notice).