Team Management

Authorization

What are teams?

A team is a collection of users, groups, and other teams that already exist. Unlike users and groups, teams are not stored in LDAP. The nesting depth of teams is unlimited, but cycles are not allowed. To control authorization to resources, you can associate teams with them, such as desktops in Navigator or apps in Studio.

Identifying teams across different environments

A team assignment is specific to the environment (development, test, production) you specify it in. When you move resources between environments, the teams associated with the resources are not automatically moved too. Instead, you must create corresponding teams in the target environment, if they do not already exist. However, because creating a team in multiple environments with the same team name and for the same purpose will have different unique team IDs (UUID), it might not be easy to identify corresponding teams just by their display name, which is not guaranteed to be unique, for example, many teams might be named "managers".

To avoid confusion, use team distinguished names (which are guaranteed to be unique in a given environment) consistently across all your environments to identify teams that serve the same purpose. This will make it easier to identify the correct team in a target environment and map it to the resources that you deploy.

Using multiple email addresses

When the user repository contains multiple email addresses for a user, by default, only the primary email address of the user is returned, for example when using the REST API call GET /teamserver/rest/users. But you can search for users that match with an alternative email address.