重要提示:我们不再接受 Play EMM API 的新注册。
了解详情。
管理类型
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Google Play EMM API 包含 Devices
资源,该资源表示由 EMM 管理并与特定用户关联的每个实体。在您的客户现场,设备通过您的 EMM 控制台和设备政策控制器 (DPC) 进行管理。组织通过 Google Play 企业版向用户提供应用。
设备和管理类型
如果您的 DPC 管理整个设备,则该设备的 managementType
值为 managedDevice
。如果您的 DPC 仅管理工作资料,则设备的 managementType
为 managedProfile
,它仅表示实体设备上的受管理资料。这些设备称为“受管设备”。
管理类型为“unmanagedProfile
”的设备称为“不受管理的设备”,包括:
- 搭载 Android 5.0 之前的 Android 版本或不支持工作资料的旧版设备。
- 不受 DPC 控制且管理类型为“
managedDevice
”或“managedProfile
”的设备。例如,组织的 G Suite 管理员可以允许用户在未设置工作资料的情况下,将公司电子邮件帐号添加到他们的个人 Android 设备上。
使用非受管个人资料管理类型可以执行的操作
使用“unmanagedProfile
”管理类型时,旧版设备的用户可以通过其组织的 Google Play 企业版商店获取应用,并且:
- 使用按用户和按应用 ACL 访问为他们提供的专用应用。
- 从客户公司购买的批量许可应用中提取许可。
- 访问 Google Play 企业版,即可安装管理员推荐和精选的应用。
此外,管理员还可以查看设备上安装了哪些工作应用。
您可以在搭载 Android 5.0 之前版本的设备或不支持工作资料的设备上使用“unmanagedProfile
”管理类型。如果设备支持工作资料,请使用 managedDevice
或 managedProfile
管理类型。
用户意见征求和 Google Play 企业版
用户首次尝试访问 Google Play 企业版时,必须同意服务条款 (ToS)。在用户同意服务条款后:
- 系统会为用户拥有的每台非受管设备在 Google Play 企业版中创建一条“
unmanagedProfile
”记录。
- 您可以通过 Google Play EMM API 查看设备。
- 用户安装应用的方式与设备由您的 DPC 直接管理的用户相同。
资源、方法和管理类型摘要
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):2025-08-31。"],[[["\u003cp\u003eThe Google Play EMM API allows organizations to manage devices and distribute apps through managed Google Play, supporting different management types for varying levels of control.\u003c/p\u003e\n"],["\u003cp\u003eDevices can be managed as \u003ccode\u003emanagedDevice\u003c/code\u003e (entire device), \u003ccode\u003emanagedProfile\u003c/code\u003e (work profile only), or \u003ccode\u003eunmanagedProfile\u003c/code\u003e (legacy devices or personal devices with corporate accounts).\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eunmanagedProfile\u003c/code\u003e type enables users on legacy or personal devices to access managed Google Play, install apps, and draw down licenses, while admins can see installed work apps.\u003c/p\u003e\n"],["\u003cp\u003eUser consent to Google Play Terms of Service is required for accessing managed Google Play, resulting in the creation of an \u003ccode\u003eunmanagedProfile\u003c/code\u003e record for unmanaged devices.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Play EMM API provides various resources and methods for managing devices, entitlements, and app installations, with varying levels of support for different management types.\u003c/p\u003e\n"]]],[],null,["# Management types\n\nThe Google Play EMM API includes a `Devices` resource that represents each entity that's managed by an EMM and associated with a specific user. At your customer sites, devices are managed using your EMM console and your\ndevice policy controller (DPC). Organizations provide apps to users through\nmanaged Google Play.\n\nDevices and management types\n----------------------------\n\nIf your DPC manages an entire device, the device has a `managementType` value of `managedDevice`. If your DPC manages only the work profile, the device has a `managementType` of `managedProfile` , which represents only the managed profile on the physical device. These devices are called \"managed devices.\"\n\nDevices with an `unmanagedProfile` management type are called \"unmanaged devices,\" including:\n\n- Legacy devices that run Android versions earlier than 5.0 or don't support work profiles.\n- Devices that aren't controlled by a DPC and don't have `managedDevice` or `managedProfile` as their management type. For example, a G Suite administrator at an organization could allow users to add their corporate email accounts to their personal Android devices without setting up a work profile.\n\nWhat you can do with the unmanagedProfile management type\n---------------------------------------------------------\n\nUsing the `unmanagedProfile` management type, users of legacy devices can get apps through their organizations' managed Google Play store, and:\n\n- Access private apps that are made available to them using per-user and per-app ACLs.\n- Draw down licences from bulk-licensed applications purchased by their business.\n- Access managed Google Play to install apps recommended and curated by an administrator.\n\nIn addition, administrators can see which work apps are installed on the device.\n\nYou can use the `unmanagedProfile` management type on devices that run Android versions earlier than 5.0 or devices that don't support work profiles. If a device supports work profiles, use the `managedDevice` or `managedProfile` management types.\n\n### User consent and managed Google Play\n\nA user has to agree to the Terms of Service (ToS) presented when they attempt to access managed Google Play for the first time. After a user agrees to the ToS:\n\n- An `unmanagedProfile` record is created in managed Google Play for each unmanaged device a user has.\n- You can see the devices on the Google Play EMM API.\n- The user can install apps in the same way as users whose devices are managed directly by your DPC.\n\nSummary of resources, methods, and management types\n---------------------------------------------------\n\n|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------|---------------------------------------------------|\n| **Resource\\ and\\ method** | **Description** | **`managed` `Device`** | **`managed` Profile** | **`unmanaged` `Profile`** |\n| [Devices.get](/android/work/play/emm-api/v1/devices/get) | Returns a `Devices` resource that contains details about the device. | ✔ | ✔ | ✔ |\n| [Devices.getState](/android/work/play/emm-api/v1/devices/getState) | Retrieves whether a device's access to Google services is enabled or disabled. | ✔ (Google- managed users only) | ✔ (Google- managed users only) | |\n| [Devices.list](/android/work/play/emm-api/v1/devices/list) | Retrieves a list of `Device` resources for the specified `userID`. | ✔ | ✔ | ✔ |\n| [Devices.setState](/android/work/play/emm-api/v1/devices/setState) | Sets whether a device's access to Google services is enabled or disabled. Requires setting up mobile device management for Android devices in the Google Admin console. | ✔ (Google- managed users only) | ✔ (Google- managed users only) | |\n| [Entitlements.delete](/android/work/play/emm-api/v1/entitlements/delete) | Removes the entitlement and the app from the device. | ✔ | ✔ | ✔ (the app isn't removed from the device) |\n| [Entitlements.update](/android/work/play/emm-api/v1/entitlements/update) | When invoked with the optional install parameter, attempts to install the app on the device along with assigning the entitlement to the user. | ✔ | ✔ | ✔ |\n| [Installs.get](/android/work/play/emm-api/v1/installs/get) | Retrieves the details of an app installation on a device. | ✔ | ✔ | ✔ (limited to apps installed by the work account) |\n| [Installs.list](/android/work/play/emm-api/v1/installs/list) | Retrieves the details of all apps installed on a device. | ✔ | ✔ | ✔ (limited to apps installed by the work account) |\n| [Installs.delete](/android/work/play/emm-api/v1/installs/delete) | Requests to remove an app from a device. | ✔ | ✔ | ✔ |\n| [Installs.update](/android/work/play/emm-api/v1/installs/update) | Requests to install the latest app version on a device. | ✔ | ✔ | ✔ |"]]