Content
View differences
Updated by Rosanna Sibora 27 days ago
Currently, OpenProject controls work package visibility primarily through project-level permissions and role-based access. However, there is no granular mechanism to restrict visibility of _individual_ work packages within a project. This creates challenges when a project contains a mix of public and confidential items (e.g., security vulnerabilities, HR-related tasks, or client-confidential issues) that should only be visible to a defined subset of project members.
Project members today see all work packages they have permission to view at the project level. There is no way to:
* Hide a specific work package from certain project members while keeping the rest of the project visible to them.
* Apply confidentiality rules consistently across multiple work packages.
* Allow the reporter or assignee of an issue to retain visibility regardless of group membership.
Project members today see all work packages they have permission to view at the project level. There is no way to:
* Hide a specific work package from certain project members while keeping the rest of the project visible to them.
* Apply confidentiality rules consistently across multiple work packages.
* Allow the reporter or assignee of an issue to retain visibility regardless of group membership.