1 ---
2 title: npm-team
3 section: 1
4 description: Manage organization teams and team memberships
5 github_repo: npm/cli
6 github_branch: release/v6
7 github_path: docs/content/commands/npm-team.md
8 redirect_from:
9 - /cli-documentation/v6/cli-commands/npm-team
10 - /cli-documentation/v6/cli-commands/team
11 - /cli-documentation/v6/commands/npm-team
12 - /cli-documentation/v6/commands/team
13 - /cli-documentation/v6/npm-team
14 - /cli-documentation/v6/team
15 - /cli/v6/cli-commands/npm-team
16 - /cli/v6/cli-commands/team
17 - /cli/v6/commands/team
18 - /cli/v6/npm-team
19 - /cli/v6/team
20 ---
21
22 ### Synopsis
23
24 ```bash
25 npm team create <scope:team>
26 npm team destroy <scope:team>
27
28 npm team add <scope:team> <user>
29 npm team rm <scope:team> <user>
30
31 npm team ls <scope>|<scope:team>
32
33 npm team edit <scope:team>
34 ```
35
36 ### Description
37
38 Used to manage teams in organizations, and change team memberships. Does not handle permissions for packages.
39
40 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.
41
42 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.
43
44 - create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
45 - add / rm: Add a user to an existing team, or remove a user from a team they belong to.
46
47 - 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.
48
49 - edit: Edit a current team.
50
51 ### Details
52
53 `npm team` always operates directly on the current registry, configurable from the command line using `--registry=<registry url>`.
54
55 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.
56
57 Organization creation and management of team admins and _organization_ members is done through the website, not the npm CLI.
58
59 To use teams to manage permissions on packages belonging to your organization, use the `npm access` command to grant or revoke the appropriate permissions.
60
61 ### See Also
62
63 - [npm access](/cli/v6/commands/npm-access)
64 - [npm registry](/cli/v6/using-npm/registry)