When setting up SEI one of the biggest challenges we face is the manual effort required to define teams. Today, we need to explicitly repositories, service/pipelines and projects into the configuration, which doesn’t scale well for an organization of our size. What we’d like to see is Intelligent Team Definition i.e. the ability for SEI to automatically infer and populate team settings based on the data it already has from our integrations (SCM, Project Management, CI/CD, etc.). For example: Identify contributors or developers and their repositories automatically from commit/PR activity. Auto-map services and pipelines from Harness or other CI/CD integrations. The system should propose these team definitions automatically, allowing us to accept, fine-tune, or override them. This would solve three key problems for us at EY: Onboarding speed: new teams should be ready to go with minimal manual setup. Data accuracy: avoid errors or incomplete team definitions when done manually. Scale: with hundreds of teams, manual setup simply doesn’t work. In short, we’d like SEI to use the data it already has to do the heavy lifting and make team setup intelligent, accurate, and scalable.
