# 🌰 Fibery major conceptual (yet) unsolved problems

**URL:** <https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995>\
**Category:** News & Announcements\
**Created:** [December 20, 2024, 10:51am UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995 "2024-12-20T10:51:00Z")\
**Posts on this page:** 15\
**Page:** 2

<div class="post-metadata">

**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\
**Post date:** [January 8, 2025, 3:26pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/21 "2025-01-08T15:26:44Z")

</div>

Those look promising. I’m particularly interested in:

> [@mdubakov](#):
>
> Permissions & Sharing

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?”

> [@mdubakov](#):
>
> Dates as Databases.

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.

---

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [January 8, 2025, 4:31pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/22 "2025-01-08T16:31:50Z")

</div>

> [@Mircea\_Braescu](#):
>
> 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?”

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.

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [January 8, 2025, 5:41pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/23 "2025-01-08T17:41:53Z")

</div>

> [@mdubakov](#):
>
> Nested Spaces (and make Spaces optional, so it will be possible to mix Spaces, Views, Smart Folders on a top level)

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”)
      - “Invoice 3” Entity
      - “Invoice 4” Entity

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [January 8, 2025, 5:57pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/24 "2025-01-08T17:57:43Z")

</div>

You can already do this with regular Smart Folders - you just put all the levels you want in the Folder Configuration:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/65d57c888dafd693062c6396e63941af5866a414.png)

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [January 8, 2025, 6:32pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/25 "2025-01-08T18:32:32Z")

</div>

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.

My request:

- Smart Folder (Top Level)
  - Entity
    - Smart Folder
      - Entity and/or View

What you’re showing:

- Space (Top Level)
  - Smart Folder
    - Entity (Multiple Levels)
      - Views

---

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [January 8, 2025, 6:32pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/26 "2025-01-08T18:32:46Z")

</div>

What?! I didn’t know you could do this! I must’ve totally missed this functionality somehow … off to build something cool with this…

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [January 8, 2025, 7:26pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/27 "2025-01-08T19:26:49Z")

</div>

How does what you need differ from what is possible already (apart from specific ‘subheadings’ for Projects/Invoices)?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/47a71a299324e720ec4aac8c47b00562c9b6ae4d.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9423bde6e0f563ed932b4d7389001918a5d04de1.png)

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [January 8, 2025, 11:01pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/28 "2025-01-08T23:01:17Z")

</div>

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?

[I’ve been calling what I’m hoping for “nested” or “sub” smart folders which is maybe overcomplicating things.](https://community.fibery.io/t/allow-smart-folders-sections-to-be-nested-inside-of-other-smart-folders-sections/6429) I really just need the option to display the levels in a smart folder as “folders” or “groups” or “sections” or anything better than the ugly and useless shared icon/database abbreviation thing that we’ve got now. We have grouping on list and table views, so why can’t the same concept be done as an option in the main sidebar?

---

<div class="post-metadata">

**Author:** ![Bronn](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@Bronn](https://community.fibery.io/u/Bronn)\
**Post date:** [January 9, 2025, 9:28am UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/29 "2025-01-09T09:28:57Z")

</div>

> [@interr0bangr](#):
>
> I really just need the option to display the levels in a smart folder as “folders” or “groups”

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.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [January 9, 2025, 9:56am UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/30 "2025-01-09T09:56:44Z")

</div>

> [@interr0bangr](#):
>
> [I’ve been calling what I’m hoping for “nested” or “sub” smart folders which is maybe overcomplicating things.](https://community.fibery.io/t/allow-smart-folders-sections-to-be-nested-inside-of-other-smart-folders-sections/6429) I really just need the option to display the levels in a smart folder as “folders” or “groups” or “sections”

I think you hit the nail on the head.  
Seems to be a UI problem, rather than a fundamental failing of the smart folder concept.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [January 9, 2025, 10:00am UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/31 "2025-01-09T10:00:29Z")

</div>

> [@interr0bangr](#):
>
> I really just need the option to display the levels in a smart folder as “folders” or “groups” or “sections” or anything better than the ugly and useless shared icon/database abbreviation thing that we’ve got now

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

 ![Screenshot 2025-01-09 at 11.59.24 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5dace1549c93cea5cb97f8a46bad514d5f4095bb.png)

---

<div class="post-metadata">

**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\
**Post date:** [February 1, 2025, 8:48pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/32 "2025-02-01T20:48:40Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![karthikk\_vijay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/karthikk_vijay/32/1220_2.png) [@karthikk\_vijay](https://community.fibery.io/u/karthikk_vijay)\
**Post date:** [July 7, 2025, 8:59am UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/33 "2025-07-07T08:59:55Z")

</div>

> [@Ryan\_Dejaegher](#):
>
> CRM/People databases come to mind. Every person has an email field, but family may have “birthdate” fields, while client may have more business oriented fields

Tana has nailed this one with their supertags btw

---

<div class="post-metadata">

**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\
**Post date:** [July 7, 2025, 7:19pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/34 "2025-07-07T19:19:39Z")

</div>

> [@mdubakov](#):
>
> Can’t hide information from Admin (and Private Databases)

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.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 8, 2026, 1:21pm UTC](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995/35 "2026-10-08T13:21:30Z")

</div>

> [@timothy](#):
>
> ’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.

now you can hide data from admins! [October 8, 2026 / 🫣 Hide Space data from Admins](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389/1)

[Previous page](https://community.fibery.io/t/fibery-major-conceptual-yet-unsolved-problems/7995.md?page=1)
