1 .TH "NPM\-ORGS" "7" "October 2016" "" ""
3 \fBnpm-orgs\fR \- Working with Teams & Orgs
6 There are three levels of org users:
9 Super admin, controls billing & adding people to the org\.
11 Team admin, manages team membership & package access\.
13 Developer, works on packages they are given access to\.
17 The super admin is the only person who can add users to the org because it impacts the monthly bill\. The super admin will use the website to manage membership\. Every org has a \fBdevelopers\fP team that all users are automatically added to\.
19 The team admin is the person who manages team creation, team membership, and package access for teams\. The team admin grants package access to teams, not individuals\.
21 The developer will be able to access packages based on the teams they are on\. Access is either read\-write or read\-only\.
23 There are two main commands:
26 \fBnpm team\fP see npm help team for more details
28 \fBnpm access\fP see npm help access for more details
31 .SH Team Admins create teams
34 Check who you’ve added to your org:
40 npm team ls <org>:developers
45 Each org is automatically given a \fBdevelopers\fP team, so you can see the whole list of team members in your org\. This team automatically gets read\-write access to all packages, but you can change that with the \fBaccess\fP command\.
53 npm team create <org:team>
58 Add members to that team:
64 npm team add <org:team> <user>
67 .SH Publish a package and adjust package access
70 In package directory, run
76 npm init \-\-scope=<org>
80 to scope it for your org & publish as usual
89 npm access grant <read\-only|read\-write> <org:team> [<package>]
100 npm access revoke <org:team> [<package>]
103 .SH Monitor your package access
106 See what org packages a team member can access:
112 npm access ls\-packages <org> <user>
117 See packages available to a specific team:
123 npm access ls\-packages <org:team>
128 Check which teams are collaborating on a package:
134 npm access ls\-collaborators <pkg>