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.
Asset Filtering logic : Currently, a single PDM task are linked to multiple delivery teams, which in turn have associated accelerators. However, all teams linked to the task can see all associated accelerators(since majority accelrators are tech agnostic), even if they did not specifically request them. This creates an issue where teams may have access to assets beyond their intended scope, increasing the risk of unintended exposure and inefficiencies in asset management.
Option 1: Asset Visibility Filtering via Metadata: Enhance the data model to include a mapping that links Accelerators to specific Delivery Teams within the same task.
Option 2: Include an additional field in the asset attribute to handle this
Option 3: Task-Level Segmentation by Delivery Team : Instead of a single Task linking multiple Delivery Teams, create separate tasks for each team