ORGANIZATIONS(7)

💖 NAME 💖

Organizations — all about working with teams & organizations, bestie 🫶

---

✨ DESCRIPTION ✨

Okay so real talk: there are three levels of org users, and you gotta know which one you are 👑

1. Super admin — controls billing & adding people to the org.
2. Team admin — manages team membership & package access.
3. Developer — works on packages they're given access to.

The super admin is the only person who can add users to the org, because it literally 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 — no cap, automatic 🌟.

The team admin is the person who manages team creation, team membership, and package access for teams. And this is the key part: the team admin grants package access to teams, not individuals. iykyk 🎀

The developer will be able to access packages based on the teams they are on. Access is either read-write or read-only. That's the whole vibe check 🔥

There are two main commands, and honestly? These are your besties:

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. slay 💅
• 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 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>]

---

🍓 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>

---

🎀 SEE ALSO 🎀

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

---

ngl bestie, if you forget everything else, remember: super admin = billing & people, team admin = teams & package access, developer = the packages their teams gave them. periodt 💜

That's the whole page! Brought to you by NPM@12.2.1, dated October 2026 — go be iconic with your orgs 🧚‍♀️⭐