# \[DONE\] Many-to-many relationships should be usable for levels in lists

**URL:** <https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624>\
**Category:** Ideas & Features\
**Tags:** list-view\
**Created:** [May 13, 2021, 4:29pm UTC](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624 "2021-05-13T16:29:07Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [February 1, 2022, 5:18pm UTC](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624/16 "2022-02-01T17:18:33Z")

</div>

This is very exciting 😁

@mdubakov I had two questions:

1. Will this apply to all hierarchical structures (i.e. both hierarchical lists and smart folders)?

2. Is there a chance that as part of the implementation, the more complex nested relations would also be addressed? By this I mean something like:

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

Or the following example:

> [@Representing nested relations](https://community.fibery.io/t/representing-nested-relations/1405/10):
>
> Just wanted to add another example of this type of nested relation in the area of project management (as defined by PMBOK):
> 
> - A **project** is a temporary endeavor undertaken by a company or organization (such as the creation of a new product, service, or result)
> - A **program** is a group of projects that are similar or related to one another, and which are often managed and coordinated as a group instead of independently
> - A **portfolio** is a group of different programs and/or projects within the same organization, which may be related or unrelated to one another
> 
> Portfolios will be the top layer, but then both programs and individual/stand-alone projects would be nested inside the portfolio. The programs in turn would have some nested projects. I’ve modeled it in Fibery like this:
> 
> ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3337275c8bd52c3149565f39acaad88e236d0d5a.png)

There was a discussion with @Chr1sG around this [as part of this thread](https://community.fibery.io/t/representing-nested-relations/1405/15) which I think might be helpful in illustrating what is desired and some ideas on how it might be possible.

---

_[View the full topic](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624)._