# Email-only signup, followed by full signup after verification

**URL:** <https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967>\
**Category:** Get Help\
**Created:** [July 8, 2020, 4:55pm UTC](https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967 "2020-07-08T16:55:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ccleve](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ccleve/32/22441_2.png) [@ccleve](https://community.auth0.com/u/ccleve)\
**Post date:** [July 8, 2020, 4:55pm UTC](https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967/1 "2020-07-08T16:55:08Z")

</div>

I’d like to put an “Enter your email to sign up” control on my website home page, which would then show a “check your email” message. The user would go to their email, click the link, and it would take them to a larger signup page that would ask them for their name, company, the password they want to use, etc. Only users with verified emails would get to the second signup page, and only users that had filled out both pages would get into the app. Is this possible?

(I’m sure this question has been asked before, but I didn’t see it in the FAQ and I’m not even sure what terms to search for.)

---

<div class="post-metadata">

**Author:** ![colin.coutts](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/colin.coutts/32/17217_2.png) [@colin.coutts](https://community.auth0.com/u/colin.coutts)\
**Post date:** [July 8, 2020, 9:51pm UTC](https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967/2 "2020-07-08T21:51:28Z")

</div>

Hi @ccleve and welcome to the Auth0 Community! We’re happy to have you 🤠

I think we can get pretty close to this use-case, but let me try and break it down below.

> [@ccleve](#):
>
> I’d like to put an “Enter your email to sign up” control on my website home page, which would then show a “check your email” message.

This aspect may be tricky from an Auth0 perspective because at this point we have no idea who those users are. Something to possibly consider is maybe that ‘Enter your email to sign up’ message triggers a mechanism that calls the [Management API and creates a User](https://auth0.com/docs/api/management/v2#!/Users/post_users) with a temporary password. Here’s some further documentation (not quite your use-case) but a number of the steps could be similar.

> **[Send Email Invitations for Application Signup](https://auth0.com/docs/customize/email/send-email-invitations-for-application-signup)**
>
> Describes how to customize the signup process to invite users to signup for an account in the context of a specific Auth0 application.

Alternatively, this part of the flow could simply be handled by your application which would still trigger an email event and the link supplied in the email would redirect you to your login page.

> [@ccleve](#):
>
> The user would go to their email, click the link, and it would take them to a larger signup page that would ask them for their name, company, the password they want to use, etc.

Depending on how you created the User, you could use our Universal login page to gather further information using [additional fields](https://auth0.com/docs/libraries/custom-signup) for the user to fill out. Additionally here’s our resource on progressive profiling which may offer some ideas on collecting this data as well:

> **[Understand How Progressive Profiling Works](https://auth0.com/docs/manage-users/user-accounts/user-profiles/progressive-profiling)**
>
> Understand how progressive profiling can gather information about users over time as they engage with your website or application.

> [@ccleve](#):
>
> Only users with verified emails would get to the second signup page, and only users that had filled out both pages would get into the app. Is this possible?

Depending on your implementation some of this could be handled with either [Hooks](https://auth0.com/docs/hooks) or [Rules](https://auth0.com/docs/rules) to modify the user’s login flow (either by denying access to the app or whitelisting their entry).

Hope this information gets you a solid start in architecting out your use-case (apologies that the response is a bit broad).

Best,  
Colin

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [July 14, 2020, 10:12pm UTC](https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967/3 "2020-07-14T22:12:53Z")

</div>

Hi @ccleve,

We are currently seeking feedback to improve our User Invitation flow. If you have a moment, please take a second to checkout this feedback opportunity with one of product managers.

> [@](#):
>
> Greetings! I’m Michael and work as a Product Manager looking after User Management here at Auth0. User onboarding is core to every application builders’ solution. In many apps this is done by way of invitation which needs to be simple for users as well as secure for organizations. Implementation can be tricky as there are a lot of edge cases to consider. We really want to hear your frustrations (and joys why not?) when using Auth0 to design and implement user invitation flows. Topic: Product …

Thanks!

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [July 29, 2020, 2:12am UTC](https://community.auth0.com/t/email-only-signup-followed-by-full-signup-after-verification/45967/4 "2020-07-29T02:12:56Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
