> 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-cloud/manage/settings/deployment-templates/macos-templates.md).

# Deployment Templates for macOS in Patch My PC Cloud

*Applies to: Patch My PC Cloud*

When creating a new macOS deployment template in Patch My PC (PMPC) Cloud, as we do not know which **Installer Type** the deployment this template will be applied to, the **Install App as Managed** setting on the **Configurations** tab is enabled by default and can be configured.

Obviously, the same rules for creating [macOS deployments](/patch-my-pc-cloud/macos-support/deploy-macos-app.md) apply to macOS templates; i.e., templates don’t have different logic rules than creating a deployment without a template.

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

If you try applying a template to a deployment that is configured with incompatible settings for the selected **Installer Type**, the following **Warning** notification is shown:

**Warning – Template ‘<*****template\_name*****>’ only partially applied as some template settings are incompatible with the selected Installer Type.**

Any incompatible settings are not applied. This could be because you applied the wrong template for the **Installer Type** in which case either:

* Apply the correct template.
* Switch the **Installer Type** and reapply the same template.
  {% endhint %}

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

To avoid issues applying incompatible templates when creating deployments, consider creating one template for LOB apps with the appropriate settings and another for non-LOB apps, with clear names. Then, when you create a deployment, you can easily determine which template to apply based on the **Installer Type** of the deployment.
{% 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-cloud/manage/settings/deployment-templates/macos-templates.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.