?HAMA

Edit File Size: 2.26 KB

/proc/self/root/opt/alt/alt-nodejs12/root/lib/node_modules/npm/docs/content/using-npm/orgs.md

Text Base64

---
section: using-npm
title: orgs
description: Working with Teams & Orgs
---

# orgs(7)

## Working with Teams & Orgs

### 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](/cli-commands/npm-team) for more details
2. `npm access` see [npm access](/cli-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 ls-packages <org> <user>
```

* See packages available to a specific team:

```bash
npm access ls-packages <org:team>
```

* Check which teams are collaborating on a package:

```bash
npm access ls-collaborators <pkg>
```

### See also

* [npm team](/cli-commands/npm-team)
* [npm access](/cli-commands/npm-access)
* [npm scope](/using-npm/scope)

Exit & Reset Text mode: syntax highlighting auto-detects file type.

Name	Size	Perms	Modified	Actions
config.md	32.05 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
developers.md	7.63 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
disputes.md	6.09 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
orgs.md	2.26 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
registry.md	4.04 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
removal.md	1.71 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
scope.md	4.35 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
scripts.md	10.60 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive
semver.md	15.44 KB	lrw-r--r--	2026-03-09 07:21:28	Edit Download recursive recursive

Directory Contents