1ORGS(7)                                                                ORGS(7)
2
3
4

NAME

6       orgs - Working with Teams & Orgs
7
8   Description
9       There are three levels of org users:
10
11       1. Super admin, controls billing & adding people to the org.
12
13       2. Team admin, manages team membership & package access.
14
15       3. Developer, works on packages they are given access to.
16
17
18       The super admin is the only person who can add users to the org because
19       it impacts the monthly bill. The super admin will use  the  website  to
20       manage  membership.  Every org has a developers team that all users are
21       automatically added to.
22
23       The team admin is the person who manages team  creation,  team  member‐
24       ship,  and  package access for teams. The team admin grants package ac‐
25       cess to teams, not individuals.
26
27       The developer will be able to access packages based on the  teams  they
28       are on. Access is either read-write or read-only.
29
30       There are two main commands:
31
32       1. npm team see npm help team for more details
33
34       2. npm access see npm help access for more details
35
36
37   Team Admins create teams
38       • Check who you’ve added to your org:
39
40
41         npm team ls <org>:developers
42
43       • Each org is automatically given a developers team, so you can see the
44         whole list of team members in your org. This team automatically  gets
45         read-write  access  to all packages, but you can change that with the
46         access command.
47
48       • Create a new team:
49
50
51         npm team create <org:team>
52
53       • Add members to that team:
54
55
56         npm team add <org:team> <user>
57
58   Publish a package and adjust package access
59       • In package directory, run
60
61
62         npm init --scope=<org>
63
64       to scope it for your org & publish as usual
65
66       • Grant access:
67
68
69         npm access grant <read-only|read-write> <org:team> [<package>]
70
71       • Revoke access:
72
73
74         npm access revoke <org:team> [<package>]
75
76   Monitor your package access
77       • See what org packages a team member can access:
78
79
80         npm access ls-packages <org> <user>
81
82       • See packages available to a specific team:
83
84
85         npm access ls-packages <org:team>
86
87       • Check which teams are collaborating on a package:
88
89
90         npm access ls-collaborators <pkg>
91
92   See also
93       • npm help team
94
95       • npm help access
96
97       • npm help scope
98
99
100
101
102                                 January 2022                          ORGS(7)
Impressum