Capabilities
The connector syncs the members of a single npm organization as users, the
organization itself as a group carrying the
developer, admin, and owner
role entitlements, and every team in the organization as a group carrying a
member entitlement. Organization role assignments and team memberships are
synced as grants.
Gather npm credentials
1
Sign in to npmjs.com as a user with owner or admin
access to the target organization.
2
Go to Access Tokens in your account settings and create a Granular
Access Token. Grant it read access and scope it to the organization you
want to sync. (Granular access tokens are the supported token type; a
classic automation token with organization access also works.)
3
Copy the generated token and note the organization name (the value after the
@ in a scoped package name, e.g. my-org in @my-org/pkg).Configure the npm connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your npm connector is now pulling access data into C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for npm and click Add.
3
Choose how to set up the new npm connector.
4
Set the owner for this connector.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the npm credentials:
- Access token: the npm access token you created.
- Organization: the npm organization scope to sync (e.g.
my-org).
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
npm has no global, cross-organization user directory, so each connector instance
syncs a single organization. To govern multiple npm organizations, add one
connector per organization.