> 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/admin/enterprise.md).

# Enterprise

## User Guide: Admin Tab <a href="#user-guide-admin-tab" id="user-guide-admin-tab"></a>

### Enterprise <a href="#enterprise" id="enterprise"></a>

Administrators in organizations that have chosen to enroll in BlueFletch's Enterprise Mobility Management (EMM) toolset will have an additional subtab under ***Admin***, the ***Enterprise*** subtab. ***Enterprise*** provides settings management for the BlueFletch EMM Console. Upon first being set up with EMM capabilities by BlueFletch, an administrator can [register his or her organization with Managed Google Play](/bluefletch-enterprise/product-guides/portal/emm-console/setup/enroll-org-in-emm.md) by clicking the **Enroll Enterprise** button on this page.

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

To edit the settings for an existing enterprise, press the pencil icon. If desiring to unenroll from an enterprise, contact your BlueFletch representative.

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

#### Display Name & Logo <a href="#display-name-logo" id="display-name-logo"></a>

When editing enterprise settings, the only required field to save changes is *Enterprise Display Name*, which is empty by default. The *Enterprise Name* is a static value generated by the server during creation, in the form "enterprises/{enterpriseId}".

Using a custom [Android Device Policy Controller](https://developer.android.com/work/dpc/build-dpc) allows organizations enrolled in EMM to display a logo on their devices during enrollment. The *Logo* field uses a URL to define this logo. The *Sha256 Hash* field is automatically populated with a base-64 encoded SHA-256 hash of the URL's content upon saving the logo URL.

> **Note:** BlueFletch does not currently support custom device policy controllers and Android Enterprise is no longer accepting new registrations for them.

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

#### Primary Color <a href="#primary-color" id="primary-color"></a>

To set the enterprise's branding color that will display on the devices as certain accents on the enrollment flow screens, use the *Primary Color* field. Clicking **Edit Color** allows selection of the branding color by a spectrum, hex code, RGB values, or HSL values.

<figure><img src="/files/PRAhDFmju8xWvzB4iU0q" alt="" width="492"><figcaption></figcaption></figure>

#### Sign-In Details <a href="#sign-in-details" id="sign-in-details"></a>

Provide sign-in details for authentication if the organization's EMM device will be provisioned with a sign-in enrollment token. Only the *Sign In URL* field is required; *Sign In Enrollment Token* and *QR Code* cannot be edited; they will be automatically poulated from the sign-in URL when the enterprise settings are saved.

<figure><img src="/files/arqSRTcqdeQSeNL4KqLz" alt="" width="551"><figcaption></figcaption></figure>

#### Terms And Conditions <a href="#terms-and-conditions" id="terms-and-conditions"></a>

Submitting *Header* and *Content* field sets sections of terms and conditions that will be viewable and accepted on each device during provisioning.

<figure><img src="/files/UHOuCHeiTIjlg5p4oJQG" alt="" width="554"><figcaption></figcaption></figure>

When finished editing, press **Save** to return to the ***Enterprise*** page, where major settings such as display name and primary color will be highlighted.


---

# 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/admin/enterprise.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.