We don’t Fibery-to-Fibery sync and are not sure when it will appear
We also have some big customers (like ~600 teammates) - they started working in different workspaces but ended up in a structured one
Permissions + Hidden spaces have to work, and your ability to structure the data and configure Fibery - I’m pretty sure will make a magic
I think that Fibery needs to step up its game in the way collaborative technologies are rapidly becoming decentralized now. Fibery is a monolithic app that yes has integrations, but that is the minimum to expect nowadays. The next steps is to become modular and make the community contribute modules for Fibery, as well as to support Fibery to Fibery database connections.
The current topic is about multiple departments using different Fibery Workspaces, but I think we should look ahead and see the tech trends as well as the opportunity of Fibery to align with that, instead of trying to accomodate invididual organizations only.
For the readers here who are interested in that decentralized and networked development, see this related topic where we can continue the talk about that evolution:
I would likely have arrived at this question myself in time. Did you ever get an answer? I guess I wonder if you’re the admin (or creator) and you create a view using the appropriate filters to show only the allowed tasks for a given space and make it read-only, are the viewers of that space still able to change the filter to see all global tasks?
The current permissions model only allows granularity at the space level, so if you can see/edit one entity in a database in a space, you can see/edit every entity in all databases in that space (with a caveat about contributor level permissions which isn’t important for this discussion).
And this means you can find anything in that space via api and search.
For the upcoming permissions model, granularity will be down to the entity level (eventually including levels in between). So you can have view/edit permissions for ‘X’ and you will only be able to view/edit ‘X’ where X can be a space, a database, or an entity.
And the search/API behaviour will reflect those permissions.
If you mean, the use case in the first post of this topic “sharing a space/db among multiple workspaces” then, no, it is not part of the plans for permissions.
Workspaces are independent from each other, and we have no active plans to change that.