github · lee-dohm · Apr 26, 2021 · Apr 26, 2021 · Apr 23, 2021
diff --git a/assets/images/help/organizations/settings-button.png b/assets/images/help/organizations/settings-button.png
diff --git a/assets/images/help/profile/your-organizations.png b/assets/images/help/profile/your-organizations.png
diff --git a/...ies/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/...ies/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -57,7 +57,7 @@ In your organization's repositories, blocked users also cannot:
 1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. Under "Block a user", type the username of the user you'd like to block.
 ![Username field](/assets/images/help/organizations/org-block-username-field.png)

diff --git a/...s/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/...s/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -31,7 +31,7 @@ If you selected a specific amount of time to block the user, they will be automa
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**.
 ![Unblock user button](/assets/images/help/organizations/org-unblock-user-button.png)

diff --git a/...g-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/...g-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -12,7 +12,7 @@ topics:
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", review the list of users who are blocked from your organization.
   ![List of blocked users](/assets/images/help/settings/list-of-blocked-users-for-org.png)

diff --git a/...rating-comments-and-conversations/limiting-interactions-in-your-organization.md b/...rating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -24,13 +24,13 @@ Members of the organization are not affected by any of the limit types.
 
 When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
 
-Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." 
+Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
 
 ### Limiting interactions in your organization
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the organization settings sidebar, click **Moderation settings**.
   !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Under "Moderation settings", click **Interaction limits**.

diff --git a/...github-marketplace/applying-for-publisher-verification-for-your-organization.md b/...github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -13,16 +13,16 @@ Once your organization has been verified, you can publish paid plans for your ap
 
 To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)."
 
-### Requesting publisher verification 
+### Requesting publisher verification
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the left sidebar, click **Developer settings**.
   ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Under "Developer settings", click **Publisher Verification**.
   ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
-1. Under "Publisher Verification", complete the information in the checklist: 
+1. Under "Publisher Verification", complete the information in the checklist:
    - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
    - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."
    - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."

diff --git a/content/github/administering-a-repository/restoring-a-deleted-repository.md b/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -33,7 +33,7 @@ Restoring a repository will not restore release attachments or team permissions.
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}

diff --git a/...eveloping-online-with-codespaces/managing-access-and-security-for-codespaces.md b/...eveloping-online-with-codespaces/managing-access-and-security-for-codespaces.md
@@ -39,9 +39,9 @@ When you enable access and security for a repository owned by your organization,
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.click-codespaces %}
-5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.  
+5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.
   ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png)
 1. Under "Access and security", select the setting you want for your organization.
   ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)

diff --git a/...ub/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/...ub/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -58,7 +58,7 @@ Downgrading to {% data variables.product.prodname_free_team %} for organizations
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
   ![Buy Enterprise and Downgrade to Team buttons](/assets/images/help/organizations/finish-trial-buttons.png)

diff --git a/...b/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/...b/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -18,7 +18,7 @@ When you disable project boards, you will no longer see project board informatio
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
     - To disable organization-wide project boards, unselect **Enable projects for the organization**.
     - To disable repository project boards in the organization, unselect **Enable projects for all repositories**.

diff --git a/...-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/...-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -42,7 +42,7 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/...d-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/...d-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -41,7 +41,7 @@ If your organization is outside of the US or if you're using a corporate checkin
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
 1. If your account has an existing credit card that you want to update, click **New Card**.

diff --git a/...d-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/...d-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -37,7 +37,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
@@ -48,7 +48,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/...ents-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/...ents-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -46,7 +46,7 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
 
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (You can add more seats to the organization in the next step.)
@@ -58,7 +58,7 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
 ### Step 4: Upgrade the number of paid seats in the organization
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}

diff --git a/...d-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/...d-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -25,7 +25,7 @@ When you downgrade your number of data packs, your change takes effect on your n
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/...payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/...payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -29,7 +29,7 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.marketplace-org-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}

diff --git a/...managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/...managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -47,7 +47,7 @@ If you downgrade your organization from {% data variables.product.prodname_team
 If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want.
   ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
@@ -60,7 +60,7 @@ If you downgrade your organization from {% data variables.product.prodname_ghe_c
 {% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**.
     ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png)
@@ -77,7 +77,7 @@ To reduce the number of paid seats your organization uses, you can remove member
 - "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**.
   ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)

diff --git a/...lling-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/...lling-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -37,7 +37,7 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization.
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}

diff --git a/...ling-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/...ling-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -37,7 +37,7 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization.
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}

diff --git a/...ing-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/...ing-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -36,7 +36,7 @@ If you're paying for your {% data variables.product.product_name %} subscription
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}

diff --git a/...aging-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/...aging-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -21,9 +21,9 @@ topics:
 ### Updating your organization's credit card
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Under "Payment method", click **New Card**. 
+1. Under "Payment method", click **New Card**.
 ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/...ng-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/...ng-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -29,7 +29,7 @@ Your organization's billing email is where {% data variables.product.product_nam
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Under **Billing email**, type a valid email address. The email does not need to be unique to the organization account.
   ![Billing email textbox](/assets/images/help/settings/org-billing-email.png)
 5. To confirm your changes, click **Update profile**.
@@ -42,7 +42,7 @@ If you have users that want to receive billing reports, you can add their email
 #### Adding a recipient for billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 1. Under "Billing management", to the right of "Email recipients", click **Add**.
   ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png)
@@ -54,7 +54,7 @@ If you have users that want to receive billing reports, you can add their email
 One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 1. Under "Billing management", find the email address you want to set as the primary recipient.
 1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**.
@@ -63,7 +63,7 @@ One address must always be designated as the primary recipient. The address with
 #### Removing a recipient from billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 1. Under "Email recipients", find the email address you want to remove.
 1. For the user's entry in the list, click **Edit**.

diff --git a/...and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/...and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -24,7 +24,7 @@ topics:
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}

diff --git a/...d-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/...d-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -23,7 +23,7 @@ topics:
 ### Upgrading an organization's number of paid seats
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
@@ -34,7 +34,7 @@ After you add seats, the payment method on file for the organization will be cha
 ### Downgrading an organization's number of paid seats to free
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/...d-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/...d-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -27,7 +27,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 {% data reusables.marketplace.marketplace-org-perms %}
 
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}