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

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!

1 Like

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.

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.

1 Like

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:


Here is also the link: Database_Name

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


Here is also the link: Database_Name
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!!!

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.


is this the breadcrumbs component? If so, you can try deleting it and see if the result works.

1 Like

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:


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.

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

@Himaladin
@ThinhDinh

1 Like

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.

4 Likes

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!!

2 Likes

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

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

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.

2 Likes

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

2 Likes

what’s BOB? :smiling_face_with_tear:
Do you actually mean a guy named Bob?? :rofl: Ok, i get it.

2 Likes

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

tumbleweed.gif.d5ab39b50dcca50a7615cee0a4c7739a

The youngsters may not get it.

2 Likes

Just an example for something that would never be true :laughing:

2 Likes

2 Likes

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

1 Like