> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/product-tree.md).

# Product Tree for ConfigMgr Apps in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The *Product Tree* in Patch My PC (PMPC) Publisher is where you choose which updates the Publisher should publish in your environment and keep up to date. The tree is a hierarchical view that lets you enable updates at different levels of granularity, from all products for a vendor down to individual products.

{% hint style="info" %}
**Note**

As the Product Tree is used in several places, to avoid duplicating content, see [Product Tree in Patch My PC Publisher](/patch-my-pc-publisher/fundamentals/product-tree/overview.md) for more information and guidance on working with it.
{% endhint %}

{% hint style="success" %}
**Tip**

For more details on product naming conventions in the product tree, refer to [Catalog Information](/patch-my-pc-publisher/technical-references/catalog-information.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/product-tree.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.