Skip to main content

Teams

Teams group members for policy and solution access. They reduce repeated direct assignments and make responsibility visible.

Create a team​

Open Organization → Teams, select create, and enter:

  • a distinctive name;
  • color used in the interface;
  • description of responsibility;
  • initial members.

Example:

Name: Lending Test Analysts
Color: Blue
Description: Owns regression testing for Lending HubItems in Development and Test. No production deployment access.

Grant access through policies​

Create a policy that assigns the appropriate role and scope:

Team: Lending Test Analysts
Role: Test Analyst
Solution: Lending

The role can grant Hub view, saved-test management, and Test-environment run/debug permissions without granting HubItem editing or deployment execution.

Manage membership​

Add and remove users as responsibilities change. Effective access is additive, so review the member's direct policies and other teams before concluding that removal from this team fully revokes a permission.

Do not create overlapping teams with unclear ownership. A small set of responsibility-based teams is easier to audit than one team per individual task.

Review checklist​

  • Team description still reflects its actual responsibility.
  • Every member still needs the access.
  • Policies point to the correct solution and role.
  • Production/debug permissions remain appropriately restricted.
  • Departed or inactive users are removed from the organization, not only the team.