fix(organization): Block profile updates to org-related fields in Multi-Member Organization context #5310
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
Blocked updates to profile fields related to the organization when the user belongs to a Multi-Member Organization (MMO). Ensured other profile updates remain unaffected.
📖 Description
This PR fixes an issue where users in a Multi-Member Organization (MMO) could update fields in their profile that are directly related to the organization. Such updates are now blocked to maintain data integrity within MMO contexts.
These organization-related fields are synchronized with the
Organization
model to ensure the information remains up-to-date, especially when a user purchases a plan.