> 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/fundamentals/about-interface.md).

# About the Patch My PC Publisher Interface

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

The Patch My PC (PMPC) Publisher interface consists of the following tabs down the left-hand side:

<table data-search="false"><thead><tr><th width="148.99993896484375" valign="top">Tab</th><th valign="top">Used to...</th></tr></thead><tbody><tr><td valign="top">General</td><td valign="top">Provide a high-level view of Publisher’s licensing status, usage information, and other core administrative settings.</td></tr><tr><td valign="top">WSUS Updates</td><td valign="top">Configure and customize third-party updates for Microsoft Windows Server Update Services (WSUS).</td></tr><tr><td valign="top">ConfigMgr Apps</td><td valign="top">Configure and customize third-party updates for Microsoft Configuration Manager (ConfigMgr).</td></tr><tr><td valign="top">Intune Apps</td><td valign="top">Configure and customize third-party apps for Microsoft Intune.</td></tr><tr><td valign="top">Intune Updates</td><td valign="top">Configure and customize third-party updates for Microsoft Intune.</td></tr><tr><td valign="top">Sync Schedule</td><td valign="top">Control when Publisher runs an automated publishing sync.</td></tr><tr><td valign="top">Alerts</td><td valign="top">Provide visibility into publishing activity and operational events.</td></tr><tr><td valign="top">Advanced</td><td valign="top">Provide configuration options used to customize Publisher behavior beyond standard publishing settings.</td></tr><tr><td valign="top">Cloud</td><td valign="top">Connect Publisher to PMPC Cloud and manage the connection.</td></tr><tr><td valign="top">About</td><td valign="top">Show version and support information</td></tr></tbody></table>

Clicking a tab displays more relevant information in the right-hand *details* window, and if a tab also contains child tabs, the parent tab automatically expands to reveal any child tabs.

Regardless of the tab selected, at the bottom of Publisher you will find the following items:

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><a href="#theme-control">Theme Control</a></td><td valign="top"><a href="#show-granted-permissions-shield">Show Granted Permissions Shield</a></td><td valign="top"><a href="#version-number">Version Number</a></td><td valign="top"><a href="#action-buttons">Action Buttons</a></td></tr></tbody></table>

## Theme Control

The *Theme Control* lets you decide which theme to use to display the Publisher.

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

See [Switch Themes](/patch-my-pc-publisher/fundamentals/switch-themes.md) for more information on how to switch themes and examples.
{% endhint %}

## Show Granted Permissions Shield

Clicking the *Show Granted Permissions* shield (![Show Granted Permissions Shield](/files/ZqNujkCNt66qNAGpGvad)) at the bottom of the Publisher UI opens the read-only **Permissions** screen showing a list of every Publisher permission and whether your account currently holds it, resolved against the server you are connected to.

This works the same regardless of the Settings console being accessed locally or remotely, so you can confirm your effective access at any time.

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

See the [Access and Permissions Reference](/patch-my-pc-publisher/remote-ui/technical-references/access-permissions-reference.md) for more information about these permissions.
{% endhint %}

<figure><img src="/files/qrLfACa0T3MFQFDY2qqX" alt=""><figcaption></figcaption></figure>

## Version Number

Underneath the Theme Control is the *Version* number field showing which version of Publisher you are currently running.

For example **3.x.x.x**

## Action Buttons

The *Action Buttons* are used as follows:

<table><thead><tr><th width="161.22222900390625" valign="top">Button</th><th valign="top">Used to...</th></tr></thead><tbody><tr><td valign="top">Logs</td><td valign="top"><a href="/pages/hT7iWrZ0mD7DBCwUrfnX">Manage log files in Publisher</a></td></tr><tr><td valign="top">Save and Close</td><td valign="top">Save any changes and quit Publisher.</td></tr><tr><td valign="top">Cancel</td><td valign="top">Cancel any changes and quit Publisher. If you have unsaved changes, you will be prompted to save them, if you choose to.</td></tr><tr><td valign="top">Apply</td><td valign="top">Apply (save) any changes without quitting Publisher (only available if you have made a change and not applied/saved it).</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/fundamentals/about-interface.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.