# \[IN DEV\] Fibery-to-Fibery workspaces integration

**URL:** <https://community.fibery.io/t/in-dev-fibery-to-fibery-workspaces-integration/2279>\
**Category:** Integrations\
**Created:** [December 1, 2021, 11:43am UTC](https://community.fibery.io/t/in-dev-fibery-to-fibery-workspaces-integration/2279 "2021-12-01T11:43:53Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [December 6, 2022, 1:58pm UTC](https://community.fibery.io/t/in-dev-fibery-to-fibery-workspaces-integration/2279/9 "2022-12-06T13:58:48Z")

</div>

Hi @cover  
I think your use case will be solvable when per-entity permissions are rolled out.

> [@\[DONE\] Entity-level permissions](https://community.fibery.io/t/planned-entity-level-permissions/2163):
>
> Why? So far all the [access management](https://help.fibery.io/en/articles/5350066-permissions) in Fibery happens on the App level. The only way to share an individual Entity (ex. a Task) with a teammate is via read-only [external sharing](https://help.fibery.io/en/articles/5303654-sharing-entities-and-documents) poop Introducing Entity-level permissions will unlock new opportunities: Collaborating with clients As we’ve learned, Fibery is a surprisingly good fit for many service companies: think digital agencies and development studios. A good fit, that is to say, before we start talking about access management. …

---

_[View the full topic](https://community.fibery.io/t/in-dev-fibery-to-fibery-workspaces-integration/2279)._