Make images accessible in the images/help/teams directory (#35121)

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md

@@ -55,8 +55,7 @@ Any member of an organization can create a new team and connect the team to an I
 {% data reusables.organizations.new_team %}
 {% data reusables.organizations.team_name %}
 {% data reusables.organizations.team_description %}
-1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect.
+1. To connect a team, under "Identity Provider Groups", select the **Select Groups** dropdown menu and click the team you want to connect.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}
 

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md

@@ -52,6 +52,4 @@ You can also configure and manage team synchronization for an individual organiz
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
 {% data reusables.identity-and-permissions.team-sync-confirm %}
 7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+8. To disable team synchronization, under "Team synchronization", click **Disable team synchronization**.
-8. To disable team synchronization, click **Disable team synchronization**.
-  ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)

content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md

@@ -40,10 +40,12 @@ To remove an existing member of a team synced to an LDAP group, contact your LDA
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
-4. Select the person or people you'd like to remove.
+1. Select the person or people you'd like to remove.
-![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
+
-5. Above the list of team members, use the drop-down menu and click **Remove from team**.
+   ![Screenshot of the first user in a list of team members. To the left of the user, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/team-member-check-box.png)
-![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+1. Above the list of team members, select the **X members selected** dropdown menu and click **Remove from team**.
+
+   {% data reusables.organizations.bulk-edit-team-members %}
 
 ## Removing a user from an organization
 

content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md

@@ -23,7 +23,7 @@ permissions: Organization owners can remove members from an organization.
 **Warning:** When you remove members from an organization:
 - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[AUTOTITLE](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
 - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
-- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork. 
+- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork.
 {%- ifversion ghec %}
 -  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[AUTOTITLE](/admin/overview/about-enterprise-accounts)."
 {%- endif %}
@@ -58,11 +58,12 @@ To help the person you're removing from your organization transition and help en
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.people %}
 4. Select the member or members you'd like to remove from the organization.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
+
-5. Above the list of members, use the drop-down menu, and click **Remove from organization**.
+  ![Screenshot of the first two users in a list of organization members. To the left of each member, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-members-selected-bulk.png)
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
+5. Above the list of members, select the **X members selected...** dropdown menu, and click **Remove from organization**.
+
+   ![Screenshot of the list of organization members. Above the list, a dropdown menu, labeled "2 members selected..." is outlined in dark orange.](/assets/images/help/teams/user-bulk-management-options.png)
 6. Review the member or members who will be removed from the organization, then click **Remove members**.
-  ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png)
 
 ## Further reading
 

content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md

@@ -27,7 +27,7 @@ Organization owners have full administrative access to the organization. {% data
 
 {% note %}
 
-**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role. 
+**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role.
 
 {% endnote %}
 
@@ -40,9 +40,10 @@ If your organization is owned by an enterprise account, any enterprise owner can
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the person or people you'd like to promote to owner.
+1. Select the person or people you'd like to promote to owner.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
+
-5. Above the list of members, use the drop-down menu and click **Change role**.
+  ![Screenshot of the first two users in a list of organization members. To the left of each member, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-members-selected-bulk.png)
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
+1. Above the list of members, select the **X members selected...** dropdown menu and click **Change role**.
-6. Select a new role for the person or people, then click **Change role**.
+
-  ![Radio buttons with owner and member roles and Change role button](/assets/images/help/teams/select-and-confirm-new-role-bulk.png)
+   ![Screenshot of the list of organization members. Above the list, a dropdown menu, labeled "2 members selected..." is outlined in dark orange.](/assets/images/help/teams/user-bulk-management-options.png)
+1. Select a new role for the person or people, then click **Change role**.

content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md

@@ -64,7 +64,6 @@ You must have a linked SAML identity. To create a linked identity, you must auth
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
 {% data reusables.identity-and-permissions.team-sync-confirm %}
 6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
 
 ### Enabling team synchronization for Okta
 
@@ -85,10 +84,9 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.identity-and-permissions.team-sync-confirm-scim %}
 1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
-7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
+1. Under your organization's name, in the "SSWS Token" field, type a valid SSWS token.
-  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+1. In the "URL" field, type the URL for your Okta instance.
-6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
+1. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
-  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
 
 ## Disabling team synchronization
 
@@ -98,4 +96,3 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "Team synchronization", click **Disable team synchronization**.
-  ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)

content/organizations/managing-user-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md

@@ -49,12 +49,13 @@ When you convert an organization member to an outside collaborator, their privil
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the person or people you'd like to convert to outside collaborators.
+1. Select the person or people you'd like to convert to outside collaborators.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
+
-5. Above the list of members, use the drop-down menu and click **Convert to outside collaborator**.
+  ![Screenshot of the first two users in a list of organization members. To the left of each member, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-members-selected-bulk.png)
-  ![Drop-down menu with option to convert members to outside collaborators](/assets/images/help/teams/user-bulk-management-options.png)
+1. Above the list of members, select the **X members selected...** dropdown menu and click **Convert to outside collaborator**.
-6. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**.
+
-  ![Information on outside collaborators permissions and Convert to outside collaborators button](/assets/images/help/teams/confirm-outside-collaborator-bulk.png)
+   ![Screenshot of the list of organization members. Above the list, a dropdown menu, labeled "2 members selected..." is outlined in dark orange.](/assets/images/help/teams/user-bulk-management-options.png)
+1. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**.
 
 ## Further reading
 

content/organizations/managing-user-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md

@@ -37,12 +37,13 @@ While forks of private repositories are deleted when a collaborator is removed,
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
-5. Select the outside collaborator or outside collaborators you'd like to remove from the organization.
+1. Select the outside collaborator or outside collaborators you'd like to remove from the organization.
-![List of outside collaborators with two outside collaborators selected](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png)
+
-6. Above the list of outside collaborators, use the drop-down menu, and click **Remove from all repositories**.
+   ![Screenshot of the first two users in the list of outside collaborators. To the left of each user, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png)
-![Drop-down menu with option to remove outside collaborators ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png)
+1. Above the list of outside collaborators, select the **X collaborators selected...** dropdown menu, and click **Remove from all repositories**.
-7. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**.
+
-  ![List of outside collaborators who will be removed and Remove outside collaborators button](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png)
+   ![Screenshot of the list of outside collaborators. Above the list, a dropdown menu, labeled "2 collaborators selected..." is outlined in dark orange.](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png)
+1. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**.
 
 ## Removing an outside collaborator from a particular repository in an organization
 
@@ -59,7 +60,6 @@ If you only want to remove an outside collaborator from certain repositories in
 7. To completely remove the outside collaborator's access to the repository, in the upper right corner, click **Remove access to this repository**.
 ![Remove access to this repository button](/assets/images/help/organizations/remove-access-to-this-repository.png)
 8. To confirm, click **Remove access**.
-![Confirm outside collaborator who will be removed from the repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png)
 
 You can also remove an outside collaborator from a repository in the access overview in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)."
 

content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md

@@ -25,7 +25,7 @@ You have a few options to convert your legacy Owners team:
 
 {% tip %}
 
-   **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+   **Note:** Because "admin" is a term for organization members with specific access to certain repositories in the organization, we recommend you avoid that term in any team name you decide on. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% endtip %}
 
@@ -33,13 +33,11 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. In the team name field, choose a new name for the Owners team. For example:
+1. In the team name field, choose a new name for the Owners team. For example:
     - If very few members of your organization were members of the Owners team, you might name the team "Core".
     - If all members of your organization were members of the Owners team so that they could [@mention teams](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams), you might name the team "Employees".
-  ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png)
+1. Under the team description, click **Save and continue**.
-6. Under the team description, click **Save and continue**.
+1. Optionally, make the team public. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/changing-team-visibility)."
-![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png)
-7. Optionally, [make the team *public*](/organizations/organizing-members-into-teams/changing-team-visibility).
 
 ## Delete the legacy Owners team
 
@@ -54,4 +52,3 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
 5. At the bottom of the page, review the warning and click **Delete the Owners team**.
-  ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png)

content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md

@@ -15,6 +15,8 @@ topics:
 shortTitle: Migrate admin team
 ---
 
+## About migrations for legacy admin teams
+
 By default, all organization members can create repositories. If you restrict [repository creation permissions](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization) to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories.
 
 Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
@@ -35,9 +37,7 @@ For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-yo
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Review your organization's legacy admin teams, then click **Migrate all teams**.
-  ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.**
-  ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
 
 ## Migrating a single admin team
 
@@ -45,4 +45,3 @@ For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-yo
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 1. In the team description box, click **Migrate team**.
-  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)

content/organizations/organizing-members-into-teams/about-teams.md

@@ -14,17 +14,15 @@ topics:
   - Teams
 ---
 
-![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png)
+## About teams
 
-Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
+You can use teams to organize, mention, and manage access for people in an organization. Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
 
 For more information, see:
 - "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
 - "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams)"
 - "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)"
 
-![Image of a team mention](/assets/images/help/teams/team-mention.png)
-
 {% ifversion ghes %}
 
 You can also use LDAP Sync to synchronize {% data variables.location.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap#enabling-ldap-sync)."
@@ -55,12 +53,8 @@ Child teams inherit the parent's access permissions, simplifying permissions man
 
 For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification.
 
-![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png)
-
 To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team.
 
-![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png)
-
 You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[AUTOTITLE](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)."
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}

content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md

@@ -23,7 +23,6 @@ shortTitle: Add members to a team
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
 6. Above the list of team members, click **Add a member**.
-![Add member button](/assets/images/help/teams/add-member-button.png)
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 

content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md

@@ -43,9 +43,10 @@ Before you can promote an organization member to team maintainer, the person mus
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-4. Select the person or people you'd like to promote to team maintainer.
+1. Select the person or people you'd like to promote to team maintainer.
-![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
+
-5. Above the list of team members, use the drop-down menu and click **Change role...**.
+   ![Screenshot of the first user in a list of team members. To the left of the user, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/team-member-check-box.png)
-![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+1. Above the list of team members, use the drop-down menu and click **Change role...**.
-6. Select a new role and click **Change role**.
+
-![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png)
+   {% data reusables.organizations.bulk-edit-team-members %}
+1. Select a new role, then click **Change role**.

content/organizations/organizing-members-into-teams/changing-team-visibility.md

@@ -25,9 +25,10 @@ topics:
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.teams %}
-3. Select the team or teams whose visibility you'd like to change.
+1. Select the team or teams whose visibility you'd like to change.
-  ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png)
+
-4. Above the list of teams, use the drop-down menu and click **Change visibility**.
+   ![Screenshot of the first two teams in the list of teams. To the left of each team, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-teams-selected.png)
-  ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png)
+1. Above the list of teams, use the drop-down menu and click **Change visibility**.
-5. Choose whether to make the team or teams visible or secret, then click **Change visibility**.
+
-  ![Radio buttons for making a team visible or secret and Change visibility button](/assets/images/help/teams/select-and-confirm-new-visibility.png)
+   {% data reusables.organizations.bulk-edit-team-dropdown %}
+1. Select a visibility, then click **Change visibility**.

content/organizations/organizing-members-into-teams/creating-a-team.md

@@ -28,8 +28,7 @@ Only organization owners and maintainers of a parent team can create a new child
 {% ifversion ghec %}
 1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team.
     * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
-    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+    * If your organization or enterprise account uses team synchronization, under "Identity Provider Groups", select the **Select Groups** dropdown menu, and click up to five identity provider groups to connect to the new team. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
 {% endif %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}

content/organizations/organizing-members-into-teams/deleting-a-team.md

@@ -23,9 +23,10 @@ topics:
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.teams %}
-4. Select the team or teams you'd like to delete.
+1. Select the team or teams you'd like to delete.
-  ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png)
+
-5. Above the list of teams, use the drop-down menu and click **Delete**.
+   ![Screenshot of the first two teams in the list of teams. To the left of each team, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/list-of-teams-selected.png)
-  ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png)
+1. Above the list of teams, select the **X teams selected** dropdown menu and click **Delete**.
-6. Review the team or teams that will be deleted, then click **I understand, delete teams**.
+
-  ![List of teams that will be deleted and Delete teams button](/assets/images/help/teams/confirm-delete-teams-bulk.png)
+   {% data reusables.organizations.bulk-edit-team-dropdown %}
+1. Review the team or teams that will be deleted, then click **I understand, delete teams**.

content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md

@@ -38,9 +38,9 @@ When code owners are automatically requested for review, the team is still remov
 
 ### Routing algorithms
 
-Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. 
+Code review assignments automatically choose and assign reviewers based on one of two possible algorithms.
 
-The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. 
+The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have.
 
 The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
 
@@ -57,14 +57,13 @@ Any team members that have set their status to "Busy" will not be selected for r
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
 {% endif %}
 1. Select **Only notify requested team members.**
-![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
 1. Click **Save changes**.
 {% endif %}
 
 ## Configuring auto assignment
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
@@ -73,26 +72,21 @@ Any team members that have set their status to "Busy" will not be selected for r
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
 {% endif %}
 1. Select **Enable auto assignment**.
-![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
+1. Under "How many team members should be assigned to review?", select the dropdown menu and choose a number of reviewers to be assigned to each pull request.
-1. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
+1. Under "Routing algorithm", use the dropdown menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
-![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png)
-1. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
-![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png)
 1. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
-![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png)
 1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
 1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
 1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
 1. Click **Save changes**.
 
 ## Disabling auto assignment
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-1. Select **Enable auto assignment** to remove the checkmark.
+1. Deselect **Enable auto assignment**.
-![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png)
 1. Click **Save changes**.

content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md

@@ -32,15 +32,12 @@ Organization owners can change the parent of any team. Team maintainers can chan
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team whose parent you'd like to change.
+1. In the list of teams, click the name of the team whose parent you'd like to change.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
 {% data reusables.organizations.team_settings %}
-6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**.
+1. Under "Parent team", select the **Select a parent team** dropdown menu and either click a parent team, or, to remove an existing parent, click **Clear selected value**.
-  ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png)
+1. Click **Update**.
-7. Click **Update**.
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm new parent team**.
+1. Click **Confirm new parent team**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
 
 ## Further reading
 

content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md

@@ -16,12 +16,14 @@ topics:
 shortTitle: Remove members
 ---
 
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}  
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
-4. Select the person or people you'd like to remove.
+1. Select the person or people you'd like to remove.
-  ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
+
-5. Above the list of team members, use the drop-down menu and click **Remove from team**.
+   ![Screenshot of the first user in a list of team members. To the left of the user, a checkbox is checked and outlined in dark orange.](/assets/images/help/teams/team-member-check-box.png)
-  ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+1. Above the list of team members, use the drop-down menu and click **Remove from team**.
+
+   {% data reusables.organizations.bulk-edit-team-members %}

content/organizations/organizing-members-into-teams/renaming-a-team.md

@@ -18,6 +18,6 @@ topics:
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. Type a new name or description for the team.
+1. In the "Team name" field, type a new name for the team.
-  ![Fields for team name and description](/assets/images/help/teams/team-name-description.png)
+1. Optionally, in the "Description" field, type a new description of the team.
-6. Click **Update**.
+1. Click **Update**.

content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md

@@ -24,17 +24,14 @@ If you're an organization owner or you have team maintainer permissions in both
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team where you'd like to add the child team.
+1. In the list of teams, click the name of the team where you'd like to add the child team.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
+1. At the top of the team page, click {% octicon "people" aria-label="" %} **Teams**.
-5. At the top of the team page, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+
-  ![Teams tab on a team page](/assets/images/help/teams/team-teams-tab.png)
+   ![Screenshot of the header of a team's page. A tab, labeled with a people icon and "Teams", is outlined in dark orange.](/assets/images/help/teams/team-teams-tab.png)
-6. Click **Add a team**.
+1. Click **Add a team**.
-  ![Add a team button on a team page](/assets/images/help/teams/add-a-team.png)
+1. Type the name of the team you'd like to add as a child team, and click the team in the results.
-7. Type the name of the team you'd like to add as a child team, and select it from the drop-down list.
-  ![Text box to type and drop-down menu to select the name of the child team](/assets/images/help/teams/type-child-team-name.png)
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm changes** to send a request to add the child team.
+1. To send a request to add the child team, click **Confirm changes**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
 
 ## Further reading
 

content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md

@@ -24,15 +24,12 @@ If you're an organization owner or you have team maintainer permissions in the c
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team you'd like to nest under a parent.
+1. In the list of teams, click the name of the team you'd like to nest under a parent.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
 {% data reusables.organizations.team_settings %}
-6. Under "Parent team", use the "Select parent team" drop-down menu and click the name of the new parent team.
+1. Under "Parent team", select the **Select a parent team** dropdown menu and click the name of the new parent team.
-  ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png)
+1. Click **Save changes**.
-7. Click **Save changes**.
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm changes** to send a request to add or change your team's parent.
+1. To send a request to add or change your team's parent, click **Confirm changes**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
 
 ## Further reading
 

content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md

@@ -21,7 +21,5 @@ Unless you set a profile picture for a team, the team profile picture will match
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. Click **Upload new picture** and select your desired profile picture.
+5. Under "Profile picture", click **Upload new picture**, then select your desired profile picture.
-![Upload new picture](/assets/images/help/teams/org-team-profile-picture-upload.png)
 6. Click and drag to crop the image as needed, then click **Set new team avatar**.
-![Set new team avatar](/assets/images/help/teams/org-team-set-new-team-avatar.png)

content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md

@@ -87,12 +87,12 @@ When you connect an IdP group to a {% data variables.product.product_name %} tea
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion ghec %}
+{%- ifversion ghec %}
-6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups.
+1. Under "Identity Provider Groups", select the **Select Groups** dropdown menu, and click up to 5 identity provider groups.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+{%- elsif ghae %}
-6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list.
+1. Under "Identity Provider Group", select the **Select Group** dropdown menu, and click an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+{%- endif %}
-7. Click **Save changes**.
+1. Click **Save changes**.
 
 ## Disconnecting an IdP group from a team
 
@@ -102,9 +102,11 @@ If you disconnect an IdP group from a {% data variables.product.prodname_dotcom
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion ghec %}
+{%- ifversion ghec %}
-6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
+1. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="Remove group" %}.
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+{%- elsif ghae %}
-6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
+1. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="Remove group" %}.
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+
-7. Click **Save changes**.
+   ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
+{%- endif %}
+1. Click **Save changes**.

data/reusables/identity-and-permissions/enable-team-sync-azure.md

@@ -1,2 +1 @@
 1. Under "Team synchronization", click **Enable for Azure AD**.
-  ![Enable team synchronization button on security settings page](/assets/images/help/teams/enable-team-synchronization.png)

data/reusables/identity-and-permissions/enable-team-sync-okta.md

@@ -1,2 +1 @@
 1. Under "Team synchronization", click **Enable for Okta**.
-  ![Enable team synchronization for Okta button on security settings page](/assets/images/help/teams/enable-team-synchronization-okta.png)

data/reusables/identity-and-permissions/team-sync-confirm.md

@@ -1,4 +1,3 @@
 5. Confirm team synchronization.
     - If you have IdP access, click **Enable team synchronization**. You'll be redirected to your identity provider's SAML SSO page and asked to select your account and review the requested permissions.
     - If you don't have IdP access, copy the IdP redirect link and share it with your IdP administrator to continue enabling team synchronization.
-    ![Enable team synchronization redirect button](/assets/images/help/teams/confirm-team-synchronization-redirect.png)

data/reusables/organizations/bulk-edit-team-dropdown.md

@@ -0,0 +1 @@
+   ![Screenshot of the "Teams" page. Above the list of teams, a dropdown menu, labeled "2 teams selected", is outlined in dark orange.](/assets/images/help/teams/bulk-edit-drop-down.png)

data/reusables/organizations/bulk-edit-team-members.md

@@ -0,0 +1 @@
+   ![Screenshot of a team's "Members" page. Above the list of team members, a dropdown menu, labeled "2 members selected", is outlined in dark orange.](/assets/images/help/teams/team-member-bulk-management.png)

data/reusables/organizations/convert-owners-team-confirm.md

@@ -1,2 +1 @@
 1. Under the description of the new owner role, click **Okay, got it**.
-![Description of the new owners role with Okay got it button highlighted](/assets/images/help/teams/okay-got-it.png)

data/reusables/organizations/create-team-choose-parent.md

@@ -1,2 +1 @@
-6. Optionally, if you're creating a [child team](/organizations/organizing-members-into-teams/about-teams#nested-teams), use the drop-down menu to choose a parent team for your new team.
+6. Optionally, if you're creating a child team, under "Parent team", select the **Select a parent team** dropdown menu and click a parent team. For more information about child teams, see "[About teams](/organizations/organizing-members-into-teams/about-teams#nested-teams)."
-  ![Drop-down menu listing the organization's existing teams](/assets/images/help/teams/choose-parent-team.png)

data/reusables/organizations/new_team.md

@@ -1,8 +1,7 @@
-1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+1. Under your organization name, click {% octicon "people" aria-label="" %} **Teams**.
   {% ifversion fpt or ghes or ghec %}
   ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
   {% else %}
   ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
   {% endif %}
-1. On the right side of the Teams tab, click **New team**.
+1. At the top of the page, click **New team**.
-  ![New team button](/assets/images/help/teams/new-team-button.png)

data/reusables/organizations/owners-team.md

@@ -4,5 +4,4 @@
   {% else %}
   ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
   {% endif %}
-1. On the Teams tab, click **Owners**.
+1. In the list of teams, click **Owners**.
-  ![Owners team selected](/assets/images/help/teams/owners-team.png)

data/reusables/organizations/review-team-repository-access.md

@@ -1,2 +1 @@
 1. Review the list of repositories that the new team member will have access to, then click **Add _USERNAME_ to _TEAMNAME_**.
-  ![Modal box with a list of the repositories the new team member will have access to and confirmation button](/assets/images/help/teams/add-team-member-repo-perms.png)