-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add GUI option to disable settings flow #188
Comments
do you remember the use case? slack history is gone... |
yes :( I think the use case was to prevent the user from changing their profile information. |
Maybe we could also introduce a “reject” Action / built in hook that you can just configure to run pre settings flow (or anywhere else deemed useful). |
Hello contributors! I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue
Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic. Unfortunately, burnout has become a topic of concern amongst open-source projects. It can lead to severe personal and health issues as well as opening catastrophic attack vectors. The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone. If this issue was marked as stale erroneously you can exempt it by adding the Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you! Thank you 🙏✌️ |
It is possible to disable the settings flow in the identity service configuration, but not in the UI.
Would be a good addition in base settings
context: https://ory-community.slack.com/archives/C02MR4DEEGH/p1669392879249409
The text was updated successfully, but these errors were encountered: