Managing access to a project (classic) for organization members

In this article

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

Notes:

  • Projects (beta), the all-new projects experience, is now available. For more information about Projects (beta), see "About Projects (beta)."
  • You can only create a new classic project board for an organization, repository, or user that already has at least one classic project board. If you're unable to create a classic project board, create a project instead.

By default, organization members have write access to their organization's classic projects unless organization owners or classic project admins set different permissions for specific classic projects.

Setting a baseline permission level for all organization members

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

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

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  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 classic project.

  6. On the top-right side of the classic project, 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