# How can I share a detail pages publicly but keep the collection screen private?

**URL:** <https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377>\
**Category:** Ask for Help\
**Created:** [October 27, 2024, 3:32pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377 "2024-10-27T15:32:56Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kilian](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kilian/32/81230_2.png) [@Kilian](https://community.glideapps.com/u/Kilian)\
**Post date:** [October 27, 2024, 3:32pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/1 "2024-10-27T15:32:57Z")

</div>

Hi Glide-Lovers!  
I am brand new to the tool and have a question regarding permission.  
I want to use Glide to automatically create multiple landingpages. Each data entry is one landingpage and its property items are the landingpage content blocks.  
Thus, I want to make the detail page (=my landingpage) publicly accessible for everyone who has the link without having to log in, but don’t want the page visitors to be able to see the other landingpages. I managed to create unique links for each detail page by using row id’s but visitors can always click on the database name in the top section to navigate to the collection page, showing all data base entries.  
How can I prevent visitors from being able to navigate their when sharing the link for the detail page?  
Thanks in advance for all the help - it’s very much appreciated!

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 27, 2024, 3:48pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/2 "2024-10-27T15:48:40Z")

</div>

If I were doing it, I’d hide all of the unwanted navigation tabs and then create a custom navigation with visibility conditions that public visitors cannot influence.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/d/bd8c1d9cc98c52b1a68733fd5a9ce34b21addd8a.png)

For example, simply allowing the buttons to be seen by your email address or if you don’t have a user table, creating a user specific boolean column that can only be “checked” by you and when checked allows your custom navigation buttons to be visible.

I’m sure the more experienced Gliders would have even better alternatives to this workaround. I look forward to hearing it as well.

---

<div class="post-metadata">

**Author:** ![Kilian](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kilian/32/81230_2.png) [@Kilian](https://community.glideapps.com/u/Kilian)\
**Post date:** [October 27, 2024, 4:53pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/3 "2024-10-27T16:53:12Z")

</div>

Thanks for your response!  
Unfortunately, somehow this doesn’t seem to work for me.  
When adjusting the conditional visibility of the database as suggested the detail pages also get removed.  
I’ll try to provide some more context:

This is the databases with all the ‘landingpages’, which I want to be invisible:

 ![CleanShot 2024-10-27 at 17.49.47@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/1/01fa9d077ff48061754339f9c9a50076cd87d7d3.png)  
Here is also the link: [Database\_Name](https://testdatabase-637h.glide.page/dl/d0a5f4)

This is one example detail page which I want to be visible for everyone with the link:

 ![CleanShot 2024-10-27 at 17.50.57](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/3/e363da980131cd5b2ac67d3654437a57ca43a7ff.jpeg)  
Here is also the link: [Database\_Name](https://testdatabase-637h.glide.page/dl/d0a5f4/s/181c4d/r/dgUv9CR0th7d9WtXoIOV)  
Currently visitors can always navigate to the first view by clicking on the database title “Database\_Name” or removing the row id from the landingpage url.  
By applying the conditional visibility to the first view, the second view also gets invisible.

I’d love some more input on how to address this, thanks in advance!!!

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 27, 2024, 5:08pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/4 "2024-10-27T17:08:26Z")

</div>

what I meant was hiding the native tabs not hiding the collection. I assumed you were sharing the direct links to the desired detail screen with the users.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/b/cbeebd3526cd6f0edc6aa91670eeae84b26500ce.jpeg)  
is this the breadcrumbs component? If so, you can try deleting it and see if the result works.

---

<div class="post-metadata">

**Author:** ![Kilian](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kilian/32/81230_2.png) [@Kilian](https://community.glideapps.com/u/Kilian)\
**Post date:** [October 27, 2024, 6:47pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/5 "2024-10-27T18:47:10Z")

</div>

Thanks again for the reply!  
Regarding your response - Yes, I am sharing the direct links, however by clicking on “Database\_Name” (which is the title of the page) the visitor gets redirected to the collection page (which is exactly what I want to prevent).  
I also don’t need to hide native tabs as I have only one tab in this particular scenario. Maybe I am phrasing the requirements very poorly (in that case my appologies) but I simply want to generate a detail pager where the visitors have no way to navigate to the underlying collection. Any ideas?

Here’s where the title of the detail page comes from btw:

 ![CleanShot 2024-10-27 at 19.43.34](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/2/e23e5e42a021ba79919c6ec28b487abe2e019ea1.jpeg)  
Adjusting the toggle for “Show” to “None” does here also not help since the top row where title is will still be a link which visitors can use.

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 27, 2024, 7:19pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/6 "2024-10-27T19:19:49Z")

</div>

Ok, I think I understand now. You may need some CSS for this.

@Himaladin  
@ThinhDinh

---

<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:** [October 27, 2024, 7:40pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/7 "2024-10-27T19:40:27Z")

</div>

You could just change the visibility of the primary collection to be hidden via an impossible condition or only be visible to certain users. If a user does try to navigate back to that main tab, they just won’t see anything since the collection is hidden. You could leave it as a blank tab, or have a message saying “nothing to see here”.

But I have also seen that you found the other post referring to the url query parameter method, which works quite well, but requires a little bit more setup.

---

<div class="post-metadata">

**Author:** ![Kilian](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kilian/32/81230_2.png) [@Kilian](https://community.glideapps.com/u/Kilian)\
**Post date:** [October 27, 2024, 9:00pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/8 "2024-10-27T21:00:58Z")

</div>

Amazing, changing the visibility of the primary collection did the trick, thanks for the advice @Jeff_Hager! This is very similar to the solution that @Sekayi_Liburd suggested but I think I made a mistake by trying to adjust the visibility settings on the page level and not the component level. Thanks to the both of you!!

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 27, 2024, 9:47pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/9 "2024-10-27T21:47:59Z")

</div>

Nice @Jeff_Hager . I don’t know about the impossible condition. Could you describe that?

@Kilian I’m glad you found something that works!

---

<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:** [October 27, 2024, 10:29pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/10 "2024-10-27T22:29:23Z")

</div>

> [@Sekayi\_Liburd](#):
>
> impossible condition. Could you describe that?

It’s just any visibility condition that could never be true. For example, you could have a condition of RowID is BOB. That would never be a true condition because a RowID will never be assigned a value of BOB.

---

<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:** [October 27, 2024, 10:56pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/11 "2024-10-27T22:56:00Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/9/290c84b3da0a0dfc240d2b45c4567bb822b26f23.jpeg)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/9/094e84fa2898bdcd2d7326af4f69dc3fdc228e91.jpeg)

Had this exact use case very recently, here’s the setup from me.

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 28, 2024, 12:43am UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/12 "2024-10-28T00:43:54Z")

</div>

what’s BOB? 🥲  
Do you actually mean a guy named Bob?? 🤣 Ok, i get it.

---

<div class="post-metadata">

**Author:** ![Sekayi\_Liburd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sekayi_liburd/32/77608_2.png) [@Sekayi\_Liburd](https://community.glideapps.com/u/Sekayi_Liburd)\
**Post date:** [October 28, 2024, 12:46am UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/13 "2024-10-28T00:46:14Z")

</div>

nice. I have a tumbleweed for “no search results” 😂

![tumbleweed.gif.d5ab39b50dcca50a7615cee0a4c7739a](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/1/b18e92fca5ffe876f451ce341bad9b0d6c5aaf8c.gif)

The youngsters may not get it.

---

<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:** [October 28, 2024, 11:30pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/14 "2024-10-28T23:30:13Z")

</div>

> [@Sekayi\_Liburd](#):
>
> what’s BOB? 🥲  
> Do you actually mean a guy named Bob?? 🤣 Ok, i get it.

Just an example for something that would never be true 😆

---

<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:** [October 28, 2024, 11:41pm UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/15 "2024-10-28T23:41:14Z")

</div>

![Microsoft-Bob-in-application-extension-for-Microsoft-Office-featuring-Comic-Sans.ppm](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/9/e932f958230a454e7d93d210863e9c01e6bdafd9.png)

---

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [October 29, 2024, 3:57am UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/16 "2024-10-29T03:57:04Z")

</div>

Sorry Bob, I’m lost. Can you send me back? 😅

 ![716oOSV-SHL.AC_UF894,1000_QL80](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/5/c5c7600c9be4d2f2390b151e8a7a82b66dcae2f3.jpeg)

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [November 5, 2024, 3:57am UTC](https://community.glideapps.com/t/how-can-i-share-a-detail-pages-publicly-but-keep-the-collection-screen-private/77377/17 "2024-11-05T03:57:19Z")

</div>

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