Can the Auth0 Guardian app be "disabled" after we make our own authenticator app?

Problem Statement

Our users can now utilize our own Authenticator app to log in by scanning the QR code. However, this method can also be accomplished using the Auth0 Guardian app. The issue arises when a user chooses the Guardian app, as this leads to the loss of the capability to save the user’s phone number using our proprietary authenticator app. Is it feasible to “disable” only the Auth0 Guardian app?


Currently, it is not feasible to achieve this. The enrollment process involves two aspects. Firstly, there is a One-Time Password enrollment that is not exclusive to Auth0 Guardian. Secondly, the process combines this enrollment with configurations to offer the push functionality.