> 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/technical-references.md).

# Technical references for Patch My PC Publisher

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

Welcome to the Technical references section for Patch My PC (PMPC) Publisher.

This section contains articles providing technical reference-related information for PMPC Publisher.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><a href="/patch-my-pc-publisher/technical-references/access-permissions-reference.md"><strong>Access and Permissions Reference</strong></a><br>Understand how access to Publisher is controlled </td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/configure-sms-provider.md"><strong>Configure the SMS Provider Connection</strong></a><br>Learn how to configure the SMS Provider for Publisher</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/catalog-information.md"><strong>Catalog Information</strong></a><br>Understand the naming conventions used in the Patch My PC Catalog</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/data-flow-diagram.md"><strong>Data Flow Diagram</strong></a><br>Learn where Publisher sits in the overall update workflow</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/example-email-alerts.md"><strong>Example Email Alerts</strong></a><br>Examples of emails Publisher sends (if configured) at the end of a Publisher sync</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/gsma-support.md"><strong>gMSA Support</strong></a><br>Learn about Publisher's support for group Managed Service Account (gMSA)</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/log-file-reference.md"><strong>Log File Reference</strong></a><br>A reference list of various log files created by Publisher to record its activities</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/list-product-statistics.md"><strong>List of Product Statistics</strong></a><br>Understand the optional <em>Statistics</em> Publisher offers</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/multi-tenant-support.md"><strong>Multi-tenant Support</strong><br></a>If you are an MSP, learn how Publisher can support multiple Intune tenants</td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/products-available-limited-trial-mode.md"><strong>Products Available in Limited Trial Mode</strong></a><br>See which products are available in Publisher's <strong>Limited Trial Mode</strong></td></tr><tr><td><a href="/patch-my-pc-publisher/technical-references/telemetry-data-collected.md"><strong>Telemetry Data collected</strong></a><br>See the telemetry data collected by Publisher, which helps us monitor and improve our products and services</td></tr></tbody></table>


---

# 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/technical-references.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.