"installation not allowed to Create organization package"

[somebodylikeRAIL]

Select Topic Area

Question

Body

I keep getting this error message. I updated my PAT to have all permissions with read/write. But I keep getting this error. Is this possibly related to not having a paid account? My developer has a Teams account and he does not have this issue.

[asadchaudhary79]

This error occurs because GitHub Personal Access Tokens (PAT) have different permission requirements depending on your account type and the package registry you're using.

Solution Steps:

1. Check Your PAT Scopes

Your PAT needs the following scopes at minimum:

• write:packages - to upload packages
• read:packages - to download packages
• repo - if your package is in a private repository
• delete:packages - (optional) if you need to delete package versions

2. Organization Package Permissions

If you're trying to publish to an organization, you need additional permissions:

• The organization must grant you permission to publish packages
• Go to: Organization Settings → Packages → Member privileges
• Ensure "Members can publish packages" is enabled
• Your account must have write or admin role in the organization

3. Update Your PAT

1. Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
2. Create a new token or update your existing one
3. Select the required scopes mentioned above
4. Regenerate and update your token in your project configuration

4. Configure Package Registry Authentication

Make sure your .npmrc (for npm) or equivalent config file is properly set up:

//npm.pkg.github.com/:_authToken=YOUR_PAT_TOKEN
@YOUR_ORG:registry=https://npm.pkg.github.com

5. Verify Organization Settings

Even with correct PAT permissions, organization admins may have restricted package publishing. Ask your organization admin to:

• Check organization package settings
• Verify you have the necessary role/permissions
• Confirm that the package visibility settings allow your action

Common Causes:

• Using a PAT without write:packages scope
• Organization has disabled member package publishing
• Trying to publish to an organization you're not a member of
• PAT has expired or been revoked

Note:

As mentioned, having a Teams account doesn't affect package permissions - this is controlled by organization settings and your PAT scopes.

If the issue persists after checking all these points, try creating a fresh PAT with all necessary scopes and test with a simple package publish operation.

[krishparmar22242]

"Hey! I looked into that PAT permission error.
Good news: It’s almost certainly not because you have a free account. GitHub doesn't lock those features behind a paywall; it’s usually just a sneaky default setting that’s different for Personal vs. Teams accounts.
Here is the 2-minute fix:

1. Check the 'Master Switch': Go to your repository Settings > Actions > General. Scroll to the bottom and make sure 'Read and write permissions' is selected under 'Workflow permissions'. On free accounts, this sometimes defaults to 'Read only'.
2. The 'Workflow' Scope: Go back to your PAT settings (Developer Settings) and make sure the specific 'workflow' scope is checked. Even with 'Full Repo' access, you need that specific one to edit Action files.
3. Secret Check: Make sure your workflow is actually using your PAT. If the code says ${{ secrets.GITHUB_TOKEN }}, it’s using GitHub's default limited token. You need to save your PAT as a Secret (like PAT_TOKEN) and use ${{ secrets.PAT_TOKEN }} in your YAML.
   Usually, it’s that first toggle in the Repo Settings that trips everyone up. Let me know if that clears it for you! "

[AnuragDubey007]

This error is usually related to permissions and organization-level settings rather than the account being paid or free.

For organization packages, the org must explicitly allow package creation and publishing. Even if your PAT has read/write permissions, the organization settings (or your role within the org) may restrict package creation.

Things to check:

• Your role in the organization (must typically be Owner or have package permissions)
• Organization → Packages settings
• Whether the package registry requires approval or specific scopes

Since your teammate with a Teams account doesn’t see the issue, it’s likely a permissions or org-policy difference rather than billing alone.

[sakthimurugesanr]

This issue is not related to having a paid GitHub account. A free account can use PATs with full read/write access.

The problem usually happens because the PAT is missing the correct scopes for the specific operation or the token is not authorized for the organization/repository.

Most common causes:

• The PAT does not include required scopes like repo, workflow, read:org, or write:packages (depends on what you’re doing).

• The repository belongs to an organization, and the PAT is not approved under Organization → Settings → Third-party access.

• You’re using a fine-grained PAT, which requires explicitly selecting the repository and permissions.

• The old token is still cached (CI, Git config, or environment variables).

How to resolve:

1 .Regenerate the PAT and ensure the exact required scopes are enabled.

2 .If it’s an org repo, approve the PAT in the organization settings.

3 .Update the token everywhere it’s used (local Git, CI/CD, secrets).

4. If using fine-grained PATs, confirm the repo is selected and permissions match the action.

Since your developer’s Teams account works, this confirms it’s a token scope or org-authorization issue, not billing.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[shayaaniqbal]

This is not related to having a paid account. The error usually means the token or app you’re using does not have permission to create packages at the organization level.

Make sure that:

• You are an organization owner or have permission to create org packages
• GitHub Packages is enabled for the organization
• The token has write:packages (and read:packages) permissions
• You are not using a GitHub App / installation token that lacks package write access

Free organizations can create packages, but private packages require a paid plan.