# Combine databases (e.g. projects of different groups)

**URL:** <https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577>\
**Category:** Get Help\
**Created:** [June 8, 2023, 11:38pm UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577 "2023-06-08T23:38:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [June 8, 2023, 11:38pm UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577/1 "2023-06-08T23:38:50Z")

</div>

I like to have multiple groups have similar setups like projects and tasks, but each groups has its own group user and content permissions. This means that projects and tasks can only be seen if you are member of that group.

I also want to have a master list of all projects and tasks of all groups, and it should only show those that I am allowed to see.

I can’t see how to create such master list in Fibery since it probably needs combining of databases.  
Or, if you can think of another configuration that does not require combining of databases, let me know.

Any suggestions? Thanks!

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [June 9, 2023, 12:07am UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577/2 "2023-06-09T00:07:28Z")

</div>

I just found this feature in dev, about granual permissions…will this be helpful in my case? [[IN DEV] Entity-level permissions](https://community.fibery.io/t/in-dev-entity-level-permissions/2163)

---

<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:** [June 9, 2023, 7:37am UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577/3 "2023-06-09T07:37:33Z")

</div>

Almost certainly, yes, it will address your use case.

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [June 9, 2023, 4:31pm UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577/4 "2023-06-09T16:31:31Z")

</div>

Thank you. This is similar to the need of separate teams or departments in an organization, which often have some similar basic infrastructure (projects, tasks, documents).

Until that is implemented in Fibery, I think it is limited to only single teams, thus not as advertised in for example the blog [https://fibery.io/blog/fibery-vs-clickup/](https://fibery.io/blog/fibery-vs-clickup/) which assumes its suitable for medium company, while Clickup is much more scalable with finegrained permissions.

---

<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:** [June 9, 2023, 6:28pm UTC](https://community.fibery.io/t/combine-databases-e-g-projects-of-different-groups/4577/5 "2023-06-09T18:28:44Z")

</div>

There are companies with several hundred employees using Fibery successfully, so I don’t think the current permission capabilities are fundamentally limiting for every case.  
Certainly, for companies that want to limit access/visibility within the organization, then the current space-based permissions model may not be ideal.