Organization Archiving [GHES 3.11] (#45335)

Author: sophietheking

content/organizations/managing-organization-settings/archiving-an-organization.md

@@ -9,12 +9,16 @@ topics:
   - Organizations
 ---
 
+{% ifversion fpt or ghec %}
+
 {% note %}
 
 **Note:** You can only archive an organization if it's using {% data variables.product.prodname_free_team %} or if the organization is part of an enterprise. If you want to archive an individually-billed organization, you must downgrade your organization to {% data variables.product.prodname_free_team %} first. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
 
 {% endnote %}
 
+{% endif %}
+
 ## About archiving your organization
 
 When you archive an organization, all repositories in the organization will be archived as well. This means that all issues, pull requests, and comments will be read-only. A key will be set in the API to indicate the organization has been archived. Many actions that can be performed in an organization will be disabled, including creating new repositories. You will still be able to delete repositories. You will also still be able to transfer repositories out of the organization, for example, to give a project to a user who is taking over active maintenance.

data/features/archive-organizations.yml

@@ -3,3 +3,4 @@
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.11'