Problem Statement
Instana currently provides team management capabilities only through administrative permissions that apply across all teams. Organizations with many application teams often want to delegate ownership and maintenance of specific teams to local leaders while maintaining centralized governance.
Today, if a user needs the ability to update team settings, modify team scope, add or remove members, or manage team-related configurations, they must be granted permissions that provide visibility and administrative capabilities beyond their own team. This creates operational bottlenecks because platform administrators become responsible for every team change request, even when those requests should be handled directly by the owning team.
This limitation reduces self-service capabilities and increases administrative overhead for large enterprises managing dozens or hundreds of teams.
Proposed Enhancement
Introduce a Team Lead or Team Administrator role that is scoped to a specific Instana team.
Users assigned this role should be able to:
- Manage members within their assigned team
- Modify team scope and assigned application perspectives
- Maintain team-related configurations and permissions
- Manage integrations or resources associated with their team
- Perform team administration tasks without requiring access to other teams
The role should be restricted to the team(s) explicitly assigned to the user and should not grant tenant-wide administrative privileges
Business Value
This enhancement would provide:
Improved Self-Service
- Application owners and team leads could manage their own teams without requiring intervention from Instana administrators.
Reduced Administrative Overhead
- Platform administrators would no longer be a bottleneck for routine team-management activities such as membership updates, scope changes, or application ownership transitions.
Better Governance
- Organizations could delegate responsibility while maintaining security boundaries. Team leads would only be able to manage their designated teams and would not receive global team administration privileges.
Increased Adoption
- Teams would have greater ownership of their Instana configuration, improving agility and encouraging broader platform adoption across large enterprises.
Example Use Case
An enterprise has 100+ Instana teams supporting different business applications.
The central observability team wants the manager or technical lead of each application team to:
- Add and remove users from their team
- Adjust team scope when new services are onboarded
- Update application perspectives relevant to their organization
Currently, only Instana administrators can perform these actions across all teams. A Team Administrator role would allow delegated management of a single team while preserving security and separation of duties.
This is on our roadmap as the next bigger iteration on the Teams feature and is aligned with our goals to provide more self-service capabilities to teams without admin overhead, while assuring that scope limitations and "need to know" aspects are maintained.
We're currently focusing on adding more granular access to core areas, like Infrastructure, Logs and genAI observability, but are planning to follow up with this "team manager" or granular user and team configuration access work afterwards.
Considering this, I don't currently expect this work to be completed in 2026.