Granular View Permissions (Group-based visibility)

@ID.000 You spent a lot of time detailing a lack of functionality that, in my humble opinion, is glaring. Obviously, proliferating spaces and using smart folders to get around this issue are both tedious to set up, maintain, and use, plus the sidebar can grow substantially depending on how the implementation occurs. As you observed, I’m unclear on how Fibery is going to accommodate large teams. CADSharp is only 25 people and this is already causing issues.

Hi! Totally agree, this is still a pain for us too, though mostly for admins :grinning_face:

Our admins already have a huge number of spaces in the sidebar, one for each team (even small).
We can’t group them into folders just for admins, because those folders would then show up for team members too, and their sidebar would immediately look cluttered. So we made a conscious choice: better for admins to be inconvenienced than the teams :grimacing: .

Overall it’s a pain we’ve learned to live with, because so much else in Fibery is really convenient and great. Hopefully this gets addressed at some point! :face_holding_back_tears:

I have some kind of idea around this, but it is missing 1 thing from the Custom Apps platform:
Either a “close this panel” function, or a “redirect main app to” function.

Then you could build a Meta Fibery to Fibery sync (similar to Chris’s Meta Data sync he made in the past), which syncs the Spaces and Views.

Then the Views database has a custom entity view app, which all it does it redirect you to the actual view in Fibery when you open it.

This then means you can relate the view to your own “Folder” or “User” or “Team” database with a many to many relation, then have a smart folder show the “View” database related to what that user needs to see, and when they press on it, they get redirected to the actual Fibery view. Allowing you add more meta data to views. It almost works now, but it opens within the entity, which isn’t ideal.

You could already do this (integrate views and add meta data for view assignments) and make it filtered and openable with a custom app which would act as a “Home page” with the views which are related to the user / this user’s user group. But then this replaces the sidebar.

@ID.000 I’d be quite interested to see if this solves your use case! Reach out if you wanna look into this together.

Thanks a lot for the idea, @RonMakesSystems !:grinning_face:

To be honest, we’ve already tried a few approaches like this, including a database of views linked to teams and users. We didn’t like it in the end :melting_face: . It’s a workaround that makes navigation noticeably more complicated. We have a lot of matrix-like overlaps between teams, and an extra layer of “who is linked to which view” added more chaos for us :grimacing: .

What we have now isn’t always convenient, but it’s transparent: it’s always clear who can see what. For us that matters more.

One approach that does help us in some areas is a custom app that checks who opened it and shows a view tailored to that person. We build it once and embed it, and every user sees their own version. It’s not ideal: you don’t always want to build a custom app to replace a standard view, and it has to be maintained. But in a few places it really saves us :upside_down_face: .

So in the long run, native hard links to views (or view-level permissions) would still be the real solution for us we think :grinning_face: .

In terms of user experience? If, upon opening the View entity, it would auto redirect to the actual view, would that not be just as simple as opening a view? Then those views can either be in smart folders in the sidebar, or have a Custom App which is kind of like the Launchpad for all views specific to that user, and when clicked, it opens the view itself.

It this what you mean with this? ^^

Isn’t this also what would happen once there will be view-level permissions?


The biggest down-side with this is that technically the users have permissions to the views, it just doesn’t clutter up their sidebar.