> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/portal/playbook-mdm/deployment-groups.md).

# Deployment Groups

## User Guide: Playbook MDM <a href="#user-guide-playbook-mdm" id="user-guide-playbook-mdm"></a>

### Deployment Groups <a href="#deployment-groups" id="deployment-groups"></a>

The [***Deployment Groups***](https://ems.bluefletch.com/deploymentGroups) subtab within ***Playbook MDM*** manages the various groups of devices found across the organization. A deployment group represents a logical collection of devices that all need the same applications, site lists, configuration files, and other properties. A deployment group could be created for all the devices in one store, or a region of stores, for example, depending on the needs of the organization. Adding a device to a specific deployment groups tells it which playbook it will run, and therefore which plays it must have to be in compliance with the organization's needs.

#### Create New Deployment Group <a href="#create-new-deployment-group" id="create-new-deployment-group"></a>

1. To add a deployment group, press the **New Group** button.
2. On the ***Create New Deployment Group*** editor page, enter content in the *Name* field. This is the only field required to save the deployment group.
3. Enter content in the *Version* field if desired.
4. Select one of the organization's playbooks from the *Playbook* dropdown if desired. The deployment group can also be linked to a playbook from the [***Playbooks***](https://ems.bluefletch.com/playbook/playbooks) subtab when [creating or editing the playbook](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/portal/playbook-mdm/playbooks.md).
5. Press **Save** to save the new deployment group and return to the ***Deployment Groups*** list page.

#### Manage Deployment Groups <a href="#manage-deployment-groups" id="manage-deployment-groups"></a>

1. To add a device that is not currently in any deployment group, press the **Show Barcode** button on a specific deployment group card to display its enrollment QR code. On the device, open the Playbook Agent application to access its barcode scanner screen and scan the code to start the initial sync of that deployment group's playbook on the device. After scanning, press **Hide Barcode** on the deployment group card to no longer display the barcode. For more details on this process, see the documentation on [deploying the application suite from the BlueFletch Portal](https://docs.bluefletch.com/bluefletch-enterprise/technical-documentation/deploying-bluefletch-enterprise.md).
2. Press the **Go to Devices** button on a deployment group card to navigate to the [***Devices***](https://ems.bluefletch.com/playbook/devices) page. The device list will be automatically filtered to display only the devices that belong to that deployment group.
3. Press **Edit** on a deployment group card to navigate to the ***Editing Deployment Groups*** editor page. Changes can be made here to the deployment group's *Name*, *Version*, or *Playbook* fields.
4. Press **Delete** on a card to delete that particular deployment group. Confirm intention to delete in a pop-up alert box. If the deployment group still has devices in it, all devices will be unassigned from the deployment group.


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/portal/playbook-mdm/deployment-groups.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.
