> 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/enroll-org-in-emm.md).

# Enroll Org in EMM

## Enroll Org in EMM <a href="#enroll-org-in-emm" id="enroll-org-in-emm"></a>

### How do I enroll my organization in BlueFletch's EMM? <a href="#how-do-i-enroll-my-organization-in-bluefletchs-emm" id="how-do-i-enroll-my-organization-in-bluefletchs-emm"></a>

1. Login to BlueFletch Portal as an admin.
2. Go to the *Admin* tab and select the *Enterprise* tab below.
3. Click *Enroll Enterprise*; page is transferred to a Google Play *Bring Android to Work* site.
4. Press *Sign In* to login to a Google account (NOT a G-Suite account; if logged into a G-Suite account, *Get Started* option will not be displayed).
5. Click *Get Started*.

<figure><img src="https://799338798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSxhNrDkmDAkv7QEWfOIh%2Fuploads%2Flea0gPensVW4SmJQiQXv%2Fenroll_getStarted.png?alt=media&amp;token=19e70c33-bf0c-40ce-a7cc-fbc211e406b2" alt="" width="563"><figcaption></figcaption></figure>

6. Enter business name of the organization; EMM provider should be populated by the site as “BlueFletch Mobile, LLC.”
7. *Optional*: Enter contact information for Data Protection Officer and EU Representative if the organization is subject to the European Union’s (EU) General Data Protection Regulation (GDPR). The page can be submitted with these fields empty, but they may need to be completed later. For more information, read [Android Enterprise GDPR](https://www.android.com/enterprise/data-protection/) and [Register a DPO or EU representative for the GDPR - Managed Google Play Help](https://support.google.com/googleplay/work/answer/7681629?hl=en).
8. Review and accept the Managed Play Agreement and press *Confirm*.
9. Press Complete Sign Up.
10. Return to BlueFletch *Admin* > *Enterprise* tab. A server-generated enterprise name should be listed.

### How do I customize details unique to my enterprise, such as name, logo, and terms and conditions? <a href="#how-do-i-customize-details-unique-to-my-enterprise-such-as-name-logo-and-terms-and-conditions" id="how-do-i-customize-details-unique-to-my-enterprise-such-as-name-logo-and-terms-and-conditions"></a>

1. On *Admin* > *Enterprise* tab, press the pencil icon to edit.
2. Enter a customized name in *Display Name*.
3. Enter a publicly accessible URL for the desired logo. A base-64 encoded SHA-256 hash of the URL content will populate on *Save*.
4. Under *Primary Color*, select *Edit Color*. Choose a color manually from the spectrum or by entering a 7-character HEX code.

<figure><img src="https://799338798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSxhNrDkmDAkv7QEWfOIh%2Fuploads%2FyyvpN3svgRfsssMCBXQg%2Fcustomize_logo.png?alt=media&amp;token=6af27ce3-08fe-4841-b84e-b0697f2caa5c" alt="" width="563"><figcaption></figcaption></figure>

5. Under *Signin Details*, enter Sign-in URL for authentication when device is provisioned with a sign-in enrollment token. Additional fields can be added or removed.
6. Under *Terms And Conditions*, enter header descriptions and content of the terms of use. Additional fields can be added or removed.
7. Press *Save*.


---

# 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/emm-console/setup/enroll-org-in-emm.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.