> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/advanced-enterprise-services/device-management/managing-zoom-clients-and-devices-explainer/use-cases.md).

# Use Cases

Zoom Device Management (ZDM) for Clients addresses critical IT management needs across diverse organizational scenarios. Whether you're orchestrating controlled update rollouts across thousands of endpoints, enforcing enterprise compliance requirements in regulated industries, or providing consistent user experiences regardless of who signs in to a device, ZDM provides the centralized control and flexibility modern IT teams require.

{% hint style="warning" %}
**Important**

ZDM for Clients is not a guarantee of compliance with any specific legal regulations, including HIPAA, GDPR, SOC 2, and so on.
{% endhint %}

Common use cases include:

* [Managing Zoom Workplace App Updates](#manage-zoom-workplace-app-updates)
* [Modifying Default Settings](#modify-default-settings-ex-screen-sharing-zoom-windows)
* [Enforcing Corporate Policies](#enforce-corporate-policies-ex-require-sso)

### Manage Zoom Workplace App Updates

#### <mark style="color:blue;">**Scenario**</mark>

Administrators need to ensure rapid deployment of new updates to early adopters, while having a controlled method to expand to the larger user base.

#### <mark style="color:blue;">**Objective**</mark>

Create multiple groups to define a scaled update rollout process.

#### <mark style="color:blue;">**Why this matters**</mark>

ZDM allows Admins to control the installed app version, removing user ability to choose the upgrade version. Phased updates enable administrators to deploy new software systematically, allowing them to test features and integrations in a controlled environment before rolling out changes to the broader user base.

#### <mark style="color:blue;">**Steps**</mark>

Follow the steps below to define the update cadence for the group(s) in your account. By defining these settings, users in the group will update to the specific version of the Zoom Workplace app you define. While their app will check periodically for available admin-defined updates, they are also given the option to manually check if their admin has allowed a new version and to upgrade to it immediately. Their app will also automatically update and restart when idle.

{% hint style="warning" %}
**Important**

Each defined group can have a different version selected, allowing for scaled and controlled deployment of Zoom Workplace application updates.
{% endhint %}

{% stepper %}
{% step %}
Sign in to the [Zoom web portal](https://www.zoom.com/).
{% endstep %}

{% step %}
In the left navigation, scroll to the **Admin** section and click **Device Management**, **Device List**.
{% endstep %}

{% step %}
Click the **Groups** tab. If you haven't already created a group, click **+ Add Group** to add your desired groups within ZDM.\
\
Some common groups include Early Testers, IT Users, General Users, Regulated Users, and Executives.
{% endstep %}

{% step %}
Click on the appropriate group to edit the ZDM settings.
{% endstep %}

{% step %}
Click the **Zoom Clients** tab. In the **Updates** section, review the following fields:

* **Manage Update Channels:** By default, both Slow and Fast are enabled. To change this, click Edit.
  * **Slow** means less frequent changes and a more mature feature set.
  * **Fast** allows users to try the newest features and updates sooner.
* **Manage Zoom desktop client version:** Select **Deploy a specific version** and choose the appropriate version per OS.
* **When to download update:** Select **Any time**, then select **Automatically restart the Zoom client and install updates when inactive**.
* **Allow users to configure auto-update for Zoom desktop client:** Make sure this field is **disabled**.
* **Allow users to manually check for updates:** Make sure the field is **enabled**, then select **Update to Auto Update defined version** and click **Save**.
  {% endstep %}

{% step %}
Repeat this process as necessary, in order to define each group of users to be managed.
{% endstep %}
{% endstepper %}

### Modify Default Settings (ex: Screen Sharing Zoom Windows)

#### <mark style="color:blue;">**Scenario**</mark>

Administrators want to standardize all users' Zoom Workplace apps to show their Zoom windows when desktop screen sharing. By default, the workplace app will not show Zoom windows unless a local app setting is adjusted by the end user.

See the [Showing Zoom windows during screen share](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0059848) article for more information.

#### <mark style="color:blue;">**Objective**</mark>

Adjust the ZDM parameter for all device groups to show Zoom windows during screen sharing.

#### <mark style="color:blue;">**Why this matters**</mark>

This is a common configuration for application behavior and reduces the number of internal help tickets and saves end-user time.

#### <mark style="color:blue;">**Steps**</mark>

{% stepper %}
{% step %}
Sign in to the [Zoom web portal](https://www.zoom.com/).
{% endstep %}

{% step %}
In the left navigation, scroll to the **Admin** section and click **Device Management**, **Device List**.
{% endstep %}

{% step %}
Click the **Groups** tab. If you haven't already created a group, click **+ Add Group** to add your desired groups within ZDM.
{% endstep %}

{% step %}
Click on the appropriate group(s) to edit the ZDM settings.
{% endstep %}

{% step %}
Click the **Zoom Clients** tab. In the **Updates** section, review the **Show Zoom Win When Sharing** field. By default, this switch is disabled and unlocked.\
\
To change this, click on the switch. If a popup appears, click **Enable**. To prevent users from changing this setting in the client, click the lock icon next to the switch. If a popup box appears, click the **Lock** button to confirm.
{% endstep %}
{% endstepper %}

### Enforce Corporate Policies (ex: Require SSO)

#### <mark style="color:blue;">**Scenario**</mark>

An organization needs to ensure all managed Zoom Workplace desktop apps comply with corporate identity and security requirements. Administrators want to prevent unmanaged sign-in methods, direct users to the organization's Single Sign-On (SSO) endpoint, and enforce consistent authentication behavior across all managed devices, regardless of which user signs in.

#### <mark style="color:blue;">**Objective**</mark>

Standardize authentication across the organization by enforcing SSO, preconfiguring the organization's SSO login URL, requiring users to authenticate before using the Zoom Workplace app, and configuring all managed devices to follow the organization's security policies.

#### <mark style="color:blue;">**Why this matters**</mark>

ZDM enables device-based policy management, so these controls remain in effect on every enrolled app. Enforcing SSO strengthens an organization's security posture by centralizing authentication through the corporate identity provider, reducing reliance on local credentials, improving compliance with corporate access policies, simplifying the user sign-in experience through preconfigured settings, and ensuring consistent login behavior across all managed endpoints. Because ZDM applies policies at the device level, the configured controls remain consistent regardless of the user who signs in.

#### <mark style="color:blue;">**Steps**</mark>

{% stepper %}
{% step %}
Sign in to the [Zoom web portal](https://www.zoom.com/).
{% endstep %}

{% step %}
In the left navigation, scroll to the **Admin** section and click **Device Management**, **Device List**.
{% endstep %}

{% step %}
Click the **Groups** tab. If you haven't already created a group, click **+ Add Group** to add your desired groups within ZDM.
{% endstep %}

{% step %}
Click on the appropriate group(s) to edit the ZDM settings.
{% endstep %}

{% step %}
Click the **Zoom Clients** tab. In the **General** section, review the following fields.

{% hint style="info" %}
**Note**

To prevent users from changing this setting in the app, click the lock icon next to the switch. If a dialog box appears, click the **Lock** button to confirm.
{% endhint %}

| Field Name                   | Default Setting                                                      | How to Turn On the Field                                                   |
| ---------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Disable Facebook Login       | Enabled and not configured; meaning that this feature is not active. | Click on the switch and click the Enable button.                           |
| Disable Google Login         | Enabled and not configured; meaning that this feature is not active. | Click on the switch and click the Enable button.                           |
| Disable Login With Email     | Enabled and not configured; meaning that this feature is not active. | Click on the switch and click the Enable button.                           |
| Force Login With SSO         | Disabled and not configured; meaning this feature is not active.     | Click on the switch and click the Enable button.                           |
| Set SSO URL                  | This field is blank by default.                                      | Click on the pencil, type the URL you are setting for SSO, and click Save. |
| Enable Embed Browser For SSO | Enabled and not configured; meaning that this feature is not active. | Click on the switch and click the Enable button.                           |
| {% endstep %}                |                                                                      |                                                                            |
| {% endstepper %}             |                                                                      |                                                                            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/advanced-enterprise-services/device-management/managing-zoom-clients-and-devices-explainer/use-cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.