# Sign in button only

**URL:** <https://community.glideapps.com/t/sign-in-button-only/59872>\
**Category:** Feature Requests\
**Created:** [March 30, 2023, 2:06am UTC](https://community.glideapps.com/t/sign-in-button-only/59872 "2023-03-30T02:06:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [March 30, 2023, 2:06am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/1 "2023-03-30T02:06:47Z")

</div>

I want to allow an admin/owner of an app to sign in to perform certain actions, like send push notification, delete records etc - you get the gist.

**Issue**  
If I enable the optional sign in on a public app two buttons are enabled/displayed _Sign up_ and _Sign in_. I only want to show _Sign in_  
I don’t want anyone signing up or thinking they can sign up.

**What would make me and app owners happy**  
Give me the option to hide the _Sign up button_ and just show the _Sign in_ button

**Thanks 🙏**

---

<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:** [March 30, 2023, 3:57am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/2 "2023-03-30T03:57:34Z")

</div>

This is actually a bug, and a known issue.

Tristan has said they will fix it, but no timeline given. Maybe it will come when the new sign in page options drop? 🤷🏼‍♂️

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [March 30, 2023, 6:18am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/3 "2023-03-30T06:18:08Z")

</div>

Thanks for that.

Apologies I wasn’t aware it was a bug.

I have never seen it where we had just a sign in option so assumed it was something which has been overlooked.

Let’s see if it does come as part of the custom sign in screen. 🤞

---

<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:** [March 30, 2023, 7:40am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/4 "2023-03-30T07:40:59Z")

</div>

Yeah it’s a bit of an edge case, and so not one that you bump into very often. But as you noted, it creates a poor (and confusing) user experience.

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [March 30, 2023, 10:05am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/5 "2023-03-30T10:05:41Z")

</div>

Indeed.

Will keep my close eye on this one as pretty fundamental to what I am trying to achieve for both myself and clients.

Appreciate your insight in this, very helpful

---

<div class="post-metadata">

**Author:** ![Luther](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/luther/32/17929_2.png) [@Luther](https://community.glideapps.com/u/Luther)\
**Post date:** [April 26, 2023, 6:38am UTC](https://community.glideapps.com/t/sign-in-button-only/59872/6 "2023-04-26T06:38:45Z")

</div>

I have voted on this as well. Another issue that it causes is that it eats up on the allocation of public users because once a person has signed up whether you want them to sign up or not, they are counted as a public user.  
The public user quotas were drastically reduced and therefore this would really help us to protect the little that we have. I hope they expedite this and fix it if it really is a bug.
