Web-published space URLs

Get Help
1

I’m trying out the web publishing for the first time and I’ve run into a few things:

  1. Despite getting separate share URLs from each published space, all published spaces appear when any of those URLs is used. Is this expected behavior? (I hope not.) :frowning:
  2. Filters configured in the views define default view states and are not available to the web user. Is there another way for web visitors to filter by field values?

Thank you!

2
  1. Yes it is, I’m afraid. A publicly shared space is hosted alongside all other publicly-shared spaces from the same workspace
  2. Non logged-in users can’t affect the filters on views
3

Can I ask the rationale behind providing unique URLs for each published space that then all feed into the same view? I’m not getting the point of this.

My issue is that I have seperate published views for different clients, and it makes no sense for them all to be visible to everyone.

I guess I’m ultimately hoping for something as powerful as Baserow’s Application Builder, which would address both of these concerns. :frowning:

4

Publicly shared spaces follow the form of https://workspace.fibery.io/@public/spacename

(you can add the suffix ?show-only-current-space-in-menu to not show the other spaces, but if a user strips that, or just types https://workspace.fibery.io/@public they will see everything)

Are you talking about some other form of sharing?

In general, public space sharing is not intended to be used in the case where you want to hide information from certain people. If you want different people to see different things (and some people to not see certain things) then you should not use public sharing, but consider inviting people to be users, maybe as Guests or Observers

5

This would be fine, but that’s not what I’m seeing. As soon as the page leads, I see all web-published spaces, regardless of the URL used to open the page. I’ve tried this using “incognito” windows, too, just in case it was about me being logged in. Same result in Chrome and Safari.

image
image1026×598 47.9 KB

In the screenshot attached, the “TRU” space is different from the BERLIN space, yet it’s visible even when the “BERLIN” URL is used. And when I load the page using the “TRU” URL, it loads that view, but the BERLIN one remains visible. For the record, I get the same effect even if I omit the space name entirely. So, basically, it’s like there’s no point in having the different URLs. In fact, I can add nonsense to the end of the URL and still see the same thing.

In my case, these aren’t sensitive content items that require specific user permissions. The issue is one of user confusion rather than security.

6

Sorry I wasn’t clear - yes, the urls are different in that they indicate the name of the space being shared, but this merely has the effect of choosing which space to open. If multiple spaces have been shared, they do indeed all live in the same publicly shared workspace and can all be seen at the same time.
It’s basically no different to what happens if you go to a space url without the @public part - you get taken to a particular space in the workspace, but the other spaces in the sidebar aren’t hidden from you.

In other words, enabling public sharing of a space does not create a specific view for only that space, it just makes that space visible to anonymous users who visit the @public version of the workspace (no matter what url they use to get there)