How to restrict organization owners in zitadel ui console to certain features only?
Original message was deleted
FHm I guess in this case your best approach is to create your own UI on top of the zitadel api which allows you to create orgs as well as allow a org_owner to create new users as he sees fit.
AHi! @FFO I was searching for related issues about Zitadel Console, my problem is similar but instead I would like to restrict what users can see on the Zitadel console as I am using only for password purposes for now, so most of user metadata should be hidden, is it possible?
The idea behind this use case is I want to keep UX/UI of my app but still using Zitadel password reset capabilities, maybe I should move the profile page to my own and call human user endpoints from there If I wanna update something? what's the best approach? for those who needs Zitadel reliability without changing too much the UI, much thanks! and I appreciate the support on these channels!
The idea behind this use case is I want to keep UX/UI of my app but still using Zitadel password reset capabilities, maybe I should move the profile page to my own and call human user endpoints from there If I wanna update something? what's the best approach? for those who needs Zitadel reliability without changing too much the UI, much thanks! and I appreciate the support on these channels!
FWell in that case I think its best if you build a profile page in your webapp instead of sharing the console with the users.