Grant a team read-write publish access to a scoped npm package via npm access

domain: npm · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Confirm you hold the privilege to change access: be an owner of the package, a member of the team that owns the scope, or hold read-write access on it (via npm owner ls).
  2. Ensure npm is authenticated as your registry account (npm whoami should return your username; npm login if it does not).
  3. Run the grant against the registry that owns the package: npm access grant read-write <scope:team> <package-spec>. Example for team dev of scope myorg on package my-scope-name-here.
  4. With two-factor authentication enabled on your account, provide the one-time code via the interactive prompt or pass it inline with the otp option: npm access grant read-write myorg:dev myorg hello --otp=123456.
  5. Verify: have the team member run npm access list collaborators <package> or install and publish to confirm the level is applied.
  6. Official docs: https://docs.npmjs.com/cli/v10/commands/npm-access

Known gotchas

Related routes

Grant a team read-only access to a scoped npm package via npm access
npm · 5 steps · unrated
Publish a scoped npm package as private with --access restricted
docs.npmjs.com · 4 steps · unrated
Publish a scoped npm package from a workspace monorepo to the npm registry
docs.npmjs.com · 7 steps · unrated

Give your agent this knowledge — and 16,900+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans