prereqs

Author: chcomley

docs/boards/backlogs/work-item-template.md

@@ -145,11 +145,10 @@ As shown in the following table, a ✔️ indicates the task is available from t
 
 ## Prerequisites
 
-- To manage work item templates in the web portal, you need to join the team that owns them. You can then add, edit, or delete templates as needed.
-
-- You need to be a project Contributor and a team member to use work item templates in the web portal. You can then apply templates to existing work items. 
-
-- To add, capture, or edit work item templates through Visual Studio Team Explorer, install the [Microsoft Visual Studio Team Foundation Server 2015 Power Tools](https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer2015Power). These templates only appear in your view of Team Explorer. 
+- **Permissions**: 
+  - To manage work item templates in the web portal, be a member of the team that owns them. You can then add, edit, or delete templates as needed.
+  - To use work item templates in the web portal, be a **Contributor** to the project. You can then apply templates to existing work items. 
+- **Tools**: To add, capture, or edit work item templates through Visual Studio Team Explorer, install the [Microsoft Visual Studio Team Foundation Server 2015 Power Tools](https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer2015Power). These templates only appear in your view of Team Explorer. 
 
 <a id="capture"> </a> 
 

docs/boards/boards/add-run-update-tests.md

@@ -29,22 +29,18 @@ Tests that you create from the board automatically get linked to the user story
   - [Connect to a project](../get-started/sign-up-invite-teammates.md). If you don't have a project, create one.
   - [Add yourself to a team or project](../../organizations/security/add-users-team-project.md).
 
-- **Access levels:**
-  - Ensure you have [**Basic** access or higher](../../organizations/security/access-levels.md) to add work items and use all board features.
-  - Verify you have **Basic** access or higher to view or run tests. Users with **Stakeholder** access can't view or run tests.
+- **Access levels:** To add work items, view or run tests, and use all boards features, have at least [**Basic** access](../../organizations/security/access-levels.md). Users with **Stakeholder** access can't view or run tests.
 
 - **Permissions:**
-  - Set **View work items in this node** and **Edit work items in this node** permissions to **Allow** to view or modify work items. By default, the **Contributors** group has these permissions. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). 
+  - To view or modify work items, set **View work items in this node** and **Edit work items in this node** permissions to **Allow**. By default, the **Contributors** group has these permissions. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
 - **Project and team access:**
   - [Connect to a project](../../organizations/projects/create-project.md). If you don't have a project, create one.
   - [Add yourself to a team or project](../../organizations/security/add-users-team-project.md).
 
-- **Access levels:**
-  - Ensure you have [**Basic** access or higher](../../organizations/security/access-levels.md) to add work items and use all board features.
-  - Verify you have **Basic** access or higher to view or run tests. Users with **Stakeholder** access can't view or run tests.
+- **Access levels:** To add work items, view or run tests, and use all board features, have at least [**Basic** access](../../organizations/security/access-levels.md). Users with **Stakeholder** access can't view or run tests.
 
 - **Permissions:**
   - Set **View work items in this node** and **Edit work items in this node** permissions to **Allow** to view or modify work items. By default, the **Contributors** group has these permissions. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).

docs/boards/boards/customize-cards.md

@@ -24,7 +24,7 @@ A board presents work items in the form of cards, where each card represents a w
 ## Prerequisites
 
 [!INCLUDE [temp](../includes/prerequisites-team-settings.md)]
-- See the section, [Card customization sequence](#card-customization-sequence)
+- **Tasks (optional)**: See the section, [Card customization sequence](#card-customization-sequence)
 
 ## Card customization options  
 
@@ -62,7 +62,7 @@ Within the [Settings dialog for a board](#open-your-board-settings), you have th
 
 ## Card customization sequence 
 
-Before you configure the cards, make sure the following tasks are complete, or you might need to revisit your configuration.  
+Before you configure the cards, ensure the following tasks are complete, or you might need to revisit your configuration.  
 
 **Process Administrator**: 
 1. Add custom work item types that you want to appear on your backlog or board. For more information, see [Add and manage work item types](../../organizations/settings/work/customize-process-work-item-type.md).

docs/boards/github/install-github-app.md

@@ -21,9 +21,9 @@ For an overview of the integration that the Azure Boards app for GitHub supports
 ## Prerequisites 
 
 **Permissions:**
-- You must be an **administrator** or **owner** of the GitHub organization to install the Azure Boards app.
-- You must have **Read** permissions for the GitHub repository.
-- You must be a member of the [**Project Collection Administrators** group](../../organizations/security/change-organization-collection-level-permissions.md). If you created the project, you already have these permissions.
+- Be an **administrator** or **owner** of the GitHub organization to install the Azure Boards app.
+- Have **Read** permissions for the GitHub repository.
+- Be a member of the [**Project Collection Administrators** group](../../organizations/security/change-organization-collection-level-permissions.md). If you created the project, you already have these permissions.
 
 > [!IMPORTANT]  
 > If your repository is already connected via another authentication type such as OAuth, you must remove that repository from your existing connection before you re-connect it via the GitHub App. Follow the steps provided in [Add or remove GitHub repositories](#add-remove-repos) later in this article before you configure the GitHub App.

docs/boards/github/link-to-from-github.md

@@ -25,7 +25,7 @@ In this article, learn how to link work items to GitHub commits, pull requests,
   - Ensure your Azure Boards project is connected to the GitHub repository where the commits, pull requests, and branch you want to link to/from exist. For more information, see [Azure Boards-GitHub integration](index.md).
 
 - **Permissions:**
-  - Be a Contributor to both the Azure Boards project and the GitHub repository.
+  - Be a **Contributor** to both the Azure Boards project and the GitHub repository.
 
 ::: moniker range="azure-devops"
 > [!NOTE]   

docs/boards/includes/prerequisites-team-settings.md

@@ -9,13 +9,13 @@ ms.date: 07/30/2024
 
 ::: moniker range="azure-devops"
 
-- **[Access levels](../../organizations/security/access-levels.md):** Have at least **Basic** access.
+- **Access levels:** Have at least [**Basic**](../../organizations/security/access-levels.md) access.
 - **Permissions:** To configure team settings, be part of the **Project Administrators** security group or [have the **Team Administrator** role](../../organizations/settings/add-team-administrator.md). For more information, see [Change project-level permissions](../../organizations/security/change-project-level-permissions.md).
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
- - **[Access levels](../../organizations/security/access-levels.md):** Have at least **Basic** access.
+ - **Access levels:** Have at least [**Basic**](../../organizations/security/access-levels.md) access.
 - **Permissions:** To configure team settings, be part of the **Project Administrators** security group or [have the **Team Administrator** role](../../organizations/settings/add-team-administrator.md). For more information, see [Change project-level permissions](../../organizations/security/change-project-level-permissions.md).
 
 ::: moniker-end

docs/boards/includes/prerequisites-work-items.md

@@ -10,10 +10,15 @@ ms.date: 10/02/2024
 - **Project access:** Be a [project member](../../organizations/security/add-users-team-project.md).
 
 - **Permissions:**
-  - Have **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has these permissions. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).
-  - To add new tags to work items, have at least **Basic** access and the project-level **Create new tag definition** permission set to **Allow**. By default, the **Contributors** group has this permission.
+  - To view, follow, and edit work items, have **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has these permissions. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).
+-	To add tags to work items, have the project-level **Create new tag definition** permission set to **Allow**. By default, the **Contributors** group has this permission.
 
-    > [!NOTE]
-    > **Stakeholders** can't add new tags, even if the permission is explicitly set, due to their access level. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
+- **Access levels**: 
+  -	To add new tags to work items or to view or follow pull requests, have at least **Basic** access.  
+  -	To view or follow work items, have at least **Stakeholder** access. For more information, see [About access levels](../../organizations/security/access-levels.md).
+  - All project members, including those in the **Readers** group, can send emails containing work items.
+
+  > [!NOTE]
+  > - Provide [Stakeholder access](../../organizations/security/access-levels.md) to members who want to contribute to the discussion and review progress. These are typically members who don't contribute to code, but want to view work items, backlogs, boards, and dashboards. 
+  > - **Stakeholders** can't add new tags, even if the permission is explicitly set, due to their access level. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
 
-- **Email work items:** All project members, including those in the **Readers** group, can send emails containing work items.

docs/boards/includes/prerequisites.md

@@ -3,33 +3,27 @@ ms.service: azure-devops-boards
 ms.author: chcomley
 author: chcomley
 ms.topic: include
-ms.date: 11/02/2023
+ms.date: 11/21/2024
 ---
 
 
 ## Prerequisites
 
-When you create a project or a team, backlogs get created automatically. Each team has access to their own product, portfolio, and sprint backlogs.
-
 ::: moniker range="azure-devops"
-
-|Prerequisite  |Description  |
-|---------|---------|
-|Project Administrator or Contributor member     | You must be [added to a project](../../organizations/security/add-users-team-project.md) as a member of the **Contributors** or **Project Administrators** security group.        |
-|Stakeholder access     | To add or modify work items, you must be granted *Stakeholder* [access or higher](../../organizations/security/stakeholder-access.md). Users with **Stakeholder** access for public projects have full access to backlog and board features, like users with **Basic** access. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).       |
-|Contributor member or Allow perms on     | To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).         |
-|Defined iterations   |To use the **Planning** pane, your team administrator must [define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).         |
-
+- **Project access**: Be a [project member](../../organizations/security/add-users-team-project.md)
+- **Permissions**: 
+  - Be a member of the **Contributors** or **Project Administrators** security group.
+  - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).
+- **Access levels**: To add or modify work items, have at least [**Basic** access](../../organizations/security/stakeholder-access.md). Users with **Stakeholder** access for public projects have full access to backlog and board features, like users with **Basic** access. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
+- **Defined iterations**: To use the **Planning** pane, ensure your team administrator [defined iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
-
-|Prerequisite  |Description  |
-|---------|---------|
-|Project Administrator or Contributor member     | You must be [added to a project](../../organizations/security/add-users-team-project.md) as a member of the **Contributors** or **Project Administrators** security group.        |
-|Stakeholder access     | To add or modify work items, you must be granted *Stakeholder* [access or higher](../../organizations/security/stakeholder-access.md).        |
-|Contributor member or Allow perms on     | To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).         |
-|Defined iterations   |To use the **Planning** pane, your team administrator must [define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).         |
-
+- **Project access**: Be a [project member](../../organizations/security/add-users-team-project.md)
+- **Permissions**: 
+  - Be a member of the **Contributors** or **Project Administrators** security group.
+  - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set work tracking permissions](../../organizations/security/set-permissions-access-work-tracking.md).
+- **Access levels**: To add or modify work items, have at least [**Basic** access](../../organizations/security/stakeholder-access.md).
+- **Defined iterations**: To use the **Planning** pane, ensure your team administrator [defined iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).
 ::: moniker-end

docs/boards/work-items/auto-complete-work-items-pull-requests.md

@@ -25,6 +25,11 @@ When you link a work item to a pull request (PR), you can automatically complete
 
 For more information, see [Create, view, and manage pull requests](../../repos/git/pull-requests.md).
 
+## Prerequisites
+
+[!INCLUDE [prerequisites-work-items](../includes/prerequisites-work-items.md)]
+
+- **GitHub permissions:** Be a **Contributor** to the GitHub repository.
 
 ## Autocomplete work items  
 

docs/boards/work-items/email-work-items.md

@@ -115,16 +115,9 @@ Emailing lists of work items is a common way to share work tracking information.
 
 ## Prerequisites
 
-[!INCLUDE [temp](../includes/prerequisites-work-items.md)]
-
-> [!NOTE]   
-> Make sure you provide members of your organization [Stakeholder access](../../organizations/security/access-levels.md) who want to contribute to the discussion and review progress. These are typically members who don't contribute to code, but want to view work items, backlogs, boards, and dashboards.  
-
+[!INCLUDE [temp](../includes/prerequisites-work-items.md)] 
 
 <a id="email-print-send-links"></a>
-
-
-
 <a id="email-item"></a>
 
 ## Email a single item  

docs/boards/work-items/follow-work-items.md

@@ -43,23 +43,7 @@ This article shows you how to:
 
 ## Prerequisites
 
-::: moniker range="azure-devops"
-
-* Connect to a project. If you don't have a project yet, [create one](../get-started/sign-up-invite-teammates.md). 
-* You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md). 
-* To view or follow work items, you must be granted **Stakeholder** access or higher. For more information, see [About access levels](../../organizations/security/access-levels.md). Also, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).  
-* To view or follow pull requests, you must have **Basic** access or higher.   
-
-::: moniker-end
-
-::: moniker range="< azure-devops"
-
-* You must connect to a project. If you don't have a project yet, [create one](../../organizations/projects/create-project.md).
-* You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md). 
-* To view or follow work items, you must be granted **Stakeholder** access or higher. For more information, see [About access levels](../../organizations/security/access-levels.md). Also, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).  
-* To view or follow pull requests, you must have **Basic** access or higher.  
-
-::: moniker-end 
+[!INCLUDE [prerequisites-work-items](../includes/prerequisites-work-items.md)]
 
 ## Follow a work item