### Android Enterprise A set of APIs and other tools provided by Google for developers to build management solutions for Android devices. ### bring your own device (BYOD) A personally owned device that an employee also uses for work. Work profiles, which separate work apps from personal apps, are the recommended deployment method for BYOD devices. For more information, see [Work profile for employee-owned devices](https://developers.google.com/android/work/overview#employee-owned-devices). ### company-owned device *Formerly known as **corp-liable device*** A device owned and fully managed by an employee's organization. Company-owned devices can be set up exclusively for work use ([fully managed](https://developers.google.com/android/work/terminology#fully_managed_device)), or to allow both work and personal use ([work profile for mixed-use company-owned devices](https://developers.google.com/android/work/terminology#work_profile_for_mixed-use_company-owned_devices)). For more information, see [Company-owned devices for knowledge workers](https://developers.google.com/android/work/overview#company-owned-work-profile). ### corporate-owned, personally enabled (COPE) Deprecated. See [work profile for mixed-use company-owned devices](https://developers.google.com/android/work/terminology#work_profile_for_mixed-use_company-owned_devices). ### corp-liable device Deprecated. See [company-owned device](https://developers.google.com/android/work/terminology#company-owned_device). ### corporate-owned, single use (COSU) Deprecated. See [dedicated device](https://developers.google.com/android/work/terminology#dedicated_device). ### dedicated device *Formerly known as **corporate-owned, single use (COSU)*** A subset of company-owned devices that are locked down to a limited set of apps to serve a dedicated purpose, such as a check-in kiosk or digital signage. For more information, see [Company-owned devices for dedicated use](https://developers.google.com/android/work/overview#dedicated-devices). ### device account A term used in the Google Play EMM API developer documentation for the account on a [dedicated device](https://developers.google.com/android/work/terminology#dedicated_device). [Device accounts](https://developers.google.com/android/work/play/emm-api/user-accounts#managed_google_play_accounts) are not associated with individual users. ### device admin A mode of operation that supports legacy deployments of pre 5.0 Android devices, and allows the EMM's DPC limited control of a device. Partner support for device admin is no longer provided. For more details, see [Device admin deprecation](https://developers.google.com/android/work/device-admin-deprecation). ### device owner (DO) *Compare to [profile owner](https://developers.google.com/android/work/terminology#profile_owner_po)* The DPC installed on fully managed and dedicated devices is referred to as the device owner. ### device policy controller (DPC) An app that controls local device policies and system applications on devices. ### device provisioning The process of setting up management on a device. ### enterprise mobility management (EMM) An enterprise mobility management solution provider. EMMs provide a combination of MDM and MAM features for organizations to manage their mobile devices. ### EMM console An application created by an EMM for IT admins to manage mobile devices and apps. EMM partners are responsible for maintaining and deploying an EMM console. For more information, see [Integrate Android into your EMM solution](https://developers.google.com/android/work/overview#integrate_android_into_your_emm_solution). ### EMM partner An EMM that has followed the steps to [release an Android EMM solution](https://developers.google.com/android/work/release-solution) and has passed product review. ### EMM token A token used to bind an EMM's solution to an organization's existing managed Google domain. For details, see [managed Google domain enrollment](https://developers.google.com/android/work/play/emm-api/create-enterprise#managed_google_domain_enrollment). ### enterprise service account (ESA) An account used to manage Play EMM API resources. For details, see [Service accounts](https://developers.google.com/android/work/play/emm-api/create-enterprise#prog-esa-gen). ### fully managed device A device that is entirely managed by the user's organization, intended for company-owned devices that are used exclusively for work purposes. For more information, see [Company-owned devices for knowledge workers](https://developers.google.com/android/work/overview#company-owned-devices-for-knowledge-workers). ### fully managed device with a work profile A [fully managed device](https://developers.google.com/android/work/terminology#fully_managed_device) that is also provisioned with a [work profile](https://developers.google.com/android/work/terminology#work_profile), intended for company-owned devices that are used for both work and personal purposes. This management mode was deprecated in Android 11 and replaced with [work profile for mixed-use company-owned devices](https://developers.google.com/android/work/terminology#work_profile_for_mixed-use_company-owned_devices). ### Google Accounts enterprise *Compare to [managed Google Play Accounts enterprise](https://developers.google.com/android/work/terminology#managed_google_play_accounts_enterprise)* A type of enterprise binding that is linked to an existing managed Google domain. With this type of enterprise binding, end users access managed Google Play with their existing [managed Google Accounts](https://developers.google.com/android/work/terminology#managed_google_account). For more information, see [Organization onboarding](https://developers.google.com/android/work/overview#onboard_new_organizations). ### Google Admin console Google-provided console that an IT admin uses to generate an EMM token and to manage user accounts associated with the domain. ### Google Payments In Android, the system used to process payments for apps. IT admins use [Google Payments](https://support.google.com/payments/answer/6220307) to purchase apps in bulk, and users use Google Payments to purchase apps using in-app billing. ### Google Workspace account *Formerly known as **Google Apps account*** An account in a regular, organization-managed Google Workspace domain that is claimed and managed in the Google Admin console. ### identity provisioning The process of setting up users' managed accounts on devices and synchronizing user information across databases. ### mobile application management (MAM) A set of features for managing mobile apps in an enterprise environment. ### managed configurations Enables IT admins to remotely configure apps in situations where the app developer provides a managed configuration schema. ### managed Google Account A Google Account that's managed by a managed Google domain. ### managed Google domain A domain managed by an Android Enterprise solution. This is different from a Google Workspace domain, which is a regular, organization-managed Google domain that's claimed and managed in the Google Admin console. ### managed Google domain sign-up The initial process an organization goes through to claim a managed Google domain, which you then bind to your Android Enterprise solution. For details, see [Managed Google domain sign-up](https://developers.google.com/android/work/play/emm-api/create-enterprise#managed_google_domain_sign-up). ### managed Google Play *Formerly known as **Google Play for Work*** Content marketplace for Android apps. Admins use managed Google Play to manage apps. For more about managed Google Play, see the [managed Google Play Help Center](https://support.google.com/googleplay/work/#topic=6137710). ### managed Google Play Account *Formerly known as **Android for Work Account*** An account that gives a user access to managed Google Play and apps approved for them by their IT admin. ### managed Google Play Accounts enterprise *Compare to [Google Accounts enterprise](https://developers.google.com/android/work/terminology#google_accounts_enterprise)* A type of enterprise binding that isn't linked to an existing managed Google domain. With this type of enterprise binding, end users access managed Google Play with managed Google Play Accounts, which are provisioned for them by their organization's EMM provider. For more information, see [Organization onboarding](https://developers.google.com/android/work/overview#onboard_new_organizations). ### managed profile See *[work profile](https://developers.google.com/android/work/terminology#work_profile)* The term *managed profile* is used only in Android Open Source Project documentation and code, where it refers to the generic functionality of a managed corporate profile associated with the primary user account on an Android device. ### mobile device management (MDM) A set of features for managing device policies within an organization. ### OAuth 2.0 Open standard for authorization. You can use OAuth 2.0 with a [service account](https://developers.google.com/identity/protocols/OAuth2ServiceAccount) to call Google APIs on behalf of an application instead of using credentials that belong to an end user. ### personal profile On devices with a work profile, the area of the device outside the work profile. ### personal space Deprecated. See *[personal profile](https://developers.google.com/android/work/terminology#personal_profile)*. ### private app App visible only to selected users of a managed Google domain. For details, see [Public, private, and self-hosted apps](https://developers.google.com/android/work/distribute#public_private_and_self-hosted_apps). ### product In the context of the Google Play EMM API, usually refers to a supported app in the Google Play store or managed Google Play store. ### profile owner (PO) *Compare to [device owner](https://developers.google.com/android/work/terminology#device_owner_do)* For devices with work profiles, the DPC installed in the work profile is referred to as the profile owner. ### secondary user On some Android devices, you can set up a secondary user account that has its own profiles. Adding a secondary user is not the same as adding another profile to a device's primary user. ### Security Assertion Markup Language (SAML) An identity-management protocol used in some [identity provisioning scenarios](https://developers.google.com/android/work/play/emm-api/user-accounts#scenario-1). ### solution set A set of management features organized by use case. For more information, see [release a solution](https://developers.google.com/android/work/release-solution#2_develop_your_solution). ### work-managed device Deprecated. See [*fully managed device*](https://developers.google.com/android/work/terminology#fully_managed_device). ### work profile A self-contained profile on an Android device that isolates work apps and data from personal apps and data. For more details about work profiles, see [What is a work profile?](https://support.google.com/work/android/answer/6191949) in the Help Center. ### work profile for mixed-use company-owned devices A work profile that also allows the organization to set device-wide policies and restrictions that apply to the device's personal profile. As with a work profile for BYOD devices, the organization has no visibility into the personal profile, protecting end-user privacy. ### zero-touch enrollment A method of assigning provisioning details for fully managed and dedicated devices. For more information, see [Android zero-touch enrollment](https://developers.google.com/zero-touch/guides/overview).