# Create a no-sign in part on my app

**URL:** https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474
**Category:** Ask for Help
**Created:** [July 24, 2026, 5:57am UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474 "2026-07-24T05:57:29Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Aurelien\_Faravelon](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/aurelien_faravelon/32/39144_2.png) [@Aurelien\_Faravelon](https://community.glideapps.com/u/Aurelien_Faravelon)
#### Post date: [July 24, 2026, 5:57am UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474/1 "2026-07-24T05:57:29Z")

</div>

Hi,

I have developed a public app to manage registrations to my events. I use Glide Classic

For now, I require users to sign in but I have noticed that most people would rather connect to the app without signing in and sign in only when needed : when they want to register and manage their registrations.

I have thought about it and I want to allow users to access some part of the apps without signing in and I would like to validate my method with you:

1. At the moment, I require users to sign in. I plan on changing my settings to “Public app \> Optional user profile \> Anyone can create a profile”
2. if I set the visibility of some tabs and some components to “User is signed-in user”, will it work? Will it restrict the access to these elements to signed in users only and will people who have not signed in still be able to access the rest f he app.

Thanks for your answers 🙂

---

<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: [July 24, 2026, 6:04am UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474/2 "2026-07-24T06:04:57Z")

</div>

> [@Aurelien\_Faravelon](#):
>
> 1. if I set the visibility of some tabs and some components to “User is signed-in user”, will it work? Will it restrict the access to these elements to signed in users only and will people who have not signed in still be able to access the rest f he app.

Yes, that should work.

---

<div class="post-metadata">

### Author: ![Aurelien\_Faravelon](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/aurelien_faravelon/32/39144_2.png) [@Aurelien\_Faravelon](https://community.glideapps.com/u/Aurelien_Faravelon)
#### Post date: [July 24, 2026, 6:18am UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474/3 "2026-07-24T06:18:30Z")

</div>

Thanks a lot fr this swift answer Daren! I can keep you posed if you’d like, I feel this will change the engagement of my users 🙂

---

<div class="post-metadata">

### Author: ![Emre\_Ozturk](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/emre_ozturk/32/95266_2.png) [@Emre\_Ozturk](https://community.glideapps.com/u/Emre_Ozturk)
#### Post date: [July 25, 2026, 1:12am UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474/4 "2026-07-25T01:12:13Z")

</div>

To restrict specific tabs or components to signed-in users:

- Go to the **Visibility** settings of the tab or component.

- Set the condition: **`User Profile > Email` `is not empty`** _(or `User is signed in user`)_.

- For non-signed-in users, you can display a “Please Sign In to Register” banner with a **Show Sign In Screen** action button.

---

<div class="post-metadata">

### Author: ![herman35](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/herman35/32/95598_2.png) [@herman35](https://community.glideapps.com/u/herman35)
#### Post date: [July 26, 2026, 3:06pm UTC](https://community.glideapps.com/t/create-a-no-sign-in-part-on-my-app/87474/5 "2026-07-26T15:06:43Z")

</div>

Yes it should work. If you switch the app to Public app → Optional user profile, anyone will be able to browse the app without signing in. Then you can simply set the tabs, buttons or components you want to protect to “User is signed in user”. Anyone who is not signed in wont see those items but they will still be able to access the public parts of the app. Just test it in an incognito window after making the changes to make sure the visibility rules behave the way you expect before publishing.
