Skip to main content

Changing project (classic) visibility

As an organization owner or project (classic) admin, you can make a project (classic) public or private.

Note

Creation of new projects (classic) is now disabled. Projects (classic) will be sunset and removed on August 23, 2024. You can read more about this change on the GitHub Blog.

The new and improved Projects experience is available. For more information, see "About Projects."

On August 23, 2024, all remaining projects (classic) will be automatically migrated before the feature is removed.

By default, user-owned and organization-wide projects (classic) are private and only visible to people with read, write, or admin permissions to the project (classic). A public project (classic) is visible to anyone with the project (classic)'s URL. Repository-level projects (classic) share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed.

Notes:

  • Organization owners can control the ability of organization members to create public projects, or change the visibility of existing projects and projects (classic) to public. For more information, see "Allowing project visibility changes in your organization."
  • When you make your project (classic) public, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the project (classic) as a collaborator. For more information, see "Project (classic) permissions for an organization."
  1. Navigate to the project (classic) you want to make public or private.

  2. On the top-right side of the project (classic), click Menu.

  3. Click , then click Settings.

    Screenshot showing the project menu. The settings option is highlighted with an orange outline.

  4. Under "Visibility", choose to make your project (classic) public or private.

  5. Click Save.