Create an Access Token
Access tokens authenticate your package manager client with pckgs.io without using your personal credentials. Tokens are scoped per organization and stored locally on your device.
How Permissions Work
- A token’s permissions are bounded by your own permissions in each organization. You cannot grant a token more access than you have.
- Specificity wins: if a token has read access to all packages but is explicitly denied one, the denial takes precedence.
- Tokens can only read and write packages — they cannot delete packages or organizations.
Always grant the minimum permissions the token needs.
Prerequisites
- A pckgs.io account. See Create an Account.
- Membership in at least one organization. See Create an Organization.
How to Create an Access Token
- Go to the Create Access Token page.
- Fill in the details:
A unique name for this token
A unique name to identify this token among your others.
Optional notes about this token’s purpose.
Optional expiration date. Tokens without an expiration date are valid indefinitely. For CI/CD use, always set an expiration.
Select which organizations this token can access, and configure per-organization permissions.
- Click to finish.
Important: Your token is shown only once. Copy it immediately and store it securely. If lost, you must delete it and create a new one.
Related
- Delete an Access Token — Revoke a token you no longer need.
Need help? Contact us here or at [email protected].