Managing access to a project (classic) for organization members

As an organization owner or project (classic) admin, you can set a default permission level for a project (classic) for all organization members.

In this article

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, organization members have write access to their organization's projects (classic) unless organization owners or project (classic) admins set different permissions for specific projects (classic).

Setting a baseline permission level for all organization members

Tip: You can give an organization member higher permissions to project (classic). For more information, see "Project (classic) permissions for an organization."

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Click the name of your organization.

  3. Under your organization name, click Projects.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a table icon and "Projects," is outlined in dark orange.

  4. Click Projects (classic)

  5. In the projects list, click the name of the project (classic).

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

  7. Click , then click Settings.

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

  8. Under "Organization member permission", choose a baseline permission level for all organization members: Read, Write, Admin, or None.

  9. Click Save.

Further reading