docs/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md

title, shortTitle, intro, permissions, versions, type, topics, redirect_from, product

title	shortTitle	intro	permissions	versions	type	topics	redirect_from	product
Managing repository access for your organization's codespaces	Repository access	You can manage the repositories in your organization that {% data variables.product.prodname_github_codespaces %} can access.	To manage access and security for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.	fpt ghec * *	how_to	Codespaces Security Administrator	/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces	{% data reusables.gated-features.codespaces-org %}

{% warning %}

Deprecation note: The access and security setting described below is now deprecated and is documented here for reference only. To enable expanded access to other repositories, add the requested permissions to your devcontainer.json configuration file. For more information, see "AUTOTITLE."

{% endwarning %}

By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.

To manage which users in your organization can use {% data variables.product.prodname_github_codespaces %}, see "AUTOTITLE."

{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} {% data reusables.organizations.click-general %}

1. On the {% data variables.product.prodname_codespaces %} settings page, under "Access and security", select the setting you want for your organization:

   • Disabled - Limit the access of codespaces to only the repository they were created from.
   • All repositories - All codespaces created from repositories in my organization can access other repositories owned by my organization.
   • Selected repositories - Codespaces created for specific repositories in my organization can access other repositories owned by my organization.

2. If you chose "Selected repositories", select the "Select repositories" dropdown menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat this step for all repositories whose codespaces you want to access other repositories.

Further reading

• "AUTOTITLE"