Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Put Simply: Introduce a permission setting that provide read only access to users during key lifecycle phases like project closure, Legal Hold, or compliance reviews.
Why it Matters: Enabling a read-only access provides tangible values in multiple ways:
Protects Data Integrity: Prevents Engagement team members from editing or deleting data during critical phases like project wrap-up or litigation hold.
Supports Oversight activities: Allows governance, risk, and compliance teams to access data non-disruptively for auditing, monitoring, and regulatory reviews.
Ensures consistent Compliance: Standardizes how projects transition into a secured state, helping teams meet legal and regulatory obligations more consistently.
Reduces manual intervention: Streamlines workflows by reducing the need for manual locking or uncoordinated team communications during transitions.
Additional Context: Jira already uses a read-only mode to manage post-project access. Introducing a similar state in Concourse would align platform behavior and improve governance. The feature should support assigning read-only access to specific users or roles (e.g., oversight reviewers) and also should be able to trigger read only state request to UC, to ensure that downstream integration systems can also transition to read only state.
Acceptance Criteria:
Ability to mark a Concourse workspace as “Read-Only”
When a workspace is in Read only state- all users should automatically have read only permissions
Users with read-only access can view and download content, but not edit or delete
Read-only access configurable by role (e.g., oversight team, internal users post-close)
Clear visual indicator in UI that workspace is read-only
Supporters: Ritu Raj Agrawal, Laura Utley, Nachiket Bal
Ritu Raj Agrawal
