Skip to content

Commit

Permalink
[Improvement]: FAQs page to address migration to enterprise accounts …
Browse files Browse the repository at this point in the history
…(#52041)

Co-authored-by: Ben Ahmady <[email protected]>
  • Loading branch information
sophietheking and subatoi authored Aug 20, 2024
1 parent 456de46 commit 846df34
Show file tree
Hide file tree
Showing 4 changed files with 18 additions and 8 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,9 @@ topics:

<!-- expires 2024-09-03 -->

Check warning on line 25 in content/admin/managing-your-enterprise-account/about-enterprise-accounts.md

View workflow job for this annotation

GitHub Actions / lint-content

Content that expires soon should be proactively addressed.

Content marked with an expiration date will expire soon. The content exists between 2 HTML comment tags in the format <!-- expires yyyy-mm-dd --> and <!-- end expires yyyy-mm-dd -->. Check whether this content can be removed or rewritten before it expires.
{% ifversion ghec %}
{% data reusables.enterprise.single-organizations-enterprise-migration %}
> [!NOTE] Starting September 3, 2024, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization will be automatically upgraded to an enterprise account at no additional cost. For details, see "[AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization)."
{% endif %}
<!-- When this note expires, replace "Starting September 3, 2024" with something like "Currently" and adjust the expiry date in the articles to be a future date when we want to remove it entirely. -->
<!-- end expires 2024-09-03 -->

An enterprise account enables centralized management for **multiple organizations**.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,19 @@ In these cases, contact {% data variables.contact.contact_enterprise_sales %}.

## What will happen after I upgrade my organization?

* Your existing organization will automatically be owned by the enterprise account. To learn how the organization will change, see "[AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#about-addition-of-organizations-to-your-enterprise-account)."
* The organization's billing details will become the billing details for the enterprise.
* All of the organization's owners will become owners of the enterprise.
* All of the organization's billing managers will become billing managers for the enterprise.
* Going forward, {% data variables.product.company_short %} will bill the enterprise account for usage within **all** organizations owned by the enterprise.
The following changes also apply to single organizations that are automatically upgraded to an enterprise account. For details, see the [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2024-06-19-upcoming-automatic-upgrade-to-the-enterprise-account-experience/).

* **Ownership transfer**: Your organization will automatically be owned by the enterprise account. For details, see "[AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#about-addition-of-organizations-to-your-enterprise-account)."
* **Ownership roles:**: All organization owners will become enterprise owners.
* **Billing details**: The organization’s billing details will now apply to the enterprise account.
* **Billing managers**: All organization billing managers will become enterprise billing managers.
* **Billing process**: {% data variables.product.company_short %} will bill the enterprise account for usage within **all** organizations owned by the enterprise.
* **Enterprise account name**: During the upgrade, the new enterprise account name will match your organization name or be as close as possible if taken. You can rename it after the upgrade.
* **SAML SSO:** Existing SAML SSO will stay at the organization level after being added to the new enterprise account. You can configure SSO at the enterprise level post-upgrade, which will override the organization level. Existing PATs and SAML-authorized tokens will remain unchanged.
* **Policies**: The new enterprise account starts with no policies, so existing organization policies won't be overridden.
* **Spending limits**: Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, under "Settings" in the enterprise account sidebar, select **Billing**.
* **Coupons**: Existing coupons will carry over to the new enterprise account with no interruptions.
* **Workflow permissions**: The new enterprise account will inherit your organization's workflow permissions. If the organization has a permissive setting ("Read and write"), the enterprise account will also default to permissive. Otherwise, it defaults to restrictive ("Read repository contents and packages"). For workflows with the id-token permission, the default changes to read-only due to a February 2023 update. Add an explicit permissions block in these workflows to grant the required permissions.

## Upgrading an organization to an enterprise account

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,9 @@ To learn how to use organizations most effectively, see "[AUTOTITLE](/organizati

<!-- expires 2024-09-03 -->

Check warning on line 41 in content/organizations/collaborating-with-groups-in-organizations/about-organizations.md

View workflow job for this annotation

GitHub Actions / lint-content

Content that expires soon should be proactively addressed.

Content marked with an expiration date will expire soon. The content exists between 2 HTML comment tags in the format <!-- expires yyyy-mm-dd --> and <!-- end expires yyyy-mm-dd -->. Check whether this content can be removed or rewritten before it expires.
{% ifversion ghec %}
{% data reusables.enterprise.single-organizations-enterprise-migration %}
> [!NOTE] Starting September 3, 2024, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization will be automatically upgraded to an enterprise account at no additional cost. For details, see "[AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization)."
{% endif %}
<!-- When this note expires, replace "Starting September 3, 2024" with something like "Currently" and adjust the expiry date in the articles to be a future date when we want to remove it entirely. -->
<!-- end expires 2024-09-03 -->

{% ifversion fpt %}
Expand Down
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
> [!NOTE] Starting September 3, 2024, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization will be automatically upgraded to an enterprise account at no additional cost. For details, see the [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2024-06-19-upcoming-automatic-upgrade-to-the-enterprise-account-experience/).
> [!NOTE] Starting September 3, 2024, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization will be automatically upgraded to an enterprise account at no additional cost.
<!-- When this note expires, replace "Starting September 3, 2024" with something like "Currently" and adjust the expiry date in the articles to be a future date when we want to remove it entirely. -->

0 comments on commit 846df34

Please sign in to comment.