Cisco Umbrella's roaming client has a feature that allows customers to put roaming client devices on the 'stage' track-- otherwise known as a 'beta' or 'pre-release' track --in advance of mainline releases.
Where possible, we encourage customers to have two orgs, one for standard production and one for acceptance testing and beta testing new features.
The 'stage control' enables customers to have two 'tracks' for a subset of machines to encourage quicker adoption of the new releases after passing your internal QA/acceptance testing.
Method/What to do
The official method to do internal testing of client updates is to have certain devices on our staging track. You can do this for some devices in your org, or create a separate org for testing.
First, and most importantly, you should subscribe to updates on our release notes page. We post all roaming client release notes there, as soon as they hit the ‘stage’ track. This lets you know when a new version is available for testing to machines on the stage track.
If you observe any incompatibility issues or regressions while the build is in staging, we will prioritize investigating it and will usually halt the release process until such time that the issue can be addressed.
To learn more about early updates and automated beta testing, see this article.
For exact instructions, any questions or more information, please contact support at email@example.com