The Team API now returns richer team context

The new Grafana Team API will return richer team context. When you query a team through the new API, the response will include the team’s members and its external group mappings as part of the Team resource itself, so a single call will give you a complete picture of the team.

Team members will come back with the team. Membership used to be managed through a separate TeamBinding object and was visible only to team administrators. Members will become part of the Team resource, under spec.members, and the /teams/{name}/members and /users/{name}/teams endpoints will read from there. Anything that reads a team will get its members in the same response.

External group mappings will come back with the team. This is an Enterprise feature. External group mappings used to be managed only through the legacy /api/teams/{uid}/groups endpoint and were visible only to team administrators. They will become part of the Team resource, under spec.externalGroups. The field may appear on any Team as an empty list, but will only be used with Grafana Enterprise.

One thing to update if you already use the groups endpoint. The /teams/{name}/groups endpoint will return a plain list of group names (externalGroups: [string]) instead of the previous list of {name, externalGroup} objects. If you have an integration that reads this endpoint, update it to handle the new response before the change reaches your instance.

What is not changing. This affects the new Team API only. The Grafana UI will work exactly as before. The legacy /api endpoints that the current UI relies on will be served by the new API under the hood, but will not return the new fields. The extra data will be returned only when you query the new Team API directly. There will be no visible change in the product interface.

Why we’re making this change. Team membership and external group mappings are core parts of a team’s definition. Keeping them on the Team resource makes the Team API the single source of truth, so anything that reads a team gets a complete and consistent picture instead of stitching together separate objects and endpoints.

What to check before this rolls out.

• If you consume /teams/{name}/groups, update your client to handle the new externalGroups: [string] response shape.
• After writing spec.externalGroups, read the values back from the server. Grafana normalizes them on save (trimmed, lowercased, sorted), so the stored form may differ from what you submitted.
• Member and external group data that was previously visible only to team administrators will become part of the Team resource. If you treat membership or group mappings as sensitive, review who can read Team resources in your instance.