# Optional sign-in / Bug UX?

**URL:** <https://community.glideapps.com/t/optional-sign-in-bug-ux/65240>\
**Category:** Ask for Help\
**Created:** [August 21, 2023, 10:02am UTC](https://community.glideapps.com/t/optional-sign-in-bug-ux/65240 "2023-08-21T10:02:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manuel64](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/manuel64/32/63132_2.png) [@Manuel64](https://community.glideapps.com/u/Manuel64)\
**Post date:** [August 21, 2023, 10:02am UTC](https://community.glideapps.com/t/optional-sign-in-bug-ux/65240/1 "2023-08-21T10:02:58Z")

</div>

Hello,  
I have a user experience issue that I can’t seem to resolve with authentication. When I set the app to “PUBLIC ACCESS” and then to “Optional sign-in”, I see the “sign-in” button displayed in the menu. But if a user clicks on it, there’s no button to return to the public app. They get stuck on the login page. This is a real problem. Do you have a solution?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 22, 2023, 1:38am UTC](https://community.glideapps.com/t/optional-sign-in-bug-ux/65240/2 "2023-08-22T01:38:29Z")

</div>

![IMG_6D0BE739FE0E-1](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/1/71ff4e0688cc1e08b22cedafc00310e2461d6c0b.jpeg)

This is a fair request. I installed an app with configuration as you mentioned, and there’s no option to move back on my phone.

@Ivo_Elbert @tristan

---

<div class="post-metadata">

**Author:** ![Manuel64](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/manuel64/32/63132_2.png) [@Manuel64](https://community.glideapps.com/u/Manuel64)\
**Post date:** [August 30, 2023, 7:12am UTC](https://community.glideapps.com/t/optional-sign-in-bug-ux/65240/3 "2023-08-30T07:12:37Z")

</div>

Hi @Ivo_Elbert @tristan  
Do you have any news about this UX bug?
