Important Note: The following option discussed in this FAQ is not recommended in cases where you have multiple sub OUs at a single location. The OU setup in this section write your Chrome devices at a location back to the specific OU specified in your location fields. As long as all of your devices are stored in a single OU path for each location, then this option is viable for your district.
When enabled, the OU write back option in the Google Devices app allows you to change the OU of a device in Google based on the location of the device in Incident IQ by writing back data during system syncs.
At the bottom of the page you will see the write-back options section. You will want to enable the Write orgUnitPath to Google option.
Once enabled, you can setup a single OU path to writeback per location. As shown in the image below, you will need to structure the OUs in a /[Path] manner.
Now that your OU mappings are setup, you may have some devices in your fleet that would like to exclude from this write-back functionality. In such cases, you can apply filters to prevent these devices from writing back OU data to Google by clicking on the following highlighted option underneath the write-back checkbox.
Once filters are enabled, you will need to click on the Add Filter button.
At this point, you can select the filters needed to include or exclude the desired devices during write-back syncs. In the example below, all devices that are in the /Kiosks OU will be excluded from the OU write-back, allowing all other devices to update their OU as needed.