-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ [Frontend] Leave Organization #6107
✨ [Frontend] Leave Organization #6107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Nice. 🕺🏻
Yes, why not? I guess users should see everything up-to-date once they leave an org.
Tricky one. Ideally, if you can perform this check when they request to leave the org, you can throw an error saying that they have to close the study first. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼
Quality Gate passedIssues Measures |
What do these changes do?
Should I stay or should I go?
Let users leave an Organization if they got personal access (not through an another organization).
OpenAnswered questions:Bonus:
Related issue/s
How to test
Dev-ops checklist