03 - Roles | npm Documentation

Roles

Organizations are first and foremost a way to manage access, roles and resposibilities. Organizations offer 3 types of roles, and also have an interface with the general public:

Super-Admin

The user who creates the Organization is automatically set as the Super Admin.

can see/do everything regarding their org
can pay for the org
can add users to the org (team-admin or developer)

Currently, only one Super Admin is allowed and the Super Admin User cannot be changed. New versions of our Orgs product will make this possible.

Team-Admin

Team Admins are set by the Super Admin in the website interface. There can be >=0 Team Admins.

can see teams
can add a new org-scoped package
can add a pre-existing package
cannot pay
cannot add/remove users to/from org
can add/remove users to/from teams

Member

Members are added to teams by the Organizations Super Admin or Team Admin.

can see the teams they're on
can see the packages associated with those teams
can add a new org-scoped
cannot pay
cannot add users

General Public

While not associated with the Organization, the general public has some ability to interact with Organizations.

can see the org exists
can see public packages in the org's domain
cannot see private packages
cannot see members
cannot do anything for the org (manage members, teams, packages, billing, etc)

Last modified December 29, 2015 Found a typo? Send a pull request!

Getting Started

How npm works

Private Modules

Organizations

Using npm

coding-style npm's "funny" coding style
config More than you probably want to know about npm configuration
developers Developer Guide
disputes Handling Module Name Disputes
orgs Working with Teams & Orgs
registry The JavaScript Package Registry
removing-npm Cleaning the Slate
scope Scoped packages
scripts How npm handles the "scripts" field
semver The semantic versioner for npm

npm On-Site

CLI Commands

access Set access level on published packages
adduser Add a registry user account
bin Display npm bin folder
bugs Bugs for a package in a web browser maybe
build Build a package
bundle REMOVED
cache Manipulates packages cache
completion Tab Completion for npm
config Manage the npm configuration files
dedupe Reduce duplication
deprecate Deprecate a version of a package
dist-tag Modify package distribution tags
docs Docs for a package in a web browser maybe
edit Edit an installed package
explore Browse an installed package
help Get help on npm
help-search Search npm help documentation
init Interactively create a package.json file
install Install a package
install-test
link Symlink a package folder
logout Log out of the registry
ls List installed packages
npm javascript package manager
outdated Check for outdated packages
owner Manage package owners
pack Create a tarball from a package
ping Ping npm registry
prefix Display prefix
prune Remove extraneous packages
publish Publish a package
rebuild Rebuild a package
repo Open package repository page in the browser
restart Restart a package
root Display npm root
run-script Run arbitrary package scripts
search Search for packages
shrinkwrap Lock down dependency versions
star Mark your favorite packages
stars View packages marked as favorites
start Start a package
stop Stop a package
tag Tag a published version
team Manage organization teams and team memberships
test Test a package
uninstall Remove a package
unpublish Remove a package from the registry
update Update a package
version Bump a package version
view View registry info
whoami Display npm username

Configuring npm

folders Folder Structures Used by npm
npmrc The npm config files
package.json Specifics of npm's package.json handling