Skip to content

Managing team access to organization packages

As an organization owner or team admin, you can add or remove package access to or from teams in your organization.

Adding package access to a team

Adding package access to a team on the web

  1. Log in to npm with your user account.
    Screenshot of npm login dialog
  2. In the upper right corner of the page, click your profile picture, then click Profile Settings.
    Screenshot of profile settings selection in user menu
  3. In the left sidebar, click the name of your organization.
    Screenshot of a selected organization
  4. On the organization settings page, click Teams.
    Screenshot of the organization teams tab
  5. Beside the team to which you want to add package access, click Packages.

    Screenshot of the packages button
  6. On the "Add Packages" page, in the "Package" field, type the name of the package and select from the dropdown menu.

    Screenshot of the package selection
  7. Click + Add Existing Package.

    Screenshot of the add package button
  8. Beside the package name, click read or read/write to set the team permissions for the package.

    Screenshot of the team package permission option

Adding package access to a team using the CLI

As an organization owner or team admin, you can use the the CLI access command to add package access to a team on the command line:

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

For more information, see "npm-access".

Removing package access from a team

Removing package access from a team on the web

  1. Log in to npm with your user account.
    Screenshot of npm login dialog
  2. In the upper right corner of the page, click your profile picture, then click Profile Settings.
    Screenshot of profile settings selection in user menu
  3. In the left sidebar, click the name of your organization.
    Screenshot of a selected organization
  4. On the organization settings page, click Teams.
    Screenshot of the organization teams tab
  5. Beside the team from which you want to remove package access, click Packages.

    Screenshot of the packages button
  6. Beside the name of the package from which you want to remove access, click x.

    Screenshot of the remove package button

Removing package access from a team using the CLI

As an organization owner or team admin, you can also use the the CLI access command to revoke package access from a team on the command line:

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

For more information, see "npm-access".

Changing package access for a team

Changing package access for a team on the web

  1. Log in to npm with your user account.
    Screenshot of npm login dialog
  2. In the upper right corner of the page, click your profile picture, then click Profile Settings.
    Screenshot of profile settings selection in user menu
  3. In the left sidebar, click the name of your organization.
    Screenshot of a selected organization
  4. On the organization settings page, click Teams.
    Screenshot of the organization teams tab
  5. Beside the team from which you want to remove package access, click Packages.

    Screenshot of the packages button
  6. Beside the package name, click read or read/write to set the team permissions for the package.

    Screenshot of the change package permission option

Changing package access for a team from the CLI

As an organization owner or team admin, you can change package access for a team from the command line:

npm access

For more information, see the npm-access CLI documentation.