Unified Policies in TeamViewer ONE bring TeamViewer and Patch Management settings together into a single policy that is assigned to Device Groups and automatically applied to all devices within the group. More information on Unified Policies can be found here:
For existing customers, moving to this model is a guided migration rather than a fresh setup. This guide walks through the steps to begin using the new Unified Policy feature in TeamViewer ONE.
This article applies to customers with an existing TeamViewer ONE Standard or Advanced license.
What changes with Unified Policies
With legacy policies, settings can be managed separately and assigned at the device level. With Unified Policies, administration becomes simpler:
- One policy can contain both TeamViewer and Patch Management settings.
- Policies are assigned to device groups, not managed one device at a time.
- Devices are expected to inherit policy from their group.
- Existing legacy settings are imported into the new unified policy flow rather than recreated from scratch.
The table below explains more benefits of Unified Policies:
After migration, policy management is easier to maintain at scale because you manage policy assignment through groups instead of handling many individual device assignments.
Requirements
In order to utilize the Unified Policies feature in TeamViewer ONE, please ensure the following:
- At least one device group is ready for assignment.
- The Manage Policies permission is enabled for your account (Company Admin or custom roles with the Manage Policy permission enabled).
- The Policy assignment (administration) permission is activated on the target group.
- The devices within the group are set to inherit policies from the group level. This is done via rollout setup or device-level inheritance settings.
- Alternatively, devices that are updated to version 15.80 of TeamViewer Remote automatically are set to inherit from the group level upon successful installation of the update.
How migration works
Migrating to the new Unified Policies in TeamViewer ONE is designed to be guided and predictable. Instead of automatically changing all policies in the background, the migration flow lets admins review and consolidate their existing setup.
- Select the legacy policies to migrate. You choose which existing policies to bring into the unified model.
- Create a Unified Policy. The selected legacy policy settings are imported into one new unified policy.
- Review the imported settings. Confirm the TeamViewer and, if available, the Patching settings before continuing.
- Assign the Unified Policy to device groups. Choose the group or groups that should receive the policy.
- Devices inherit the policy from their group. Devices in those groups apply the policy through group inheritance.
It is recommended to review your group structure before migrating. A clean group structure makes assignment simpler and helps avoid conflicts later.
How to migrate legacy policies to Unified Policies
Below are the step-by-step instructions for migrating your legacy policies to the new Unified Policies in TeamViewer ONE.
1. Open Policies in the web app
Navigate to Admin → Devices → Policies to view your current policies.
2. Start the migration flow
Next, choose the option to migrate or convert your legacy policies to a Unified Policy when it is presented.
3. Select the legacy policy to migrate
Choose the policy you wish to migrate to the new Unified Policies. Any additional policies you wish to add can be done after the migration.
4. Name the new Unified Policy
Create a name for the new Unified Policy, using a descriptive and identifiable name, so that admins can easily recognize its purpose.
5. Review imported settings
While the merged policies will retain their information after migration to the new Unified Policy, it is recommended to double-check the policy settings to ensure everything remains as it was.
6 Assign the policy to device groups
Select one or more groups that should receive the new Unified Policy.
Note: Also ensure that all devices within these groups are set to inherit the policy from the group.
7. Save and apply
Once done, save the policy to complete the flow. This will create the Unified Policy and apply it to the selected groups
What to expect after migration
Migration to Unified Policies is intended to preserve your settings while moving administration to a group-based model. After migration:
- Your unified policy becomes the primary policy object managed in TeamViewer ONE.
- Devices in assigned groups will receive the primary policy via group inheritance.
- Older clients may continue to rely on legacy policy handling until they reconnect or update.
- Some environments may transition gradually as devices come back online and sync.
Post-migration checklist
Utilize the information below to confirm a successful migration:
- Confirm the Unified Policy appears in the Policies list.
- Confirm the intended device groups are assigned to the Unified Policy.
- Confirm that devices in those groups are configured to inherit from the group.
- Verify that a sample device has applied the expected settings.
- Check whether any devices are offline and have not yet synced.
Troubleshooting
A device did not apply the Unified Policy
-
Verify the device belongs to a group with the Unified Policy assigned.
-
Confirm the device is set to inherit from its group.
-
Check that the device is online and allow time for the next sync.
I do not see Unified Policies or the migration option
-
Confirm your license is TeamViewer ONE Standard or Advanced.
-
Ask your admin to verify your role includes Manage Policies.
-
If you are an existing customer using older policy types, the unified experience may require the migration flow instead of the standard create flow.
Assignment fails, or I cannot assign the policy
-
Verify you have Policy administration (assignment) permission on the target device group.
-
Check that the target group is the correct group for the devices you want to manage.
Devices are in the wrong policy context after migration
-
Review your group structure and move devices into the intended policy group if needed.
-
Check whether the device has fully transitioned to group inheritance.