Enroll and lock the assignment
Assign each device as a managed device and disallow manual removal of the assignment on the device.
{
"AssignmentID": "0123456789ab",
"allowAssignmentRemoval": false
}Android app directory · Remote support
These are the managed configuration keys TeamViewer documents for the Host app on Android Enterprise. Host stays assigned to an account, so IT can use the keys to link a device to the right Management Console configuration, restrict allowed accounts and disallow manual removal of the assignment. TeamViewer ties this feature to specific licenses, so confirm your plan before you start.
com.teamviewer.host.market Common setups
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
Assign each device as a managed device and disallow manual removal of the assignment on the device.
{
"AssignmentID": "0123456789ab",
"allowAssignmentRemoval": false
}Use a configuration from the Management Console and give every device a recognizable name.
{
"ConfigurationID": "abc12345",
"partnerListDeviceName": "Delivery van 7"
}Allowlist the support accounts and the company you list.
{
"whitelistAccounts": "u1234567;u7654321",
"whitelistCompanies": "c1234567"
}Managed configuration
Key names and value types come from the vendor’s documentation. The explanations are written by Nomid.
| Key | Type | What it does | Example |
|---|---|---|---|
| Assignment to your account | |||
ConfigurationID | Management Console configuration ID | After Host starts, the device is assigned to the TeamViewer account that this configuration belongs to. | abc12345 |
AssignmentID | Assignment ID | Assigns the device as a managed device once Host starts. | 0123456789ab |
allowAssignmentRemoval | On or off | Controls whether the assignment can be removed manually on the device. TeamViewer's default is true; set it to false to disallow manual removal. | false |
partnerListDeviceName | Device name | Replaces the default name made of brand, model and serial number with one you choose. | Delivery van 7 |
| Access limits | |||
whitelistAccounts | Account IDs separated by semicolons | An allowlist of TeamViewer account IDs, separated by semicolons. | u1234567;u7654321 |
whitelistCompanies | Company IDs separated by semicolons | An allowlist of TeamViewer company IDs, separated by semicolons. | c1234567 |
conditionalAccessServers | Router addresses separated by semicolons | Connects the app to one of the dedicated routers you list, separated by semicolons, for companies that run their own. | router1.example.com;router2.example.com |
keepAliveServerName | Router address | An older way to name a dedicated router. TeamViewer marks it deprecated in favor of conditionalAccessServers. | router1.example.com |
Deploy with Nomid
Find it on Google Play from the policy’s apps list and choose how it is installed.
In the policy, set the app’s managed configuration with the keys and values from this page.
Devices in the policy receive TeamViewer Host and its configuration on their next sync.
Questions
com.teamviewer.host.market. Use it to find the app when you add it to a policy, and to tell it apart from QuickSupport, which has its own package and its own keys.
No. TeamViewer says Host only accepts connections from the account the device is assigned to. QuickSupport is the app for ID-based sessions.
It controls whether the assignment can be removed manually on the device. Its documented default is true, so set it to false on fleet devices if people should not be able to unlink them from your account.
TeamViewer ties managed configuration to Corporate or Tensor customers. Confirm this with your TeamViewer contact.
Add the app to a Nomid policy, set its configuration and choose its permissions.