Concourse Feedback


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.


 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit CONC-I-1780 Removal of inactive users from Concourse ecosystem (Jira, Miro, SP, etc)..

User Inactivity Monitoring and Management Tool Merged

Put Simply: Develop a tool to automatically identify and remove inactive users (user no longer valid in Entra and/or no activity for a certain period) from Concourse and all integrations (Jira DC/Cloud, Miro, etc) to improve license efficiency and reduce loss of access to data and reduce IT issues..

Why it Matters: Currently, there is no automated way to remove Inactive Users which poses several risks and inefficiencies:

  • License Efficiency: Regaining licenses from inactive internal and external users can reduce costs and ensure optimal resource allocation.

  • Operational Risks: There are known issues with syncing and closing out integrations when an inactive user exist in a workspace

  • Security Risks: Users who are no longer part of the firm might still have access to sensitive engagements, posing security threats.

Acceptance Criteria

  • Detect Inactive Users

    • The system must automatically detect internal users who have left PwC or changed roles using Workday?/ PMDM

      • Users no longer in the firm should be removed from the workspace

    • The system must detect client users who are no longer registered or removed from the engagement.

      • Users no longer in the project should be removed from the workspace

  • Remove Inactive Users from Integrated Tools

    • When a user is inactive (30/60/90 days??) from any of the integrated systems, then automatically remove them from:

        • Jira (send email notification to the eng leader/ manager) with an ability to add them back to the integration from CC

        • Miro (remove access + soft delete boards for 30 days) with an ability to add them back to the integration from CC

        • Teams (remove from channels and disable links) with an ability to add them back to the integration from CC

  • Revoke license for the integrated systems

    • If a user is inactive in JIRA, Miro, or Teams for more than (30/60/90 days):

      • Send a notification to the user and their eng leader/ manager informing them of their inactivity.

      • Warn the user that they will be removed from JIRA or Miro (as applicable) if they do not log in within the next 7 days. ??

      • If there is still no activity after 7 days, remove the user from the respective system.

  • If a user has been removed from an integrated system, the engagement team should be able to add them back, if needed

  • If a user is inactive AND holds a mandatory role (e.g., Engagement Lead/ Manager), the system must block workspace closure.

    • Admins or another user must be able to reassign the role to an active user.

  • Notification

    • Workspace owners must receive email notification or banner messages when inactive users are detected.

    • Client users must receive automated emails when they are removed from Concourse.

    • Can we also maintain logs?

  • How to identify inactive users (mandatory), who have moved out of the project? Flex?

  • Kia Pourmodheji
  • May 28 2025
  • PM Refinement
Workspace Territory N/A