Opinions please!

[zvailanu98]

for GitHub Codespaces."

If a user can access one of your organization's repositories, but you haven't allowed them to create a codespace at your organization's expense, the user can still create codespaces from the repository. These codespaces will incur usage on the user's personal account.

Regardless of who pays for a codespace, only people who can either push changes to a repository, or fork the repository, can create a codespace for that repository. To allow a user to create codespaces for a repository owned by your organization, you must do one of the following things.

Ensure that the user has read access to the repository, and the repository permits forking, so that the user can create a codespace from the repository, push their changes to a fork, and create a pull request for any changes they want to make. For more information, see "Managing the forking policy for your organization."
Ensure that the user has write access to the repository, so that they can push changes directly to the repository without forking.
You must also ensure that your organization does not have an IP address allow list enabled. For more information, see "Managing allowed IP addresses for your organization" in the GitHub Enterprise Cloud documentation.

To allow people to create codespaces for which your organization will be billed, you must:

Set a spending limit
Choose who can create codespaces that are billed to your organization
When you have set a spending limit, you can access settings for GitHub Codespaces in your organization's settings and in repositories owned by your organization. For example, you can set up prebuilds for a repository, or you can set a policy to restrict the base image or machine type that can be used in your organization's codespaces. These policies apply to codespaces that your organization pays for, but not to codespaces created from your repositories that are billed to a user's personal account.

You can also use the REST API to manage codespaces owned by your organization, for example to stop or delete a codespace. For more information, see "Codespaces organizations" in the REST API documentation.

Note: 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."

By default, a codespace can only access the repository from which it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "Managing repository access for your organization's codespaces."

Choose who can create codespaces that are billed to your organization
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.

Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

Next to the organization, click Settings.

In the left sidebar, click Codespaces.

Under Codespaces, in the left sidebar, click General.

On the Codespaces settings page, under "Billing," select one of the following options:

Disabled - Your organization will not be charged for codespace usage. Codespaces created for your organization's repositories will be billed to the individual users who create them.
Selected members - Codespaces created for your organization's repositories by selected members will be billed to the organization.
All members - Codespaces created for your organization's repositories by members of your organization will be billed to the organization.
All members and outside collaborators - Codespaces created for your organization's repositories by organization members and outside collaborators will be billed to the organization.
Note: When you select All members and outside collaborators, all outside collaborators who have been added to specific repositories can create and use Codespaces for those repositories, and your organization will be billed for this usage. For more information on managing outside collaborators, see "Adding outside collaborators to repositories in your organization."

Click Save.

If you chose Selected members, an input box is displayed for you to enter the names of users you want to select.

Screenshot of the input box, below the "Save" button, for entering user names. The user "octocat" has already been added as a selected member.

Disabling Codespaces for your organization
You can prevent the creation and use of codespaces billable to your organization.

Note: If you disable billing for GitHub Codespaces for some organization members and collaborators, or for your entire organization, anyone who can either push changes to, or fork, a repository in your organization, will still be able to create a codespace for that repository by using their personal account. However, this will not incur any charge for your organization. For information about restricting access to a repository, see "Managing teams and people with access to your repository."

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

Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

Next to the organization, click Settings.

In the left sidebar, click Codespaces.

Under Codespaces, in the left sidebar, click General.

On the Codespaces settings page, under "Billing," select Disabled.

Setting a spending limit
Note: You must set a non-zero spending limit on your personal, organization, or enterprise account before the account can be billed for use of GitHub Codespaces.

By default, all accounts have a GitHub Codespaces spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, codespaces can always be created and used if the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD.

For information on managing and changing your account's spending limit, see "Managing the spending limit for GitHub Codespaces."

Help and support
Did this doc help you?

Privacy policy
Help us make these docs great!
All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

[zvailanu98]

for GitHub Codespaces."

If a user can access one of your organization's repositories, but you haven't allowed them to create a codespace at your organization's expense, the user can still create codespaces from the repository. These codespaces will incur usage on the user's personal account.

Regardless of who pays for a codespace, only people who can either push changes to a repository, or fork the repository, can create a codespace for that repository. To allow a user to create codespaces for a repository owned by your organization, you must do one of the following things.

Ensure that the user has read access to the repository, and the repository permits forking, so that the user can create a codespace from the repository, push their changes to a fork, and create a pull request for any changes they want to make. For more information, see "Managing the forking policy for your organization." Ensure that the user has write access to the repository, so that they can push changes directly to the repository without forking. You must also ensure that your organization does not have an IP address allow list enabled. For more information, see "Managing allowed IP addresses for your organization" in the GitHub Enterprise Cloud documentation.

To allow people to create codespaces for which your organization will be billed, you must:

Set a spending limit Choose who can create codespaces that are billed to your organization When you have set a spending limit, you can access settings for GitHub Codespaces in your organization's settings and in repositories owned by your organization. For example, you can set up prebuilds for a repository, or you can set a policy to restrict the base image or machine type that can be used in your organization's codespaces. These policies apply to codespaces that your organization pays for, but not to codespaces created from your repositories that are billed to a user's personal account.

You can also use the REST API to manage codespaces owned by your organization, for example to stop or delete a codespace. For more information, see "Codespaces organizations" in the REST API documentation.

Note: 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."

By default, a codespace can only access the repository from which it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "Managing repository access for your organization's codespaces."

Choose who can create codespaces that are billed to your organization In the top right corner of GitHub.com, click your profile photo, then click Your organizations.

Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

Next to the organization, click Settings.

In the left sidebar, click Codespaces.

Under Codespaces, in the left sidebar, click General.

On the Codespaces settings page, under "Billing," select one of the following options:

Disabled - Your organization will not be charged for codespace usage. Codespaces created for your organization's repositories will be billed to the individual users who create them. Selected members - Codespaces created for your organization's repositories by selected members will be billed to the organization. All members - Codespaces created for your organization's repositories by members of your organization will be billed to the organization. All members and outside collaborators - Codespaces created for your organization's repositories by organization members and outside collaborators will be billed to the organization. Note: When you select All members and outside collaborators, all outside collaborators who have been added to specific repositories can create and use Codespaces for those repositories, and your organization will be billed for this usage. For more information on managing outside collaborators, see "Adding outside collaborators to repositories in your organization."

Click Save.

If you chose Selected members, an input box is displayed for you to enter the names of users you want to select.

Screenshot of the input box, below the "Save" button, for entering user names. The user "octocat" has already been added as a selected member.

Disabling Codespaces for your organization You can prevent the creation and use of codespaces billable to your organization.

Note: If you disable billing for GitHub Codespaces for some organization members and collaborators, or for your entire organization, anyone who can either push changes to, or fork, a repository in your organization, will still be able to create a codespace for that repository by using their personal account. However, this will not incur any charge for your organization. For information about restricting access to a repository, see "Managing teams and people with access to your repository."

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

Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

Next to the organization, click Settings.

In the left sidebar, click Codespaces.

Under Codespaces, in the left sidebar, click General.

On the Codespaces settings page, under "Billing," select Disabled.

Setting a spending limit Note: You must set a non-zero spending limit on your personal, organization, or enterprise account before the account can be billed for use of GitHub Codespaces.

By default, all accounts have a GitHub Codespaces spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, codespaces can always be created and used if the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD.

For information on managing and changing your account's spending limit, see "Managing the spending limit for GitHub Codespaces."

Help and support Did this doc help you?

Privacy policy Help us make these docs great! All GitHub docs are open source. See something that's wrong or unclear? Submit a pull payment method pay id request needed please contact me for more information $$