Control Invitation flow with prompt and screen_hint parameters

Feedback
, ,
1

Feature: Control Invitation flow with prompt and screen_hint parameters.

Description: We would like Invitation flow to support parameters prompt and screen_hint, in order to be able to select which dialog to show to the user, Login or Sign Up. Additionally, it would be great if Invitations flow showed Login prompt by default, for consistency with New Universal Login Experience.
New Universal Login Experience also supports the aforementioned parameters, prompt and screen_hint. On user login, Applications are able to select which dialog to show to the user, Login or Sign Up. By default, it always shows Login. This is not the case for Invitations, where the first prompt is always Sign Up. And this behavior cannot be changed.

Use-case: Currently, when an existing user accepts an organization invitation, Auth0 defaults to show Sign Up prompt. The user doesn’t notice that it is not Login, and, when they enter their credentials, an error “Something went wrong, try again later” appears. This creates a broken user experience.
There is no workaround for this issue, unfortunately.

Here is a support ticket number, 00759959.

2

Thank you a lot for creating this feedback card! Let’s see if it gets any traction from other community members!

3

I would like to mention, there is already an older topic that raises the same issue. Have a look here, please, https://community.auth0.com/t/control-flow-of-organization-invitation-towards-login-instead-of-signup/73814.
So, we are definitely not the first ones to ask about this.

1 Like
4

We too have implemented the Organization invite feature, and would like to request the ability to configure whether to display the login or signup prompt by default.

5

@konrad.sopala any update on this. It has been a few months since this is in backlog

6

Agreed this would be great. Since by default it prompts for signup (with a small button to switch to login) it’s not a great flow.

The user doesn’t notice that it is not Login, and, when they enter their credentials, an error “Something went wrong, try again later” appears. This creates a broken user experience.

This part from the original post is especially frustrating. It’s so unclear to the user what the actual issue is.