10172e394bPR-URL: https://github.com/nodejs/node/pull/61892 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
98 lines
2.2 KiB
Markdown
98 lines
2.2 KiB
Markdown
---
|
||
title: Organizations
|
||
section: 7
|
||
description: Working with teams & organizations
|
||
---
|
||
|
||
### Description
|
||
|
||
There are three levels of org users:
|
||
|
||
1. Super admin, controls billing & adding people to the org.
|
||
2. Team admin, manages team membership & package access.
|
||
3. Developer, works on packages they are given access to.
|
||
|
||
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.
|
||
|
||
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.
|
||
|
||
The developer will be able to access packages based on the teams they are on.
|
||
Access is either read-write or read-only.
|
||
|
||
There are two main commands:
|
||
|
||
1. `npm team` see [npm team](/commands/npm-team) for more details
|
||
2. `npm access` see [npm access](/commands/npm-access) for more details
|
||
|
||
### Team Admins create teams
|
||
|
||
* Check who you’ve added to your org:
|
||
|
||
```bash
|
||
npm team ls <org>:developers
|
||
```
|
||
|
||
* 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.
|
||
|
||
* Create a new team:
|
||
|
||
```bash
|
||
npm team create <org:team>
|
||
```
|
||
|
||
* Add members to that team:
|
||
|
||
```bash
|
||
npm team add <org:team> <user>
|
||
```
|
||
|
||
### Publish a package and adjust package access
|
||
|
||
* In package directory, run
|
||
|
||
```bash
|
||
npm init --scope=<org>
|
||
```
|
||
to scope it for your org & publish as usual
|
||
|
||
* Grant access:
|
||
|
||
```bash
|
||
npm access grant <read-only|read-write> <org:team> [<package>]
|
||
```
|
||
|
||
* Revoke access:
|
||
|
||
```bash
|
||
npm access revoke <org:team> [<package>]
|
||
```
|
||
|
||
### Monitor your package access
|
||
|
||
* See what org packages a team member can access:
|
||
|
||
```bash
|
||
npm access list packages <org> <user>
|
||
```
|
||
|
||
* See packages available to a specific team:
|
||
|
||
```bash
|
||
npm access list packages <org:team>
|
||
```
|
||
|
||
* Check which teams are collaborating on a package:
|
||
|
||
```bash
|
||
npm access list collaborators <pkg>
|
||
```
|
||
|
||
### See also
|
||
|
||
* [npm team](/commands/npm-team)
|
||
* [npm access](/commands/npm-access)
|
||
* [npm scope](/using-npm/scope)
|