[Update] docs: update access token creation instructions (#1774)
## 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
Jithin Prabhakaran Girija committed
Nov 17, 2025 at 14:49 UTC
97aaaa8f7d7ebb4fb966787632b8785b37a0bad2
2 files changed
+8
-6
content/integrations/integrating-npm-with-external-services/creating-and-viewing-access-tokens.mdx
+8
-6
@@ -14,7 +14,7 @@ You can [create](#creating-access-tokens) and [view](#viewing-access-tokens) acc
14
15
<Screenshot src="/integrations/integrating-npm-with-external-services/tokens-profile.png" alt="Screenshot of the account menu with the tokens link selected" />
16
17
-2. Click **Generate New Token**, then click **Granular Access Token**.
17
+2. Click **Generate New Token**.
18
19
<Screenshot src="/integrations/integrating-npm-with-external-services/create-token.png" alt="Screenshot of the create new token button" />
20
@@ -26,13 +26,11 @@ You can [create](#creating-access-tokens) and [view](#viewing-access-tokens) acc
26
- This setting is unchecked (false) by default
27
- By checking this box, the token will bypass 2FA for write actions even if 2FA is enabled at the account or package level
28
29
-6. In the **Expiration** field, enter a token expiration period. The date must be at least 1 day in the future.
30
-
31
-7. (Optional) In the **Allowed IP Ranges** field, enter IP address ranges to restrict your access token to. You must use [CIDR][cidr-wiki] notation to enter IP address ranges. To add more than one allowed IP range, click **Add IP Range** and enter an IP range in the new text field.
29
+6. (Optional) In the **Allowed IP Ranges** field, enter IP address ranges to restrict your access token to. You must use [CIDR][cidr-wiki] notation to enter IP address ranges. To add more than one allowed IP range, click **Add IP Range** and enter an IP range in the new text field.
30
31
<Screenshot src="/integrations/integrating-npm-with-external-services/granular-access-token-ip-range.png" alt="Screenshot of the allowed IP ranges section" />
32
35
-8. (Optional) In the **Packages and scopes** section, configure your token's access to packages and scopes.
33
+7. (Optional) In the **Packages and scopes** section, configure your token's access to packages and scopes.
34
- In the **Permissions** dropdown menu, select **No access**, **Read-only**, or **Read and write**.
35
- Under **Select Packages**, select either:
36
- **All Packages** to grant the token access to all packages the user account has access to.
@@ -40,7 +38,7 @@ You can [create](#creating-access-tokens) and [view](#viewing-access-tokens) acc
38
39
<Screenshot src="/integrations/integrating-npm-with-external-services/granular-access-token-packages-scopes.png" alt="Screenshot of the packages and scopes section" />
40
43
-9. (Optional) In the **Organizations** section, configure your token's access to organizations.
41
+8. (Optional) In the **Organizations** section, configure your token's access to organizations.
42
- In the **Permissions** dropdown menu, select **No access**, **Read-only**, or **Read and write**.
43
- Under **Select organizations**, select the organizations you want to grant your token access to.
44
@@ -48,6 +46,10 @@ You can [create](#creating-access-tokens) and [view](#viewing-access-tokens) acc
46
47
_**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._
48
49
+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.
50
+
51
+ _**Note**: The date must be at least 1 day in the future._
52
+
53
10. Review the token summary, then click **Generate Token**.
54
55
<Screenshot src="/integrations/integrating-npm-with-external-services/granular-access-token-summary.png" alt="Screenshot of the granular access token summary and the generate token button" />
static/integrations/integrating-npm-with-external-services/create-token.png
Binary files a/static/integrations/integrating-npm-with-external-services/create-token.png and b/static/integrations/integrating-npm-with-external-services/create-token.png differ