- Projects, the all-new projects experience, is now available. For more information about Projects, see "About Projects" and for information about migrating your classic project, see "Migrating from projects (classic)."
- You can only create a new classic project board for an organization or user that already has at least one classic project board. You cannot create new classic projects for repositories. If you're unable to create a classic project board, create a project instead.
By default, user-owned and organization-wide classic projects are private and only visible to people with read, write, or admin permissions to the classic project. A public classic project is visible to anyone with the classic project's URL. Repository-level classic projects share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed.
- Organization owners can control the ability of organization members to create public projects and classic projects, or change the visibility of existing projects and classic projects to public. For more information, see "Allowing project visibility changes in your organization."
- When you make your classic project 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 classic project as a collaborator. For more information, see "Project (classic) permissions for an organization."
Navigate to the project board you want to make public or private.
On the top-right side of the classic project, click Menu.
Click , then click Settings.
Under "Visibility", choose to make your project board public or private. For more information, see "Changing project (classic) visibility."