> 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/customizations/list-customizations/manage-security-scopes.md).

# Manage Security Scopes option in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*\
*Available at level: All Custom Products, All Products, Vendor, Product*\
*Available on tab: ConfigMgr Apps*

The **Manage Security Scopes** right-click option in Patch My PC (PMPC) Publisher allows you to control which Microsoft Configuration Manager (ConfigMgr) security scopes are applied to applications created by Publisher.

During each synchronization, Publisher applies the selected security scopes to any applications it creates in ConfigMgr. This ensures that applications are visible and manageable only by administrators with access to the assigned scopes.

## To configure security scope tags

1. Right-click the relevant item and select **Manage Security Scopes**. The list of available security scopes is retrieved directly from your ConfigMgr environment.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FpS5hSHOKvJVn28qO6zzc%2Fimage.png?alt=media&amp;token=063ad3f1-8b30-4ed8-b59c-de8edc304990" alt="Select Security Scopes" width="450"><figcaption></figcaption></figure>

2. On the **Select Security Scopes** screen, check the relevant checkboxes beside the security scopes you want to configure.

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

The list supports filtering using the **Filter items** field, and you can customize the visible columns by right-clicking the column headers.

You can also refresh the list using the refresh button in the top right corner.
{% endhint %}

3. You can optionally enable **Enforce selected Security Scopes** (see [Enforcing Security Scopes](#enforcing-security-scopes) for more information).
4. Click **OK**.

## Enforcing Security Scopes

When the **Enforce selected Security Scopes** checkbox is checked, Publisher ensures that only the selected security scopes remain assigned to the application. If you manually add additional scopes in the ConfigMgr console, Publisher will remove them during the next synchronization.

This option is useful when you want strict control over application visibility and want to prevent scope drift caused by manual changes.

{% hint style="danger" %}
**Important**

When Publisher runs on the ConfigMgr Site Server, no additional permissions are required. The Local System account already has the necessary rights to read and assign security scopes.

Additional permissions are required only when Publisher is installed on a remote server and connects to ConfigMgr.

If you are using a custom ConfigMgr security role for Publisher in a remote deployment, that role must include the following permissions:

* **Application | Set Security Scope**
* **Security Scopes | Read**

If you are using the Patch My PC security role that is created when [configuring the SMS Provider](https://docs.patchmypc.com/patch-my-pc-publisher/technical-references/configure-sms-provider.md) integration, these permissions are already included.
{% 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/customizations/list-customizations/manage-security-scopes.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.
