# Atlas Organization Teams > Source-anchored research for Atlas Organization Teams. Run status: COMPLETED. Parent: [MongoDB Atlas IAM and RBAC](https://llms-explorer.com/tree/mongodb-atlas-iam-and-rbac/) · 3 facets · 16 facts · page: https://llms-explorer.com/tree/atlas-organization-teams/ ## Problems, failure modes and limitations - The v4.17.1 Pulumi Team reference, published October 13, 2026, demonstrates team configuration with `orgId`, `name`, and `usernames`; the page marks `usernames` deprecated and says it will be removed in the next major release. This is evidence of Pulumi tooling, not an independent source for Atlas permission semantics. (low confidence) (verified as of 2026-10-24) — [source](https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/team/) - In Atlas Kubernetes Operator issue #3359, a user who upgraded from v1 to v2.14.1 found duplicate entries in AtlasTeam.status.projects. On May 20, 2026, the maintainer and reporter narrowed this to retained historical duplicates: manual cleanup stopped the symptom and subsequent reconciles did not grow the list. The thread does not establish active growth in a fresh v2.14.1 deployment or an Atlas authorization failure. (low confidence) — [source](https://github.com/mongodb/mongodb-atlas-kubernetes/issues/3359) - The CLI reference documents `atlas teams rename --teamId ` with optional `--orgId`. Its existence conflicts with the management guide's statement that the CLI cannot rename teams; runtime behavior was not tested. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-teams-rename.md) - Pulumi's mongodbatlas.Team v4.17.1 reference marks the usernames attribute deprecated and recommends mongodbatlas.CloudUserTeamAssignment for managing team membership. (low confidence) (verified as of 2026-10-13) — [source](https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/team/) ## Comparisons and alternatives - Enzo documents its own MongoDB adapter handlers CreateTeam, AddTeamUsers, DeleteTeam, GetTeams, and GetTeamUsers, with organization-scoped identifiers. Its configuration example targets Atlas API v1.0, so it is integration evidence rather than current API-v2 guidance. (low confidence) — [source](https://www.enzounified.com/docs/adapter-mongodb) - Terraform issue #879, opened October 20, 2022, records a team data-source naming mismatch that produced Reference to undeclared resource for data.mongodbatlas_team.developers.team_id. Treat this as historical configuration/documentation evidence rather than an ongoing Atlas service defect. (low confidence) — [source](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/879) ## Facts and statements - Atlas teams group organization users so administrators can assign project roles in bulk. A user can belong to multiple teams, and a team can serve multiple projects with project-specific access. (high confidence) — [source](https://www.mongodb.com/docs/atlas/access/manage-teams-in-orgs.md) - Creating a team alone does not grant its members project access: administrators must add the team to the project. Members then share the project roles assigned to that team. (high confidence) — [source](https://www.mongodb.com/docs/atlas/access/manage-teams-in-orgs.md) - Atlas teams govern Atlas user access. Atlas users and database users are separate identities; team membership does not itself create database-user credentials. (medium confidence) — [source](https://www.mongodb.com/docs/atlas/organizations-projects.md) - The documented limits are 250 teams per organization, 100 teams per project, and 250 Atlas users per team. Pulumi's resource reference repeats these limits; it is not an independent measurement. (high confidence) (verified as of 2026-10-13) — [source](https://www.mongodb.com/docs/atlas/access/manage-teams-in-orgs.md) - The CLI provides atlas teams create, atlas teams list, and atlas teams users add. Creation accepts usernames, while adding users to an existing team takes user IDs and a team ID. (high confidence) — [source](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-teams.md) - The current CLI command reference and command index document atlas teams rename. The rename command takes a new name and --teamId, supports --orgId, and documents Organization Owner authentication. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-teams-rename.md) - Teams group users within an Atlas organization. Users can belong to multiple teams, and adding a team to a project grants its members the team's project access roles. (high confidence) — [source](https://www.mongodb.com/docs/atlas/access/manage-teams-in-orgs.md) - A team can be assigned to multiple projects. Its project role determines members' access in each project; team creation must be followed by project assignment to grant that access. (high confidence) — [source](https://www.mongodb.com/docs/atlas/organizations-projects.md) - The team-management guide requires Organization Owner access for its operations; the CLI rename reference likewise requires Organization Owner authorization. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/access/manage-teams-in-orgs.md) - Enzo's MongoDB adapter documents CreateTeam with organization ID, name, and optional usernames. Its AddTeamUsers operation accepts organization ID, team ID, and user IDs, illustrating that team creation and membership are separate automation operations. (low confidence) — [source](https://www.enzounified.com/docs/adapter-mongodb)