Our platform offers email addresses to their users and stores those in email attribue on ldap and soon planned on Keycloak where we are migrating to. However if a user issues password reset for example, the rest code/link is sent over to the email attribute which obviously the user cannot access. creating a custom attribute like platform_email is also not a solution because Keycloak uses email attribute as a primary source of communication with the user. So any kind of verification is sent to email while it should be sent to platform_email as a primary source.
As a platform administrator I would like to suggest that realm admin could select which attribute to be used for actions such as “Send Reset Email” or “Verify existing account by Email” flow. It would make keycloak more flexible out of the box for scenarios such as described above without the need to custom build flows just to change one attribute.