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
