{"meta":{"title":"Managing the forking policy for your organization","intro":"You can allow or prevent the forking of any private repositories owned by your organization.","product":"Organizations","breadcrumbs":[{"href":"/en/organizations","title":"Organizations"},{"href":"/en/organizations/managing-organization-settings","title":"Manage organization settings"},{"href":"/en/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization","title":"Manage forking policy"}],"documentType":"article"},"body":"# Managing the forking policy for your organization\n\nYou can allow or prevent the forking of any private repositories owned by your organization.\n\nBy default, new organizations are configured to disallow the forking of private repositories.\n\nIf you allow forking of private repositories at the organization level, you can also configure the ability to fork a specific private repository. For more information, see [Managing the forking policy for your repository](/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository).\n\n1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**.\n2. Select an organization by clicking on it.\n3. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n4. In the \"Access\" section of the sidebar, click **Member privileges**.\n5. Under \"Repository forking\", select **Allow forking of private repositories**.\n6. Click **Save**.\n\n## Further reading\n\n* [Forks](/en/pull-requests/reference/forks)\n* [Repository roles for an organization](/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)"}