# Exploring private data management in Fibery

**URL:** <https://community.fibery.io/t/exploring-private-data-management-in-fibery/5864>\
**Category:** Misc\
**Created:** [February 17, 2024, 8:38pm UTC](https://community.fibery.io/t/exploring-private-data-management-in-fibery/5864 "2024-02-17T20:38:03Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [May 8, 2024, 9:25am UTC](https://community.fibery.io/t/exploring-private-data-management-in-fibery/5864/10 "2024-05-08T09:25:09Z")

</div>

For completeness, less recap what we have and what we are missing:

**Clarification of Current Permissions Setup**

- **Confirmed Use Case:** We’ve established that a financial officer can view and edit financial records of their own team, while not accessing the financial records of other teams.  
_ **However, the financial officer cannot create new financial records** _

**Limitations in Entity Creation Permissions**

- **Crucial Requirement Missing:** The ability for team roles to create entities within their own teams is not addressed. This capability is essential, especially in organizations where team-specific data generation is frequent.
- **Real-World Implications:** Without the option to assign creation rights within specific permissions templates, Fibery requires users to adopt a less efficient setup. This limitation complicates deployment in larger settings where dynamic data handling is necessary.

**Current Workaround and Its Challenges**

- **Separate Spaces for Each Team:**
  - To manage permissions effectively under the current system, organizations must create isolated spaces for each team.

- **Duplication of Databases:**
  - Each team space requires its own set of duplicated databases.
  - This includes duplicating project, task, and financial data databases individually for each team.

- **Impact:**
  - It’s not just an issue for larger projects but also for small teams, especially when a basic function like creating team-sensitive content is hindered.
  - Also, this limitation affects even single-team setups, where a finance officer should perform essential tasks without being able to view ALL content in the space (thus not be space member).

**With other words, Fibery currently requires an organization to have this setup:**

Space A  
Team (Shared database)  
A-Project (Unique database)  
A-Task (Unique database)  
A-FinancialData (Unique database)

Space B  
Team (Shared database)  
B-Project (Unique database)  
B-Task (Unique database)  
B-FinancialData (Unique database)

---

_[View the full topic](https://community.fibery.io/t/exploring-private-data-management-in-fibery/5864)._