Skip to content

fpt Configuring a package's access control and visibility lists internal #46907

Open

Description

@jsoref

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility

What part(s) of the article would you like to see updated?

All references to or internal should be omitted, e.g. in:

https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#configuring-access-to-packages-for-your-personal-account

If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams.

https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#configuring-access-to-packages-for-an-organization

If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams.

https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#package-creation-visibility-for-organization-members

Under "Package Creation", choose whether you want to enable the creation of public , private , or internal packages.

(This should become or private)

To enable organization members to create internal packages that are visible to all organization members, click Internal. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.

Additional information

https://docs.github.com/en/get-started/learning-about-github/githubs-plans#github-enterprise

In addition to the features available with GitHub Team, GitHub Enterprise includes:

...
Deployment protection rules with GitHub Actions for private or internal repositories
...
Additional features such as internal repositories and repository rules.


This probably isn't limited to one page in the docs:

https://docs.github.com/en/search?query=internal&search-overlay-ask-ai=false&toplevel=GitHub+Packages

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Nov 10, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions