> 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/zoom-workplace/zoom-whiteboard/zoom-whiteboard-security-compliance.md).

# Security and Compliance

Explore the security, governance, and compliance controls available for Zoom Whiteboard.

Zoom Whiteboard provides administrative controls for protecting content and managing collaboration. This page covers encryption, access restrictions, data residency, governance, and Customer Managed Key support.

### Administrative Controls

#### <mark style="color:blue;">Manage Zoom Whiteboard data, access controls, and deployment with enterprise-level administration capabilities</mark>

Zoom Whiteboard uses multi-layered security on Zoom-Managed Services. This protects whiteboard content across platforms. The system uses distributed data centers with region-specific storage. It includes SSO integration and domain-based access controls.

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

Your organization may prefer or require SSO authentication based on your security policies. You can set data residency options to match these requirements. Customer Managed Key support adds optional protection and is described in the following section.
{% endhint %}

Account-specific settings implement administrative controls, enabling administrators to manage whiteboard creation, editing permissions, and sharing capabilities across their organization. This enables proper governance while maintaining flexibility for collaborative work.

Account owners and admins can also restrict access to cloud-saved whiteboards by IP address range, at the account or group level, with the option to lock the setting. Outside of Zoom Meetings, only users with a valid IP address can open a cloud-saved whiteboard — this doesn't restrict sharing whiteboards or generating share links. In Zoom Meetings, admins can enable an additional restriction limiting invalid-IP users to view-only access, blocking them from copying, exporting, or sharing whiteboards. When that additional restriction is off, invalid-IP users can still collaborate on whiteboards shared to them in a meeting, but can't open existing account-managed whiteboards outside of it. This setting is off and unlocked by default.

Administrators get extensive control through meeting settings. They can set content retention policies and automated whiteboard lifecycle protocols. Admins can also restrict cross-organizational collaboration.

For Zoom AI features, administrators can use the following designated controls to meter the level of AI usage and access:

* Organization-level configuration options
* Granular access controls for AI features
* Domain-based restrictions
* Custom usage policies per user group

### Encryption

#### <mark style="color:blue;">Zoom encrypts whiteboard data in transit over the public internet and at rest within its product infrastructure</mark>

Zoom’s security architecture implements robust encryption and access controls across its platform. Zoom secures data connections over the public internet on the Zoom Workplace desktop and mobile apps using TLS 1.2 security protocols, and industry-standard encryption protects in-meeting traffic.

Within Zoom’s product environment, user meeting content is encrypted at rest, with access controls managed by account owners, administrators, and designated privileged users.

### Customer Managed Key <a href="#id-3ijhgpswoeni" id="id-3ijhgpswoeni"></a>

#### <mark style="color:blue;">Customer Managed Key offers enhanced enterprise-grade security</mark> <a href="#id-3ijhgpswoeni" id="id-3ijhgpswoeni"></a>

Zoom Customer Managed Key (CMK) provides enhanced security capabilities for enterprise customers requiring stricter compliance and regulatory controls. This system allows you to maintain your own encryption keys through AWS to encrypt and decrypt your data and assets. This implementation works through Zoom's Whiteboard server (DAS), which interfaces with the CMK system to handle data encryption and storage operations.

When saving data, the DAS retrieves the document owner’s encryption key from CMK, encrypts the target data, and stores it in the destination storage. During data retrieval operations, the DAS gets the decryption key from CMK to decrypt the data as it is pulled from storage. This architecture allows you to maintain control over your encryption keys while enabling secure data handling within Zoom’s infrastructure.

### Governance

#### <mark style="color:blue;">Governance capabilities and data flow protections offer control, simplicity, and reassurance for Zoom Whiteboard content</mark> <a href="#c66zgw1fkr10" id="c66zgw1fkr10"></a>

Governance is another key feature of Zoom Whiteboard. Admins can enforce template-based publishing workflows and investigate comprehensive whiteboard metadata for root-cause analyses. Bulk operations also help content management activities.

Whiteboard data center regions set in the Zoom admin portal apply to Whiteboard content, as well.

Zoom Whiteboard's administrative framework provides comprehensive control and management capabilities for enterprise deployment. The system encompasses sophisticated meeting settings management coupled with configurable retention policies for automated whiteboard lifecycle management. Administrative controls extend to data residency options, which align with organizational Account Profile policies for content storage location management.

The platform offers extensive API integration capabilities, enabling custom solution development and integration with existing enterprise systems. Security features include customizable collaboration disclaimers and granular controls for cross-organizational collaboration restrictions.

### Project Privacy

#### <mark style="color:blue;">Whiteboard projects are private until shared</mark>

Enterprise management tools for IT admins allow them to manage and control access to Zoom Whiteboard, including default sharing permissions like the ability to share a whiteboard with anyone who has an active Zoom account.

Whiteboard owners and admins can control who has access to and can see their whiteboards. By default, the creator, listed as the owner, is the only person who can access new whiteboards created outside meetings; these whiteboards are private. Owners can then invite additional editors, commenters, or viewers, and create links to share with their organization.

They can also transfer ownership of a whiteboard between users directly within the Zoom Workplace app.

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

Account owners and whiteboard admins have the ability to add additional collaborators (including themselves) or change ownership of a Zoom Whiteboard.
{% endhint %}

For whiteboards generated through Zoom Webinars, access is tied to the associated Webinar license. If that license is paused, affected whiteboards become view-only for the document owner only; if it's cancelled, the whiteboards become fully inaccessible. In both cases a status indicator with a link to billing management appears on the board. Cancelled-license whiteboards are retained for a 30-day grace period — repurchasing the license within that window restores access — after which they're permanently and irreversibly deleted.

### Access Restriction

#### <mark style="color:blue;">Administrators can restrict Zoom Whiteboard access</mark>

Zoom administrators can selectively enable whiteboard access at the group and account levels, restricting feature access to approved users or groups.

Whiteboard admins can also:

* Enable or disable Zoom Whiteboard for in-meeting or out-of-meeting usage
* Enable or disable cloud storage for whiteboards
* Enable or disable the ability to export whiteboards
* Enable or disable the ability to share boards outside their organization


---

# 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/zoom-workplace/zoom-whiteboard/zoom-whiteboard-security-compliance.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.
