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)