# Is this the right way to make a new \*sign up\* page

**URL:** https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734
**Category:** Ask for Help
**Created:** [January 19, 2024, 3:51am UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734 "2024-01-19T03:51:25Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)
#### Post date: [January 19, 2024, 3:51am UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/1 "2024-01-19T03:51:25Z")

</div>

I see that Glide automatically has Sign Up and Sign In available for users.

I assume the difference is that sign up is meant to create a new row, whereas sign in doesn’t?

Anyhow, I want users to fill out this quick profile when they Sign Up, is this the right way to go about it?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/1/c11362a7e5c301f593e93a94845ff27970833c06.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/9/29da067498b12c9b3b591ef65bbdbf23f41bb163.png)

And then set the tab visibility to users to have an email but their profile is incomplete?

---

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 19, 2024, 4:53am UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/2 "2024-01-19T04:53:25Z")

</div>

In my opinion, there is absolutely no difference between Sign Up and Sign In. Both require you to sign in and both automatically generate a new user row if needed. It’s just two different names for something that does the exact same thing.

I recommend not using a form because you will end up with a second user row which will cause issues. Other than that, yes you would just control tab visibility based on if a user profile is completed or not.

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 19, 2024, 5:54am UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/3 "2024-01-19T05:54:16Z")

</div>

> [@Jeff\_Hager](#):
>
> In my opinion, there is absolutely no difference between Sign Up and Sign In. Both require you to sign in and both automatically generate a new user row if needed. It’s just two different names for something that does the exact same thing.

The difference is where you have a Public App with optional sign-in, and then what you do with user access.

- If you allow anyone to sign in, then you’ll see both buttons
- If you restrict who can sign in, then you’ll only see the sign in button

It makes sense to me in that context.

---

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 19, 2024, 1:00pm UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/4 "2024-01-19T13:00:07Z")

</div>

But they do the same thing, correct? With any other website that I’ve interacted with, they won’t let you Sign In until you have Signed Up. A login attempt will be rejected until you have an account. With Glide you could click on either one as a New or Existing user and gain access into the app whether or not you have an account. To me Sign Up means onboarding and collecting information **before** signing in. With Glide, I think having two separate buttons is more about making the user feel less confused, but both buttons are functionally the same.

---

<div class="post-metadata">

### Author: ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)
#### Post date: [January 19, 2024, 10:04pm UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/5 "2024-01-19T22:04:59Z")

</div>

So either way, I shouldn’t do a form screen after bc that will end up creating a different row from the email row that was just signed in?

Instead, I should just make a new screen then? With the visibility conditions I need for them to fill out the profile?

---

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 19, 2024, 11:15pm UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/6 "2024-01-19T23:15:29Z")

</div>

You can either do a detail screen with entry components linked to the same row, or you could have a button that leads to an edit screen to edit the user profile.

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 20, 2024, 9:22am UTC](https://community.glideapps.com/t/is-this-the-right-way-to-make-a-new-sign-up-page/69734/7 "2024-01-20T09:22:46Z")

</div>

> [@Jeff\_Hager](#):
>
> But they do the same thing, correct? With any other website that I’ve interacted with, they won’t let you Sign In until you have Signed Up. A login attempt will be rejected until you have an account. With Glide you could click on either one as a New or Existing user and gain access into the app whether or not you have an account. To me Sign Up means onboarding and collecting information **before** signing in. With Glide, I think having two separate buttons is more about making the user feel less confused, but both buttons are functionally the same.

Yep, I don’t disagree with any of that.
