Skip to main content

Managing access to a project (classic) for organization members

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, 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, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board 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 board permissions for an organization."

  1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu

  2. Click the name of your organization. Organization name in list of organizations

  3. Under your organization name, click Projects.

    Projects tab for your organization

  4. Click Projects (classic)

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

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

  7. Click , then click Settings. Settings option in drop-down menu from project board sidebar

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

  9. Click Save.

Further reading