Sorry for the unclear use of terminolgy. What refer to is actually ‘visibility access’ and your answer is on Fibery’s entity-level action control. Fibery can manage what a user can do to an entity, but not entirely whether they can see it .
In this post I focused mainly on the individual ‘private data’ but I realize that this will soon already be possible when the next level of ‘entity level permisisons’ is rolled out in Q1/Q2 this year. See AntonioKovs comment here
This is likely the most wanted feature in Fibery as far as I can see. Because of:
- HR Information: Employee records, performance reviews, salary data, health information. Limiting visibility ensures only authorized HR personnel have access.
- Financial Data: Detailed financial reports, budgets, and internal projections should be restricted to relevant teams and executives.
- Client Data: Protecting client contact information, project details, and confidential agreements requires visibility restrictions.
- Intellectual Property: Safeguarding trade secrets, patents, and development plans often necessitates strict visibility controls.
Whether visibility access is enough
If Fibery implements visibility access as expected, users will be able to manage data privacy more effectively; they could restrict who can see specific entities. Still:
- Admins might still have overarching access.
- Visibility control isn’t the same as encryption. For extremely sensitive data, additional security measures may be needed.
I will close this topic because at least visibility access is already on the roadmap, and that may shed light on further features regarding sensitive data.