{"meta":{"title":"Enabling or disabling GitHub Codespaces for your organization","intro":"You can control which users can use GitHub Codespaces in your organization's private repositories.","product":"Codespaces","breadcrumbs":[{"href":"/en/codespaces","title":"Codespaces"},{"href":"/en/codespaces/managing-codespaces-for-your-organization","title":"Managing your organization"},{"href":"/en/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization","title":"Enable or disable Codespaces"}],"documentType":"article"},"body":"# Enabling or disabling GitHub Codespaces for your organization\n\nYou can control which users can use GitHub Codespaces in your organization's private repositories.\n\n## About enabling and disabling GitHub Codespaces\n\nGitHub Codespaces is always available in an organization's public repositories. Any user can create a codespace from these repositories.\n\nIf your organization is on a GitHub Free plan, GitHub Codespaces is always available in your organization's private repositories. Any user with access to these repositories can create a codespace at their own expense.\n\nIf you're an organization owner on a paid GitHub plan, you can enable or disable GitHub Codespaces for your organization's private repositories. You can enable GitHub Codespaces for all users or only for selected members and collaborators.\n\n## Enabling or disabling GitHub Codespaces\n\n> \\[!NOTE]\n> Removing a user's access to GitHub Codespaces will prevent them from opening any of their existing codespaces in your organization's private repositories. For more details, see [What happens when I remove a user's access to GitHub Codespaces?](#what-happens-when-i-remove-a-users-access-to-github-codespaces)\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 left sidebar, click ** Codespaces**.\n5. Under ** Codespaces**, in the left sidebar, click **General**.\n6. On the Codespaces settings page, under \"Codespaces access,\" select your preferred setting for GitHub Codespaces in your organization's private repositories.\n\n## Ensuring your users can create codespaces\n\nTo allow a user to create codespaces for a repository owned by your organization, you must do one of the following:\n\n* Give the user **read access** to the repository and permit forking. This allows the user to create a codespace, push changes to a fork, and open a pull request. For more information, see [Managing the forking policy for your organization](/en/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization).\n* Give the user **write access** to the repository so that they can push changes directly to the repository without forking.\n\n> \\[!NOTE]\n> If you are a verified educator or a teacher, you must enable GitHub Codespaces from a GitHub Classroom to use your Codespaces Education benefit. For more information, see [Using GitHub Codespaces with GitHub Classroom](/en/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers).\n\n## What happens when I remove a user's access to GitHub Codespaces?\n\nBefore removing users' access to GitHub Codespaces, you should **alert the affected users.**\n\nWhen you remove a user's access, the user will immediately be unable to open existing codespaces they have created from your organization's private repositories.\n\n* If you alert them first, they can push any unpublished work to a branch in the repository before they lose access.\n* Once a user loses access to a codespace, the codespace is retained for a period of 7 days, then it is permanently deleted. During this 7-day period, to recover unpublished work from the codespace, the user must contact us through the [GitHub Support portal](https://support.github.com).\n\nIf you were previously paying for codespaces the user had created from your organization's public repositories, ownership of these codespaces will transfer to the user.\n\n## Further reading\n\n* [Choosing who owns and pays for codespaces in your organization](/en/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization)"}