from small one page howto to huge articles all in one place
 

search text in:





Poll
Which kernel version do you use?





poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

133968

userrating:

average rating: 1.7 (87 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

239409

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

120493

userrating:

average rating: 1.3 (28 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





NPM\-ORGS

Section: (7)
Updated: December 2016
Index Return to Main Contents
 

NAME

npm-orgs - 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 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.
*
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 ls-packages <org> <user>
*
See packages available to a specific team:

npm access ls-packages <org:team>
*
Check which teams are collaborating on a package:

npm access ls-collaborators <pkg>
 

SEE ALSO

*
npm help team
*
npm help access
*
npm help 7 scope


 

Index

NAME
DESCRIPTION
Team Admins create teams
Publish a package and adjust package access
Monitor your package access
SEE ALSO





Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2018 Sascha Nitsch Unternehmensberatung UG(haftungsbeschränkt)
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 20.4 ms