Skip to content

[Update] docs: update access token creation instructions #1774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Update] docs: update access token creation instructions #1774

wants to merge 1 commit into from

Conversation

@jpg619
Copy link
Contributor

@jpg619 jpg619 commented Nov 13, 2025 •
edited
Loading

WHAT

Improvements to token creation steps:

  • Moved the "Expiration" field step to later in the process and updated its description to clarify that users can select from predefined options or specify a custom expiration date, with an added note about the minimum date requirement.
  • Reordered and renumbered the steps for configuring allowed IP ranges, package/scope access, and organization access for better logical flow and clarity.

WHERE

Modified on: https://docs.npmjs.com/creating-and-viewing-access-tokens

jpg619
jpg619 commented Nov 13, 2025
View reviewed changes
...t/integrations/integrating-npm-with-external-services/creating-and-viewing-access-tokens.mdx

<Screenshot src="/integrations/integrating-npm-with-external-services/tokens-profile.png" alt="Screenshot of the account menu with the tokens link selected" />

2. Click **Generate New Token**, then click **Granular Access Token**.
Copy link
Contributor Author

@jpg619 jpg619 Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

jpg619
jpg619 commented Nov 13, 2025
View reviewed changes
...t/integrations/integrating-npm-with-external-services/creating-and-viewing-access-tokens.mdx

_**Note**: When you give a token access to an organization, the token can only be used for managing organization settings and teams or users associated with the organization. It does not give the token the right to publish packages managed by the organization._

9. In the **Expiration** field, select a token expiration period from the dropdown menu. You can choose from predefined options or select Custom to specify a custom expiration date using the date picker.
Copy link
Contributor Author

@jpg619 jpg619 Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

@jpg619 jpg619 self-assigned this Nov 13, 2025
@jpg619 jpg619 marked this pull request as ready for review November 13, 2025 18:06
@jpg619 jpg619 requested review from a team and leobalter as code owners November 13, 2025 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dhei dhei dhei approved these changes

@leobalter leobalter Awaiting requested review from leobalter leobalter is a code owner

Assignees

@jpg619 jpg619

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jpg619 @dhei