You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/enterprise-onboarding/setting-up-organizations-and-teams/best-practices-for-organizations-in-your-enterprise.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,9 @@ Within each organization in your enterprise, you should encourage organization o
39
39
***Add multiple owners**: If an organization only has one owner, the organization's projects can become inaccessible if the owner is unreachable. To ensure that no one will lose access to a project, we recommend that at least two people within each organization have the owner role.
40
40
***Use teams**: Teams allow you to manage permissions, code ownership, and notifications for groups of people. If you use an identity provider (IdP) for authentication, we highly recommend managing team membership through your IdP. See [AUTOTITLE](/enterprise-onboarding/setting-up-organizations-and-teams/creating-teams).
41
41
***Collaborate in organization-owned repositories**: Where possible, minimize collaboration in user-owned repositories. Organization-owned repositories have more sophisticated security and administrative features, and they remain accessible even as enterprise membership changes.
42
+
***Create a backup**: Before deleting an organization, make sure to create backups of all important data. Deleting an organization account permanently removes all repositories, forks of private repositories, wikis, issues, pull requests, and project or organization pages. Repository configuration settings cannot be restored.
43
+
44
+
For details about what happens when you delete an organization, see [Deleting an organization account](/organizations/managing-organization-settings/deleting-an-organization-account). For instructions on backing up data, see [AUTOTITLE](/repositories/archiving-a-github-repository/backing-up-a-repository).
> If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan) instead of deleting the organization and its content.
24
24
25
25
{% endif %}
26
-
Deleting your organization account removes all repositories, forks of private repositories, wikis, issues, pull requests, and project or organization pages. {% ifversion fpt or ghec %}Your billing will end and, after 90 days, the organization name becomes available for use on a new user or organization account.
26
+
Deleting your organization account permanently removes all repositories, forks of private repositories, wikis, issues, pull requests, and project or organization pages. **This action is irreversible.**
27
+
28
+
{% ifversion fpt or ghec %}Billing for the organization will end. {% ifversion ghec %}If the organization is part of an enterprise account, billing will stop through the enterprise agreement.{% endif %} **Upon deletion, the organization name will not be available to use for another organization or user account for 90 days.** After the 90 days pass, the organization name will automatically become available for use on a new user or organization account.
27
29
28
30
> [!TIP]
29
-
> If you rename an organization, you can create a new organization with the same name immediately. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/renaming-an-organization).
31
+
> If you would like to make your organization name available for reuse immediately, rename your organization instead of deleting it. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/renaming-an-organization).
30
32
31
33
{% endif %}
32
34
@@ -42,7 +44,7 @@ You can also archive an organization, instead of deleting it. Archiving an organ
42
44
43
45
## Backing up your organization content
44
46
45
-
{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and projects from the account.
47
+
{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and projects from the account. See [AUTOTITLE](/repositories/archiving-a-github-repository/backing-up-a-repository).
0 commit comments