Private NPM Registry Auth Token Cycling

Hey hey ​@Jake Mauer 👋 Thanks for the clear, specific questions — that makes this easy to dig into.

A couple of quick things so I can repro on the same screen you're looking at:

• Are you set up as an org admin? The npm registry configuration lives under Admin → Resources → npm registry. I want to confirm we're both looking at the same place 👀
• Which guide are you following for setup? If it's Bring your design system package to a Make kit, I'll repro against that exact flow
• Just to make sure I answer the right thing: when you say "auth token," you mean the token inside the .npmrc code snippet from View configuration — not a Personal Access Token or a Plan Access Token — correct?

Once I've got those, I'll get you a clear answer on both the scope and regenerating it.

— Jaycee

1. I am an org admin and yeah that’s the path I’m referring to. Admin → Resources → npm registry
2. Yes those are the instructions I was looking at and following.
3. Yes the auth token that’s provided in the code snippet that’s prefixed with “:_authToken=”

Thank you!

Thanks ​@Jake Mauer 👋 I’ll take this to my resources and get clarity for us. — Jaycee

Hey ​@Jaycee Lewis just checking in to see if you’ve been able to get any more clarification on this. Thank you!

Hey hey ​@Jake Mauer 👋 We must be on the same vibe today.

Here’s what I found out for us:

• NPM Registry Auth Token can be private or shared, and must be stored securely
• Each time you click "view configuration" you'll get a new token generated 
• Can you try this link for viewing your tokens: https://figma.com/developers/tokens?type=npm&sort_column=last_used

I’m waiting on additional details on the maximum number of tokens per plan. If you have any additional questions, let me know and I’ll add them to my internal query. Talk soon! — Jaycee

Thank you! I’ll let you know if our security team needs any more info.