ꦫꦣꦺꦤ꧀ꦄꦤ꧀ꦠꦱꦺꦤ

PATH: opt / bitninja-node-dojo / lib / node_modules / npm / docs / content / cli-commands

---
section: cli-commands 
title: npm-team
description: Manage organization teams and team memberships
---

# npm-team(1)

## Manage organization teams and team memberships

### Synopsis

```bash
npm team create <scope:team>
npm team destroy <scope:team>

npm team add <scope:team> <user>
npm team rm <scope:team> <user>

npm team ls <scope>|<scope:team>

npm team edit <scope:team>
```

### Description

Used to manage teams in organizations, and change team memberships. Does not
handle permissions for packages.

Teams must always be fully qualified with the organization/scope they belong to
when operating on them, separated by a colon (`:`). That is, if you have a `wombats` team in a `wisdom` organization, you must always refer to that team as `wisdom:wombats` in these commands.

If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.

* create / destroy:
  Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
* add / rm:
  Add a user to an existing team, or remove a user from a team they belong to.

* ls:
  If performed on an organization name, will return a list of existing teams
  under that organization. If performed on a team, it will instead return a list
  of all users belonging to that particular team.

* edit:
  Edit a current team.

### Details

`npm team` always operates directly on the current registry, configurable from
the command line using `--registry=<registry url>`.

In order to create teams and manage team membership, you must be a *team admin*
under the given organization. Listing teams and team memberships may be done by
any member of the organizations.

Organization creation and management of team admins and *organization* members
is done through the website, not the npm CLI.

To use teams to manage permissions on packages belonging to your organization,
use the `npm access` command to grant or revoke the appropriate permissions.

### See Also

* [npm access](/cli-commands/npm-access)
* [npm registry](/using-npm/registry)

[-] npm-build.md [edit]
[-] npm-bundle.md [edit]
[-] npm-prune.md [edit]
[-] npm-repo.md [edit]
[-] npm-owner.md [edit]
[-] npm-edit.md [edit]
[-] npm-audit.md [edit]
[-] npm-unpublish.md [edit]
[-] npm-bin.md [edit]
[-] npm-test.md [edit]
[-] npm-run-script.md [edit]
[-] npm-completion.md [edit]
[-] npm-adduser.md [edit]
[+] ..
[-] npm-deprecate.md [edit]
[-] npm-link.md [edit]
[-] npm-root.md [edit]
[-] npm-dist-tag.md [edit]
[-] npm-update.md [edit]
[-] npm-start.md [edit]
[-] npm-config.md [edit]
[-] npm-hook.md [edit]
[-] npm-token.md [edit]
[-] npm-pack.md [edit]
[-] npm-stars.md [edit]
[-] npm-publish.md [edit]
[-] npm-whoami.md [edit]
[-] npm-install-ci-test.md [edit]
[-] npm-prefix.md [edit]
[-] npm-shrinkwrap.md [edit]
[-] npm.md [edit]
[-] npm-install-test.md [edit]
[-] npm-version.md [edit]
[-] npm-team.md [edit]
[-] npm-fund.md [edit]
[-] npm-restart.md [edit]
[-] npm-star.md [edit]
[-] npm-ci.md [edit]
[-] npm-ls.md [edit]
[-] npm-explore.md [edit]
[-] npm-view.md [edit]
[-] npm-dedupe.md [edit]
[-] npm-cache.md [edit]
[-] npm-uninstall.md [edit]
[-] npm-ping.md [edit]
[-] npm-install.md [edit]
[-] npm-access.md [edit]
[-] npm-help-search.md [edit]
[-] npm-help.md [edit]
[-] npm-org.md [edit]
[-] npm-init.md [edit]
[-] npm-logout.md [edit]
[-] npm-doctor.md [edit]
[-] npm-stop.md [edit]
[-] npm-bugs.md [edit]
[-] npm-rebuild.md [edit]
[-] npm-docs.md [edit]
[-] npm-profile.md [edit]
[-] npm-outdated.md [edit]
[-] npm-search.md [edit]