| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146 | .TH "ORGS" "7" "August 2021" "" "".SH "NAME"\fBorgs\fR \- Working with Teams & Orgs.SS Description.PThere are three levels of org users:.RS 0.IP 1. 3Super admin, controls billing & adding people to the org\..IP 2. 3Team admin, manages team membership & package access\..IP 3. 3Developer, works on packages they are given access to\.  .RE.PThe 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\..PThe 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\..PThe developer will be able to access packages based on the teams they are on\. Access is either read\-write or read\-only\..PThere are two main commands:.RS 0.IP 1. 3\fBnpm team\fP see npm help team for more details.IP 2. 3\fBnpm access\fP see npm help access for more details.RE.SS Team Admins create teams.RS 0.IP \(bu 2Check who you’ve added to your org:.RE.P.RS 2.nfnpm team ls <org>:developers.fi.RE.RS 0.IP \(bu 2Each 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\..IP \(bu 2Create a new team:.RE.P.RS 2.nfnpm team create <org:team>.fi.RE.RS 0.IP \(bu 2Add members to that team:.RE.P.RS 2.nfnpm team add <org:team> <user>.fi.RE.SS Publish a package and adjust package access.RS 0.IP \(bu 2In package directory, run.RE.P.RS 2.nfnpm init \-\-scope=<org>.fi.RE.Pto scope it for your org & publish as usual.RS 0.IP \(bu 2Grant access:  .RE.P.RS 2.nfnpm access grant <read\-only|read\-write> <org:team> [<package>].fi.RE.RS 0.IP \(bu 2Revoke access:.RE.P.RS 2.nfnpm access revoke <org:team> [<package>].fi.RE.SS Monitor your package access.RS 0.IP \(bu 2See what org packages a team member can access:.RE.P.RS 2.nfnpm access ls\-packages <org> <user>.fi.RE.RS 0.IP \(bu 2See packages available to a specific team:.RE.P.RS 2.nfnpm access ls\-packages <org:team>.fi.RE.RS 0.IP \(bu 2Check which teams are collaborating on a package:.RE.P.RS 2.nfnpm access ls\-collaborators <pkg>.fi.RE.SS See also.RS 0.IP \(bu 2npm help team.IP \(bu 2npm help access.IP \(bu 2npm help scope.RE
 |