@cryptotaxi247 / documentation
Code Commits Issues Pulls Sessions CI/CD
reggi/dev-engines
@reggi/path-to-regexp dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2 dependabot/npm_and_yarn/main/eslint-10.4.0 dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0 dependabot/npm_and_yarn/main/proc-log-7.0.0 dependabot/npm_and_yarn/npm_and_yarn-826852524d dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2 deprecate-totp-2fa dhei/classic-tokens gat-bypass-2fa-docs jpg619/fix-accessibility-content-flow jpg619/version-bump-tar-2 kartykp/gat-bypass-2fa-docs kartykp/upgrade-path-to-regex main maitxn/version-bump-tar patch-1 reggi/cache-based-on-version reggi/dev-engines reggi/fix-transform-prettier reggi/overrides update-search-sensitivity
mdx 107 lines 2.58 KB
Raw
1 ---
2 title: orgs
3 section: 7
4 description: Working with Teams & Orgs
5 github_repo: npm/cli
6 github_branch: latest
7 github_path: docs/lib/content/using-npm/orgs.md
8 redirect_from:
9 - /cli-documentation/misc/orgs
10 - /cli-documentation/using-npm/orgs
11 - /cli-documentation/v10/misc/orgs
12 - /cli-documentation/v10/using-npm/orgs
13 - /cli/misc/orgs
14 - /cli/using-npm/orgs
15 - /cli/v10/misc/orgs
16 - /misc/orgs
17 - /using-npm/orgs
18 ---
19
20 ### Description
21
22 There are three levels of org users:
23
24 1. Super admin, controls billing & adding people to the org.
25 2. Team admin, manages team membership & package access.
26 3. Developer, works on packages they are given access to.
27
28 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 `developers` team that all users are automatically added to.
29
30 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.
31
32 The developer will be able to access packages based on the teams they are on. Access is either read-write or read-only.
33
34 There are two main commands:
35
36 1. `npm team` see [npm team](/cli/v10/commands/npm-team) for more details
37 2. `npm access` see [npm access](/cli/v10/commands/npm-access) for more details
38
39 ### Team Admins create teams
40
41 - Check who you’ve added to your org:
42
43 ```bash
44 npm team ls <org>:developers
45 ```
46
47 - Each org is automatically given a `developers` 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 `access` command.
48
49 - Create a new team:
50
51 ```bash
52 npm team create <org:team>
53 ```
54
55 - Add members to that team:
56
57 ```bash
58 npm team add <org:team> <user>
59 ```
60
61 ### Publish a package and adjust package access
62
63 - In package directory, run
64
65 ```bash
66 npm init --scope=<org>
67 ```
68
69 to scope it for your org & publish as usual
70
71 - Grant access:
72
73 ```bash
74 npm access grant <read-only|read-write> <org:team> [<package>]
75 ```
76
77 - Revoke access:
78
79 ```bash
80 npm access revoke <org:team> [<package>]
81 ```
82
83 ### Monitor your package access
84
85 - See what org packages a team member can access:
86
87 ```bash
88 npm access ls-packages <org> <user>
89 ```
90
91 - See packages available to a specific team:
92
93 ```bash
94 npm access ls-packages <org:team>
95 ```
96
97 - Check which teams are collaborating on a package:
98
99 ```bash
100 npm access ls-collaborators <pkg>
101 ```
102
103 ### See also
104
105 - [npm team](/cli/v10/commands/npm-team)
106 - [npm access](/cli/v10/commands/npm-access)
107 - [npm scope](/cli/v10/using-npm/scope)