> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/advanced-settings/bots.md).

# Bots

OneSite Patch bots are tools that give you finer control over your deployments and notifications beyond what's possible with a simple Strategy. Bots are only available as part of an [Advanced Strategy](/patch/patching-fundamentals/patch-strategies.md). You can get to bots settings either via the Advanced Strategy template or you can set them up in advance and reference them when you get to that part of the Advanced Strategy process (**Advanced Settings > Intent Schema > Bots**).

There are two types of Patch bots:

* [Deployment bots](/patch/advanced-settings/bots/bots-deployment.md)
* [Notification bots](/patch/advanced-settings/bots/bots-notification.md)

Deployment bots are used for filtering, for instance, if you want to create special rules for zero-day patches or patches flagged as critical. By using a deployment bot, you can define different user interaction settings, or set deployment or reboot windows based on urgency.

Notification bots are used when you want to send notifications to any audience beyond approvers. Perhaps you want to alert administrators about a release or inform interested parties about newly published updates.

OneSite Patch provides templates for the most-common scenarios, but you can also create custom bots for your specific business needs.

![Example of criticality templates for Deployment bots](/files/71ogmAIvdvonODVX0b1T)

### Bot Settings

Bot settings are responsible for defining the bot's behavior and controlling what occurs when the bot processes a patch that matches the filter.

The first aspect to consider is whether the bot settings should be manually provided or if a custom workflow should be utilized to dynamically configure the bot settings.

In most cases, the default setting (Deployment Settings) would be the most suitable and commonly used.

When the **Bot Settings** radio button is toggled, the available form options change accordingly.

![Complete settings screen](/files/sB4L6zQnoZKLMmjddV8b)

The bot templates include the following settings:

* **Bot Settings:** Used by both Deployment bots and Notification bots. Use the Deployment/Notification Settings unless you have a complex workflow. To create a bot workflow, enter a support ticket and request help from [Adaptiva Customer Support](https://adaptiva.com/support).
* **Desired State:** Used by Deployment bots only. Specifies what action the Deployment bot takes:
  * **Mandatory Install:** Force installation onto the end-user device.
  * **Do Not Install:** Do not install onto the end-user device.
  * **Rollback:** Roll back the patch to the last approved version.
  * **Uninstall:** Perform an uninstallation of the patch.
* **Urgency:** Used by both Deployment bots and Notification bots to specify the urgency setting (**Low**, **Normal**, **High**, **Critical**) for patches or notifications that meet the patch filter requirements. The bot compares this setting against the urgency defined in the Patching Strategy or Deployment Channel to which this bot belongs. If the urgency settings do not match, the bot does not deploy or send a notification.
* **Business Units:** Deployment bots only. Business Units are a fundamental organizational unit in OneSite Patch, and logically group and manage devices, settings, and other resources according to business needs. Groupings include geographic location, department, or business function. If no Business Units are added, patches will be approved for all Business Units in the Patching Strategy. For details, see [Business Units](/patch/patching-fundamentals/business-units.md).
* **Output Expression:** Notification bots only. The Output Expression is a free text field used to enter the text of the notification, for example, the body of an email or a text message.
* **Communication Providers:** Notification bots only. Communication Provider settings define the type of communication to send when a bot processes a patch that matches the Filter Settings. Choose one or more of the built-in **Communication Providers**.