Skip to main content

Setting base permissions for an organization

You can set base permissions for the repositories that an organization owns.

Who can use this feature?

Organization owners can set base permissions for an organization.

About base permissions for an organization

You can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. Base permissions do not apply to outside collaborators.

By default, members of an organization will have Read permissions to the organization's public repositories.

If someone with admin access to an organization's repository grants a member a higher level of access for the repository, the higher level of access overrides the base permission.

If you've created a custom repository role with an inherited role that is lower access than your organization's base permissions, any members assigned to that role will default to the organization's base permissions rather than the inherited role. For more information, see "Managing custom repository roles for an organization."

Note

  • All changes to base permissions will affect both new and existing members.
  • When you change base permissions for an organization, permissions for private forks are not automatically updated.

Setting base permissions

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.
  2. Next to the organization, click Settings.
  3. In the "Access" section of the sidebar, click Member privileges.
  4. Under "Base permissions", select the dropdown menu and click a permissions level.
  5. Review the changes. To confirm, click Change default permission to PERMISSION.

Further reading