ORGANIZATIONS(7)

💖 ORGANIZATIONS(7) 💖

okay so this is the organizations page from the big npm manual (we're living in the npm docs era, NPM@11.17.0, June 2026 if you're keeping receipts) and bestie, it's literally all about working with teams & organizations. let's get into it 🫶

---

✨ NAME ✨

Organizations — working with teams & organizations. that's the whole vibe. icon behavior only 👑

---

🌸 Description 🌸

so there are three levels of org users, and you need to know all three, no skipping:

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 (say it with me) it impacts the monthly bill 💀. the super admin will use the website to manage membership. and every org has a developers team that all users are automatically added to — automatic, no invite needed, slay.

the team admin is the person who manages team creation, team membership, and package access for teams. and lowkey important: the team admin grants package access to teams, not individuals. teams only. periodt.

the developer will be able to access packages based on the teams they are on. access is either read-write or read-only — two modes, that's it, that's the whole menu 🎀

and there are two main commands you'll be living in:

1. npm team — see npm help team for more details
2. npm access — see npm help access for more details

---

🦋 Team Admins create teams 🦋

• check who you've added to your org:

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. yes, you can change it, go off 💅
• create a new team:

npm team create <org:team>

• add members to that team:

npm team add <org:team> <user>

---

🌈 Publish a package and adjust package access 🌈

• in the package directory, run:

npm init --scope=<org>

to scope it for your org & publish as usual ✨

• grant access:

npm access grant <read-only|read-write> <org:team> [<package>]

• revoke access:

npm access revoke <org:team> [<package>]

ngl the <read-only|read-write> thing is not a suggestion — you literally pick one of those two words. and <package> is chillin' in square brackets for a reason, bestie 🙈

---

⭐ Monitor your package access ⭐

• see what org packages a team member can access:

npm access list packages <org> <user>

• see packages available to a specific team:

npm access list packages <org:team>

• check which teams are collaborating on a package:

npm access list collaborators <pkg>

the way these three commands are basically your group-chat read receipts for package permissions 😭 obsessed.

---

🎀 See also 🎀

• npm help team
• npm help access
• npm help scope

---

that's the whole page, no cap 💖 go forth and organize your org like the main character you are 👑✨

sign-off time: brought to you by NPM@11.17.0, dated June 2026, and reprinted (with extra sparkle) from ORGANIZATIONS(7) — stay scoped, stay slay 🦋