deprecate-totp-2fa
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: About the developers team |
| 3 | --- |
| 4 | |
| 5 | The "**developers**" team is automatically created when you create an organization. By default, the developers team has read/write access to all new packages created under the organization's scope. |
| 6 | |
| 7 | - Members added to the organization, including the organization owner, are automatically added to the **developers** team |
| 8 | - The [`maintainers` field] in the [`package.json`] of any newly created packages under the organization scope is automatically populated with the members of the current **developers** team |
| 9 | |
| 10 | If you create a new package under your organization's scope and you do not want members of the **developers** team to have read/write access to that package, an owner or admin can remove the **developers** team's access to that package. For more information, see "[Managing team access to organization packages][pkg-access]". |
| 11 | |
| 12 | If an owner adds a new member to an organization and **does not** want that member to be on the **developers** team, an owner can remove them. |
| 13 | |
| 14 | <Note> |
| 15 | |
| 16 | **Note:** The **developers** team can no longer be removed from an organization for the following reasons: |
| 17 | |
| 18 | - It is the source of truth for all users, packages, and default permissions in an organization. |
| 19 | - When you want to restrict write access, it is almost always better to set the default permissions to read-only and create separate teams for managing write permissions. |
| 20 | |
| 21 | </Note> |
| 22 | |
| 23 | [pkg-access]: managing-team-access-to-org-packages |
| 24 | [create-team]: creating-teams |
| 25 | [`maintainers` field]: /files/package.json#people-fields-author-contributors |
| 26 | [`package.json`]: /files/package.json |