Only our support team can connect
Allowlist the accounts of your helpdesk staff.
{
"whitelistAccounts": "u1234567;u7654321"
}Android app directory · Remote support
These are the managed configuration keys TeamViewer documents for QuickSupport on Android Enterprise. They let IT set allowlists of TeamViewer accounts or companies, route connections through dedicated routers and add devices to a group in the Management Console. TeamViewer ties this feature to specific licenses, so check your plan first. Some keys in its table apply to other TeamViewer apps and are left out here.
com.teamviewer.quicksupport.market Common setups
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
Allowlist the accounts of your helpdesk staff.
{
"whitelistAccounts": "u1234567;u7654321"
}Each tablet appears in the chosen group under a name you pick, ready for technicians to find.
{
"partnerListApiToken": "1234567-AbCdEf",
"partnerListGroupId": "g12345678",
"partnerListDeviceName": "Kiosk 12"
}Apply a Management Console configuration and send traffic through dedicated routers.
{
"ConfigurationID": "abc12345",
"conditionalAccessServers": "router1.example.com;router2.example.com"
}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 |
|---|---|---|---|
| Who can connect | |||
whitelistAccounts | Account IDs separated by semicolons | An allowlist of TeamViewer account IDs, separated by semicolons. Ask TeamViewer support if you do not know the IDs. | u1234567;u7654321 |
whitelistCompanies | Company IDs separated by semicolons | An allowlist of TeamViewer company IDs, separated by semicolons, which suits an outsourced support team. | c1234567 |
conditionalAccessServers | Router addresses separated by semicolons | Connects the app to one of the dedicated routers you list, separated by semicolons, if your company runs its own TeamViewer routers. | router1.example.com;router2.example.com |
| Device setup | |||
ConfigurationID | Management Console configuration ID | Applies a configuration you built in the Management Console, including custom module parameters, to QuickSupport on the device. | abc12345 |
partnerListApiToken | API token | The token that lets the device add itself to a group in your account. It only works together with partnerListGroupId. | 1234567-AbCdEf |
partnerListGroupId | Group ID | The group in your device list where new devices are placed. Needs the API token as well. | g12345678 |
partnerListDeviceName | Device name | Replaces the default name made of brand, model and serial number, so devices are easier to find in the list. | Kiosk 12 |
keepAliveServerName | Router address | An older way to connect to a dedicated router. TeamViewer marks it as deprecated, so use conditionalAccessServers instead. | 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 QuickSupport and its configuration on their next sync.
Questions
com.teamviewer.quicksupport.market. Use it to find the app when you add it to a policy.
TeamViewer says managed configuration is for Corporate or Tensor customers. Check your plan with TeamViewer before planning a rollout.
Host is meant for unattended access and only accepts connections from the account the device is assigned to. QuickSupport is the app TeamViewer points to for connections by TeamViewer ID or service case. Host has its own listing in this directory.
whitelistAccounts takes TeamViewer account IDs and whitelistCompanies takes company IDs, each separated by semicolons. TeamViewer describes both as allowlists.
Add the app to a Nomid policy, set its configuration and choose its permissions.