Zoom

What Zoom is and what Zoom Workplace means

Zoom is a proprietary communication and collaboration platform from Zoom Communications, Inc. Its best-known product, Meetings, connects people through audio, video and screen sharing. Zoom Workplace brings together a wider collaboration offering; the company cannot accurately be reduced to a single video-calling application.

The service combines installed clients and browser access with cloud infrastructure. Work may centre on a meeting, conversation channel, equipped physical room or customer-service interaction. Each has different participants, permissions and outputs. Choosing a format starts with what needs to happen: discussion, presentation, telephone support or producing a document after a session.

Reference documentation: Zoom — Company history · Zoom — Introducing Zoom Communications Inc. · Zoom — Workplace general availability.

History: from video meetings to a work platform

Eric Yuan founded the company in 2011 after working at Webex and Cisco. Following initial development, Zoom launched publicly in 2013. Its January announcement described meetings for up to 25 people and more than 400,000 participants over the first five months of early activity. That figure does not describe the first month after general launch.

• 2019: Zoom Phone expanded into business telephony; the company began trading on Nasdaq in April.
• 2020: pandemic growth made the service everyday infrastructure for organisations and households. It also required changes to security, privacy and default settings.
• 2021: Zoom Apps introduced applications inside the client, broadening activities during conversations.
• 2022: Whiteboard added persistent canvases; Contact Center expanded customer service, while Zoom One grouped products into commercial packages.
• 2023–2024: experiences arrived for Apple TV and Vision Pro. Zoom Workplace became generally available in April 2024; in November the company changed its name from Zoom Video Communications to Zoom Communications.

These changes explain why an older guide to “Zoom” may discuss only Meetings, show the Zoom One catalogue or use previous feature names. Historical dates explain the evolution, but licensing decisions require current product and edition information.

Reference documentation: Zoom — Company history · Zoom — January 2013 financing and product announcement · Zoom — Introducing Zoom Communications Inc. · Zoom — Workplace general availability · Zoom — Zoom One launch, corrected announcement · Zoom — Apps launch · Zoom — Apple Vision Pro · Zoom — Whiteboard launch.

Remote meetings with session controls

Zoom brings people together remotely to share information during a session. Hosts have controls over participants, audio and screen sharing. Distinguish the presenter, participation facilitator and access administrator before use: these may be different people who need a common plan.

Captions supporting understanding during a meeting and a transcript retained afterwards are different outputs. Zoom documentation explains that transcript retention depends on configuration. Do not assume a session automatically creates a complete record or that the record reproduces every intervention without error.

Reference documentation: Zoom Support — Managing participants in a meeting · Zoom Support — Frequently asked questions about meeting captions and transcript updates.

Platforms, licensing and session capacity

Zoom provides Windows, macOS and Linux clients, mobile applications and browser access. Chromebooks can use the web application. Minimum versions, peripherals and supported functions vary; access does not mean every interface has identical controls. Television and spatial-computing experiences do not automatically replace an administration workstation.

For a free account, the published reference is up to 100 participants and 40 minutes per meeting. Someone with Meetings Basic permissions inside a paid account still has Basic hosting limits unless assigned the appropriate licence. Higher capacity depends on plans and add-ons: no single maximum describes Meetings, Webinars and Events together.

Before a workshop, test the presenter’s device, an external connection and a participant using the least capable expected equipment. Include microphone, presentation, captions and reconnection. The useful result is an experience that works for actual attendees, rather than only for the licence purchaser.

Reference documentation: Zoom — Administrator FAQ · Zoom — Desktop system requirements · Zoom — Web App requirements · Zoom — Apple Vision Pro.

Meetings, webinars, breakout rooms and focus mode

Meetings encourages participation among attendees; Webinars separates hosts and panellists from the audience. Events and Webinars Plus add event and session organisation according to the offering. A large presentation and a six-person exercise require different participation, registration and moderation arrangements.

Breakout rooms divide a meeting into groups. Focus mode changes video visibility: the host retains a view that participants do not share with one another. It neither creates working groups nor verifies attention. Cloud recording of a meeting with breakout rooms captures the main room; computer recording depends on the room occupied by the recorder.

A useful safety discussion could introduce a scenario in the main room, allocate groups the same question and collect comparable conclusions. Each group returns observed facts, missing information and a proposed next step. If one group could not connect, record the missing evidence rather than interpreting silence as agreement.

Reference documentation: Zoom — Meetings and webinars · Zoom — Events and Webinars Plus types · Zoom — Focus mode · Zoom — Breakout-room administration.

Whiteboards, physical rooms, telephony and customer service

Whiteboard provides a persistent canvas that can be prepared and consulted outside the call. It helps organise ideas, diagrams and contributions, but a sticky note’s position does not by itself define priority, ownership or approval. Turning discussion into work requires identifiable decisions.

Zoom Rooms connects the experience to physical-room equipment. Cameras, microphones, displays and controls affect the result; features such as virtual-reception kiosks and participant framing depend on hardware and configuration. In a hybrid meeting, a distant camera can miss gestures, board text and side conversations even while the connection remains active.

Zoom Phone handles telephone numbers, extensions and call routing. Contact Center organises customer-service interactions across channels. These are different solutions from inviting someone to a meeting. An OSH manager may need a discussion across dispersed sites rather than a telephone system; adding products without that diagnosis increases administration without guaranteeing better coordination.

Reference documentation: Zoom — Phone administration · Zoom — Contact Center · Zoom — Whiteboard launch · Zoom — 2021 hybrid-room developments.

Integrations, applications and development

Zoom Apps brings applications into the Zoom experience; integrations can connect meetings with calendars, documents and processes. They do not all operate alike: one application may display a tool during a call while another receives information afterwards. Before installation, identify the provider, permissions, received content and output destination.

For developers, Meeting SDK embeds the Zoom meeting experience in another product. Video SDK supports a custom audiovisual experience and should not be confused with an ordinary Zoom meeting joined through its meeting identifier. The choice changes interfaces, sessions, development responsibilities and commercial arrangements.

In a safety process, a useful integration might associate a session with the reviewed procedure version and create outstanding tasks after validation. It should preserve identifiers and avoid duplication when processing the same event again. A transcript copied into two systems should not become two separate decisions or grant access to unauthorised people.

Reference documentation: Zoom — Apps launch · Zoom — Video SDK and Meeting SDK comparison.

Built-in AI, ZoomMate and checking results

In 2026 Zoom distinguishes built-in AI capabilities, such as meeting summaries and writing assistance, from ZoomMate, an add-on using context and connections to work across tools. ZoomMate launched on 1 June 2026 with initial North American availability and a gradual rollout. That announcement does not establish identical availability across countries, industries and accounts.

The evolution of AI Companion does not require purchasing ZoomMate to retain included capabilities in an eligible plan. Documentation separates these offerings. Zoom states that customer communications content is not used to train its own or third-party AI models; this does not mean the content is never processed to produce answers or that all retention disappears.

For OSH, a summary can suggest actions but must distinguish “will consider”, “approved” and “completed”. Before creating an external task, check its owner, deadline and decision source. Separately, the World ID Deep Face integration announced in April 2026 was presented as a verification beta, rather than a universal guarantee of identity or authenticity across all meetings.

Reference documentation: Zoom — ZoomMate launch · Zoom — From AI Companion to ZoomMate · Zoom — AI data handling · Zoom — Tools for Humanity integration.

Accessibility and languages: beyond switching on captions

Zoom supports keyboard navigation, screen readers, captions and options for keeping an interpreter visible. Automatic translation depends on languages, supported pairs and licensing. For example, the reviewed documentation lists translation from Catalan into English and Spanish; a language list does not imply every possible combination.

Accessibility also depends on the material. A photograph of an unreadable table remains unreadable when screen-shared, and an undescribed video can omit essential information. Provide an accessible document, describe what is being indicated and allow questions. In a safety explanation, a missed negative such as “do not remove” becoming “remove” requires explicit correction.

A multilingual session can use an agreed short glossary of equipment, actions and technical terms. Afterwards, compare a sample of generated text with the audio or approved source. The aim is for participants to understand the same instruction, rather than accumulate three divergent transcripts.

Reference documentation: Zoom — Translated captions · Zoom — Accessibility.

Access security, encryption and data location

A meeting link is a technical invitation, rather than sufficient authorisation for all its content. Waiting rooms, passcodes, authentication, screen-sharing controls and participant removal serve different purposes. For a restricted review, check who joins, presents and later receives files or recordings. A link published without context can expand the audience unexpectedly.

End-to-end encryption, E2EE, is a specific mode. Enabling it disables features including cloud recording, Whiteboard, AI and live transcription. A meeting cannot therefore promise both E2EE and every cloud-processing feature. The team must choose and test the combination that fits its purpose.

Paid accounts can select processing regions for certain content in meetings they host, subject to provisioning and transit restrictions. That choice does not establish that all data across every product stays in one country. Recordings, integrations and AI features require their own configuration review.

An operational test with an external guest should check three boundaries: meeting entry, shared-content access and subsequent access. Someone being allowed to attend does not imply they should retain an indefinite copy of a sensitive discussion.

Reference documentation: Zoom Support — Managing participants in a meeting · Zoom — End-to-end encryption · Zoom — Data-center selection.

Historical problems and security changes

Easy access to calls helped Zoom grow, but also exposed tensions between convenience and control. Historical incidents need dates: they do not prove that a fixed vulnerability remains present or that a correction removes every later risk.

• 2018: Tenable documented message spoofing and identified corrected versions.
• 2019: the Mac client’s local web server raised concerns about call and camera access; updates removed it.
• 2020: Windows UNC-link problems were fixed, and the iOS client removed a Facebook SDK collecting unnecessary device information. Sales Navigator and the attention indicator were also withdrawn.
• 2022: fixes addressed local privilege escalation in the macOS updater, illustrating that update mechanisms themselves need protection.

In April 2020, Citizen Lab identified cryptographic weaknesses and observed meeting keys distributed through Chinese servers in its tests. Zoom announced a 90-day security programme, introduced AES-256 GCM in Zoom 5.0 and acquired Keybase in May to develop E2EE. Improving transport encryption and keeping keys exclusively at endpoints are different technical decisions.

Zoombombing describes unwanted intrusions or disruption, often involving offensive content. It may involve circulated links and excessive presentation permissions rather than broken encryption. Moderation and access configuration remain relevant even when transport is protected.

Reference documentation: Zoom — Facebook SDK removal · Zoom — April 2020 security plan · Citizen Lab — April 2020 cryptography research · Zoom — Zoom 5.0 security release · Zoom — Keybase acquisition · ICANN — July 2019 Zoom vulnerabilities · Tenable — Zoom message spoofing, 2018 · Zoom — Security bulletins · NHS Digital — 2020 path injection alert.

Regulatory debates and their scope

In November 2020 the US FTC announced a settlement concerning allegations of deceptive or unfair security practices involving encryption and ZoomOpener. Final approval was voted in January 2021 and announced in February, including a security programme and independent assessments. This was a specific proceeding, rather than general certification of every subsequent use.

A 2021 warning in Hamburg concerned the city’s planned deployment and data transfers. In September 2023 the regulator reported that the dispute had ended by agreement following changes in the applicable framework. Describing it as a permanent Europe-wide Zoom ban would be incorrect.

An organisation’s practical question is which configuration, data, users and purpose are being assessed. A product profile can explain the history; a particular deployment needs its own conditions and evidence.

Reference documentation: Hamburg regulator — Dispute settled in 2023 · FTC — 2020 complaint and proposed settlement · FTC — Final approval of settlement.

Social adoption, culture and videoconference fatigue

During the pandemic, Zoom supported work, classes, social gatherings, cultural activities and remote services. The provider reported growth from about ten million daily meeting participations in December 2019 to 300 million in April 2020. These are participations: someone joining several meetings may be counted several times. They are not 300 million unique daily users.

Its presence extended into culture. Richard Nelson’s What Do We Need to Talk About?, premiered by The Public Theater in April 2020, used a Zoom conversation as a dramatic format. The example shows that the tool did more than replace meeting rooms: its interface became part of stories about life during lockdown.

“Zoom fatigue” describes tiredness associated with videoconferencing rather than exclusively one brand. A 2021 theoretical Stanford paper examined close-up gaze, self-view, reduced movement and non-verbal effort. It does not diagnose individuals or establish identical effects from every video call.

OSH considerations include each meeting’s purpose, duration, breaks, opportunities to change posture and when cameras provide useful information. An update requiring only reading a status may work asynchronously, while a complex disagreement may justify conversation. Understanding and coordination matter more than hours of video.

Reference documentation: Zoom — Reflecting on pandemic growth · Zoom — April 2020 security plan · Stanford — Videoconference fatigue research · New York Stage Review — Richard Nelson’s Zoom play.

Uses in preventive coordination and training

• Awareness sessions: explain reviewed materials and allow questions, checking that remote delivery suits the objective.
• Cross-site meetings: compare information and agree tasks without bringing every participant physically together.
• Visit preparation: clarify scope, documents and participants before an on-site activity.

These are Sabentis proposals. A video call does not replace workplace observation where that is needed, or independently demonstrate effective attendance, understanding or practical competence.

Worked example: a short session with comprehension checks

Hypothetical example. A team presents an internal procedure to managers at several sites. The session should resolve questions and identify the applicable material.

1. Define the objective and provide the authorised reference with version and date. Prepare comprehension questions, not just a slide presentation.
2. Test audio, screen sharing and readability from a participant’s device. Agree an alternative for anyone unable to connect or follow the content.
3. Configure access, hosting and screen permissions. If recording or transcript retention is planned, decide its purpose, access and authorised handling beforehand.
4. During the session, distinguish confirmed answers from questions needing review. Do not improvise technical instructions beyond the approved material.
5. Afterwards, check questions and answers before distributing a summary. Identify actions, owners and final materials without presenting a recording as automatic proof of learning.

Acceptance means participants can locate the reference and explain its key points. Where the objective includes a practical skill, define an additional assessment appropriate to that skill. Record unresolved questions clearly so uncertainty is not lost when the meeting ends.

Checking the case: a hypothetical session has 24 participants. Twenty submit the exercise and four do not. Of the 20 responses, 15 apply the criterion correctly and five need clarification: 75% refers to respondents, not all 24 connected people. Attendance does not supply the missing evidence. The team records the procedure version, question, reviewed response and outstanding issues, then uses an appropriate task to check application. If an AI summary labels the five questions “resolved” merely because they were discussed, correct it before finalising the minutes. The defensible output is traceable responses and actions, rather than an automatic declaration of competence.

Reference documentation: Zoom Support — Managing participants in a meeting · Zoom Support — Frequently asked questions about meeting captions and transcript updates.

Connection quality, transcription and participation

An active connection does not establish attention or understanding. Noise, microphone quality, screen size and language differences can affect comprehension. Check technical terms and figures in any transcript or summary before reuse.

Review who can enter, share a screen and access later materials. Avoid accidentally exposing documents, notifications or personal information when sharing a desktop. Capabilities and controls depend on account, configuration and version; a rehearsal should use participant conditions, not only the organiser’s equipment. Prepare a clear way to report a connection problem without losing the opportunity to ask questions.

Reference documentation: Zoom Support — Managing participants in a meeting · Zoom Support — Frequently asked questions about meeting captions and transcript updates.

When to choose Zoom and what complements it

Zoom may fit activities centred on live discussion and remote participation. Where ongoing documentation and conversation within Microsoft 365 are the main requirement, compare Microsoft Teams.

Google Forms can complement a session by collecting structured questions or feedback afterwards. Choose the format according to the learning or decision required, and identify where relevant evidence will be retained without accumulating unnecessary recordings.

Frequently asked questions about Zoom in OSH

Are captions and transcripts the same?

No. Captions support the session; retaining a transcript requires the relevant configuration. Check what is generated and who can access it.

Does a recording prove someone can perform a task?

Not by itself. Viewing content and demonstrating competence are different events requiring evidence appropriate to the objective.

Should every safety meeting be recorded?

Not necessarily. First decide what needs retaining and whether a reviewed summary is sufficient for the purpose.

Reference documentation: Zoom Support — Frequently asked questions about meeting captions and transcript updates.