Go to main content

man pages section 7: Standards, Environments, Macros, Character Sets, and Miscellany

Exit Print View

Updated: Wednesday, February 9, 2022
 
 

orgs (7)

Name

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 member- ship, 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 o Check who you've added to your org: npm team ls <org>:developers o 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. o Create a new team: npm team create <org:team> o Add members to that team: npm team add <org:team> <user> Publish a package and adjust package access o In package directory, run npm init --scope=<org> to scope it for your org & publish as usual o Grant access: npm access grant <read-only|read-write> <org:team> [<package>] o Revoke access: npm access revoke <org:team> [<package>] Monitor your package access o See what org packages a team member can access: npm access ls-packages <org> <user> o See packages available to a specific team: npm access ls-packages <org:team> o Check which teams are collaborating on a package: npm access ls-collaborators <pkg> See also o npm help team o npm help access o npm help scope

Synopsis

Please see following description for synopsis

Description

ORGS(7)                                                                ORGS(7)



NAME
       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  member-
       ship,  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
       o Check who you've added to your org:


         npm team ls <org>:developers

       o 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.

       o Create a new team:


         npm team create <org:team>

       o Add members to that team:


         npm team add <org:team> <user>

   Publish a package and adjust package access
       o In package directory, run


         npm init --scope=<org>

       to scope it for your org & publish as usual

       o Grant access:


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

       o Revoke access:


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

   Monitor your package access
       o See what org packages a team member can access:


         npm access ls-packages <org> <user>

       o See packages available to a specific team:


         npm access ls-packages <org:team>

       o Check which teams are collaborating on a package:


         npm access ls-collaborators <pkg>

   See also
       o npm help team

       o npm help access

       o npm help scope




ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       +---------------+--------------------------+
       |ATTRIBUTE TYPE |     ATTRIBUTE VALUE      |
       +---------------+--------------------------+
       |Availability   | runtime/nodejs/nodejs-16 |
       +---------------+--------------------------+
       |Stability      | Pass-thru volatile       |
       +---------------+--------------------------+

NOTES
       Source code for open source software components in Oracle  Solaris  can
       be found at https://www.oracle.com/downloads/opensource/solaris-source-
       code-downloads.html.

       This    software    was    built    from    source     available     at
       https://github.com/oracle/solaris-userland.    The  original  community
       source   was   downloaded   from     https://github.com/nodejs/node/ar-
       chive/v16.11.1.zip.

       Further information about this software can be found on the open source
       community website at https://github.com/nodejs/node.



                                 October 2021                          ORGS(7)