Concourse & Jira DC Portal

Put Simply: Introduce an admin role to manage user access, especially for support and oversight teams.

Why it Matters: Support teams often encounter roadblocks when assisting with workspace issues because they lack the necessary access. This leads to delays in resolving problems, creating inefficiencies and frustration for engagement teams. Additionally, when engagement leadership changes, there is no standardized process to update user access ( CONC-I-1780), often resulting in outdated permissions, communication breakdowns, and security risks.

Oversight teams-such as OGC, ECR, and Risk & Governance-also face challenges when conducting reviews or investigations( CONC-I-2170). These reviews are meant to be confidential, but current workflows require oversight teams to request access directly from the engagement team, which defeats the purpose and compromises the integrity of the review process. Admin users can help with their access as well.

Additionally, in the future, as part of the workspace closure process, once a workspace is moved to the archived state, only users with admin access will be able to view and unarchive it if needed.

Today's system lacks a secure, centralized, and auditable way to manage user access. Introducing a clearly defined admin role would:

• Enable faster and more effective support,

• Ensure accurate and timely updates during leadership transitions, and

• Empower oversight teams to carry out their responsibilities discreetly and efficiently.

Additional Context: Admin users would enable support teams to access inactive or archived workspaces. They would also handle role updates for engagement leads and managers and approve oversight team access when requested.

Acceptance Criteria:

• Admin users can access any workspace regardless of status

• Admins can assign or update user roles and permission

• Admins will be treated as Super users

• Admins can approve access requests from oversight teams

• Admin can view archived workspaces (future req)

• Admin can unarchive workspaces when archived

• Maintain audit log