Team Support

The Team support feature allows you to group the users who work in a project, or users with similar roles, as a team. Using this feature, you can assign assets for each team and specify the access level of team members based on the team members' project requirements.

This feature is helpful for organizations that have multiple teams, who work on different projects. Users can access only the assets that are assigned to them. For example, consider an organization with different teams such as Development, Configuration Management, Product Analytics, and Quality Assurance. Each of these teams needs access to different assets at different levels. That is, developers would require APIs to develop applications and they require the necessary privileges to manage APIs and applications. Similarly, analysts would want the necessary privileges to view performance dashboards of assets. In such scenarios, you can group users based on their roles as a team and assign them the necessary privileges based on their responsibility.

Prior to the 10.5 version, users were given the necessary privileges using Access Profiles. Starting version 10.5, you can limit the access of your asset to the required team members and assign access privileges using the Team support feature. A team can be defined as a group of users with a set of defined responsibilities.

You can create teams from the User Management section of API Gateway by including the required user groups and assigning them the required functional privilege. You can also assign a Team administrator for each team, who can add or modify team members.

Users with the Manage user administration privilege can create teams. When creating a team, you can assign:

Team administrator. You can assign a user or a user group as team administrator. Team administrators can add or remove users from a team. When you assign a user group as team administrator, all users of the groups can modify team members. When team administrators, who do not have the Manage user administration functional privilege log on to API Gateway, they can view only the teams assigned to them in the Teams tab of the Administration page.

Functional privileges for the team members. The functional privileges assigned to a team determines the accessibility of assets to the respective team members. For example, if you assign all privileges under the APIs, Policies, and Applications section, then the team members can manage APIs and applications assigned to their teams and perform operations related to policies.

Team members. You can assign user groups to the team. Team members can access the assets assigned to their teams and perform operations on the assets based on their functional privileges.

After you have created teams, you can assign assets to teams in one of the following ways:

Assign team during asset creation. When you create an asset, API Gateway provides an option to select the teams for the asset. You can select more than one team for an asset. You can modify the teams assigned by following the Change ownership process explained in later part of this article.

Using Global Team Assignment rule. This is a preferred method to assign teams when you already have assets to which you want to assign teams to. You can create global assignment rules that are applied to assets and assign teams to them. You can specify one or more conditions in a rule. When an asset satisfies the conditions specified in a rule, the asset is assigned to the teams specified in the rule. When you create and activate a rule, the rule is applied to the existing assets and teams are assigned accordingly.

The team, Default, is available in API Gateway when the feature is enabled and all API Gateway users are added to this team by default. Assets, which are not assigned to any team, are assigned to the Default team. Hence, all API Gateway users can view the assets that are part of the Default team. However, users can perform actions on the assets based on the functional privileges assigned to them.