Those look promising. Iām particularly interested in:
To me permissions sharing in Fibery right now is a mess, especially in our multi tenant environment. I lost track how many times people complained to me about āI canāt see X, I donāt have access to Yā . Even when using a dummy account to simulate the rights of an user, itās far from a good solutions since there is no way for me to know for certain āwhat does this user have access to?ā
This is another sore point, especially when trying to manage logged / planned work.
Having to create Day entities (even if Chris shared such a template) still triggers all my āthis feels wrongā alarms.
Joining your comment, I was thinking about an idea for the team. What about creating a sort of āProject boardā that will regroup all admin stuff in one window and by project ?
Let say that the project Car uses 5 databases, in 3 different spaces. I would like to be able to open the Car admin project board and be able to change the permissions of each spaces and each databases that are linked.
Is there any chance one day an entity itself could be āsmartā (or smart folders just get smarter and more flexible?) with contextually filtered sub-smart folders underneath entities?
I love the concept/logic of smart folders, but itās frustrating how they can only live directly under spaces and you can only use them at a single level.
Hoping for something like this:
āClientsā Smart Folder (Top Level)
āClient Aā Entity
āProjectsā Smart Folder (Context filtered to āClient Aā)
āProject Aā Entity
āProject Bā Entity
āInvoicesā Smart Folder (Context filtered to āClient Aā)
āInvoice 1ā Entity
āInvoice 2ā Entity
āClient Bā Entity
āProjectsā Smart Folder (Context filtered to āClient Bā)
āProject Cā Entity
āProject Dā Entity
āInvoicesā Smart Folder (Context filtered to āClient Bā)
I donāt think you understand (or I just did a poor job articulating). Iād like smart folders to be able to be used at any level (not just under spaces like they are now) and Iād like to be able to have child smart folders within them that can have their own configuration.
The subheader/folder heading is extremely important as without it things start looking very overwhelming and disorganized!
In reality, Projects obviously arenāt actually called āProject Aā and Invoices arenāt actually called āInvoice 1ā. Most of our users have no idea or care what the database an entity lives in is called, or is colored, so they are lost trying to navigate the sidebar and I want to help them.
If you have multiple databases on the same level like your example, itās essentially the same as just dumping all the files on your computer into a single folder and sorting them by ātypeā.
Or if you want the databases on different levels, itās like putting them all in folders with no labels so you have to blindly open them to know whatās actually inside.
Maybe Iāve being a bit extreme with the comparisons, but can you see where Iāve coming from?
Yes, this would be useful. If I have a project with say 2 quotes, 4 workstages, 10 tasks, 2 sub-projects, 4 project contacts, etc., the ability to group those different sections together would be a huge QOL. (In reality, our projects are a lot more complex than that.)
I guess the work around at the moment would be to create another database that works as āfoldersā and link different items to different āfoldersā. So all invoices are related the the āInvoicesā āfolderā, for example.
One idea is to add Icon field to database and set emoji instead. Or you can even generate the same emoji for all database entities and it may look like folder of you like
Spot on, I think these areas target limitations Iāve experienced in Fibery. Polymorphism and type composition or inheritance are the biggest single missing piece from every productivity and enterprise OS software available today. Tana has made headway, but seems like itās being developed as an outline note taker, not an enterprise OS, so itās missing all the other critical features Fibery has.
Iād be happy to be a beta tester for any solution here (I also have some vague thoughts on how this could work). This would be a huge jump forward with the solution Iām currently building in Fibery and would allow us to market the solution to a much wider audience in legal & professional services.
