Teams

Teams let developers collaborate on API products. A team maps to an Apigee AppGroup. Team apps are owned by the AppGroup, not by a member’s personal developer record. Membership and roles can differ per workspace when the team spans more than one Apigee organization.

Where to find it

Open Teams in the portal sidebar (the page is titled My Teams). Logged-in developers see teams they own and a Teams I’m a Member Of section.

Teams do not create portal accounts

Invite Member adds someone who already has a portal user. Create accounts first under Configuration → Users (Add User, registration, or Sync Developers). Inviting an email that is not in the portal fails — only existing users can be invited to teams.

Create a team

From My Teams, click New Team (or Create Your First Team when the list is empty). You need a connected Apigee organization.

Display Name — required. The human-readable name (for example Engineering Team).
Team Name — required. Internal identifier (alphanumeric and underscores). It is generated from the display name; you can edit it before you save.

You do not pick a workspace on create. The team is provisioned into the organizations its apps and members need. Cards show those workspaces as chips.

Team details

Open a team. Tabs (capitalized in the UI):

View — description, workspaces, created and last updated.
Edit — display name and description. Visible to team owners and admins.
Delete — owners only. Removes members, team apps, and team metadata. This cannot be undone.
Members — who is on the team, and in which workspaces.
Team Apps — apps owned by the team. See Developer Apps and Multi-Organization.

Members

Owners and admins click Invite Member. Enter the email of an existing portal user, choose a team role, and — when the team spans more than one workspace — choose where they can work. Being on the team does not grant every workspace it occupies.

After a successful add, the portal can email a team-member invitation when SMTP is configured. That message is a notification, not an account-creation invite.

Team roles

These are team roles, not portal roles from Configuration → Users. A person can be a Developer on the portal and an Owner on one team.

Member — always included. Collaborate on the team; cannot invite or change members.
Admin — manage members and settings. Can assign Admin or Member, not Owner.
Owner — full team management, including assigning Owner and deleting the team. Only an owner can grant Owner, and only in workspaces they themselves own.

On a multi-workspace team, open Edit Team Member to change the role in each workspace you are allowed to manage. To change where they have access at all, remove them or invite them again. Remove Member takes them off the team.

Portal roles vs team roles

Portal roles (Administrator, Developer, and any custom role) are assigned on Users and control what the person can do in the portal. Team roles control what they can do on that team. See Role-Based Access.