Team
The Team detail page shows a team's members, its service accounts, and the permissions the team holds on resources. Account Owners and Admins reach it from Account Settings › USERS & TEAMS; other users find their teams in Profile › TEAMS.
Every member of the account can open the detail of any team and see its members. The PERMISSIONS tab and the Service Accounts card are shown only to the team's members and to account Owners and Admins. What you can change depends on your team permission level.
Header
The header shows the team's basic information:
| Field | Description |
|---|---|
| Created | The user who created the team and the creation timestamp |
| Description | A short description of the team; editable via the pencil icon |
| Admins | The team's admins |
Choose Action offers Add Permission, Add Member, Create Service Account and Delete Team — depending on your rights: managing the team is for account Admins and team Admins, creating service accounts also for team Service Account Managers.
Team permission levels
Each member holds one or more levels on the team:
| Level | What it allows |
|---|---|
| Member | Belongs to the team and gets everything granted to the team. Sees the team's members, service accounts and permissions. |
| Admin | The team's owner: manages members and their levels, and manages the team's service accounts. |
| Service Account Manager | Manages the service accounts owned by the team (create, edit their permissions and mode, tokens, API keys, secrets, disable, delete). Does not manage members. |
Member is always set for every member and cannot be removed; Admin and Service Account Manager are added on top of it. Account Owners and Admins can do everything a team admin can. In the API the levels are member, admin and service-account-manager.
Rules that keep a team manageable:
- A team always keeps an admin. The last admin of a team cannot be removed or lose the admin level — make another member admin first.
- Nobody can remove their own admin level or remove themselves while they are an admin. Another admin (or an account Owner/Admin) has to do it.
In the UI the locked Admin chip and the disabled Remove action explain this with You can't remove your own admin permission. or A team must keep at least one admin. — these apply to account Admins too. The API returns 409 with these error codes:
| Error code | Message |
|---|---|
TEAM_LAST_ADMIN | User <user> is the last admin of team '<team>'; make another member admin first |
TEAM_OWN_ADMIN_REMOVAL | You cannot remove yourself from team '<team>' while you are its admin; another admin has to do it — or You cannot remove your own admin permission on team '<team>'; another admin has to do it |
The levels viewer and edit-permissions no longer exist. Former viewers are members.
The user who creates a team becomes its first member and admin. Teams are created with Create New Team in Account Settings › USERS & TEAMS (name: must start with a letter; letters, numbers, underscore and dash; at most 30 characters). Through the API, holders of the account permission Team Creator can create teams too.
Members
The MEMBERS tab lists the team's users and, in a separate Service Accounts card, the team's service accounts.
Users
Columns: Username, Full Name, Email, Permission (the member's levels) and actions Edit Permissions and Remove.
- + Add Member — search and select any number of users (up to 50 are listed; users already in the team are not offered), pick the Permissions that apply to all of them, and confirm. The result is reported per user — if some users cannot be added, the others are still added and the failed ones stay selected for a retry.
- Edit Permissions — change a member's Admin / Service Account Manager levels (account Admins and team Admins). This is possible in the CodeNOW UI only; the public API and the MCP server can set levels only when adding members.
- Remove — removes the user from the team together with the permissions the user held on the team.
Only users can be members of a team. Teams and all users cannot be added to a team.
Service Accounts
Lists the service accounts owned by the team, with links to their detail. A service account belongs to a team only through ownership — it is added by creating it for the team (or moving it to the team) and leaves the team when it is moved to another owner or deleted.
Service accounts owned by this team inherit the team's permissions on other resources. They hold no permission on the team itself. Team Admins and Service Account Managers can create service accounts here (Create Service Account); every team member sees the list.
Permissions
The PERMISSIONS tab lists all resources the team has been granted permissions on. Team members and account Owners/Admins can see it. Each row shows:
| Column | Description |
|---|---|
| Name | The resource (application, component, template, environment, etc.) |
| Permissions | The permission groups assigned to the team for that resource |
| Source | The origin of the permission assignment |
Use + Create New Permission to grant the team access to an additional resource. Whether you can grant the team a permission on a resource depends on your rights on that resource (Permission Editor or Admin on it), not on your level in the team; the resource picker offers only resources you may grant on. Filter the list by Resource Type to narrow down the view.
Deleting a team
Deleting a team also revokes the team's permissions. A team that owns service accounts cannot be deleted — delete its service accounts or move them to another owner first.