> 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/emm-console/setup/installing-playbook-in-emm.md).

# Installing Playbook in EMM

## Feature: Playbook and EMM Together <a href="#feature-playbook-and-emm-together" id="feature-playbook-and-emm-together"></a>

### Overview <a href="#overview" id="overview"></a>

This is to explain how to integrate Playbook MDM with an EMM Policy.

The general steps will allow for creating an EMM Policy that installs the enterprise installer application, Playbook Agent, during device enrollment, then allow for Playbook Agent to manage application installation via Deployment Groups and Playbooks.

**Note** This assumes your organization has access to the *EMM Console* and *Playbook MDM*.

### Flow <a href="#flow" id="flow"></a>

1. Create a Playbook and Deployment Group. This Deployment Group will be the initial group that devices will be assigned to. Make note of the Deployment Group ID.
2. Get your Organization ID.
3. Create an EMM Policy.
4. Within the EMM Policy, go to **Account & Application** tab. Add the application Playbook. The Package Name will be 'com.bluefletch.ems.staging.playbook'. (STAGING SYSTEM ONLY, needs updated for Production).
5. Edit the Application, click on 'Managed' configurations.
6. Within the Manage configurations, set the Organization Id and Deployment Group Id. Make sure to give the Managed Configuration a name.
7. Go to the EMM Policy **Provisioning** Tab.
8. Enter a 'Title', 'Description', and set the Package Name to 'com.bluefletch.ems.staging.playbook'. (STAGING SYSTEM ONLY, needs updated for Production).
9. Make other Policy changes as desired.
10. Apply now.
11. Create an Enrollment Token and enroll devices.

#### Setup Actions Example <a href="#setup-actions-example" id="setup-actions-example"></a>

<figure><img src="/files/Xy8WTOFwSb7lGf7bSdBr" alt="" width="563"><figcaption></figcaption></figure>

#### Managed Configurations Example <a href="#managed-configurations-example" id="managed-configurations-example"></a>

<figure><img src="/files/Ztm0mMnFPNROSpYxuHus" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/portal/emm-console/setup/installing-playbook-in-emm.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.