1 npm-team(1) -- Manage organization teams and team memberships
2 =============================================================
6 npm team create <scope:team>
7 npm team destroy <scope:team>
9 npm team add <scope:team> <user>
10 npm team rm <scope:team> <user>
12 npm team ls <scope>|<scope:team>
14 npm team edit <scope:team>
18 Used to manage teams in organizations, and change team memberships. Does not
19 handle permissions for packages.
21 Teams must always be fully qualified with the organization/scope they belond to
22 when operating on them, separated by a colon (`:`). That is, if you have a
23 `developers` team on a `foo` organization, you must always refer to that team as
24 `foo:developers` in these commands.
27 Create a new team, or destroy an existing one.
30 Add a user to an existing team, or remove a user from a team they belong to.
33 If performed on an organization name, will return a list of existing teams
34 under that organization. If performed on a team, it will instead return a list
35 of all users belonging to that particular team.
39 `npm team` always operates directly on the current registry, configurable from
40 the command line using `--registry=<registry url>`.
42 In order to create teams and manage team membership, you must be a *team admin*
43 under the given organization. Listing teams and team memberships may be done by
44 any member of the organizations.
46 Organization creation and management of team admins and *organization* members
47 is done through the website, not the npm CLI.
49 To use teams to manage permissions on packages belonging to your organization,
50 use the `npm access` command to grant or revoke the appropriate permissions.