Administration
Team management
Review team membership, roles, project access, and the process for people joining or leaving a team.
Overview
Team management covers collaboration workflows, ownership of applications and tests, assignment routing, and handoffs between QA and engineering. Teams map to Console visibility scopes and API resource filters.
Administrators structure teams to mirror organizational boundaries while avoiding excessive permission fragmentation.
Step-by-step procedure
Create teams
Admin Center → Teams → Create with name and description.
Assign team lead for assignment routing.
Link applications
Map applications to owning team for scoped Runs and Reports views.
Invite members
Admin Center → Users → Invite with role and team membership.
Design teams around responsibility and access
Identify who owns each application or workflow, who operates tests, who reviews changes, and who administers access. These responsibilities may belong to different people even when they sit in one organizational team.
Use the role and membership capabilities available in your deployment to represent that model. Confirm access with representative users rather than inferring it solely from a team name.
Review membership through its lifecycle
Establish a process for invitations, role changes, departures, and temporary external access. Assign an administrator to resolve pending invitations and remove access when it is no longer required.
Review service credentials and integrations when a team changes ownership. Removing a user does not necessarily retire every automation that user originally configured; check the actual credential lifecycle and operating owner.
Was this page helpful?