Advanced Call Recorder 1.5 serial key or number

Upcoming Release

Details about upcoming releases will be posted as they become available.

September 27, 2020

Changes to existing features

• Passcode and Waiting Room requirements
  Zoom will now require that all meetings have a Passcode or a Waiting Room enabled for accounts with a single licensed user, Pro accounts with 2 or more licenses, and Business accounts with 10-100 licenses.
• Updated settings for new accounts
  All new accounts created on or after September 27 will have the passcode settings for Personal Meeting ID (PMI), Personal Audio Conference (PAC), phone dial-in users, and Zoom Room Meeting ID enabled by default.

Resolved issues

• Fixes an issue where users were unable to create a poll question with more than two answers for meetings scheduled with their Personal Meeting ID (PMI)
• Minor bug fixes

Current Release

September 20, 2020

New and enhanced features

• Administrator features
  
  • Specify users to bypass SSO and login with email address and password
    Account owners and admins can now allow specified users to bypass SSO and login with an email address and password, for service accounts or internal IT purposes.

Resolved issues

• Fixes an issue where users with scheduling privilege for 20 or more meeting hosts could not view all meetings in the Zoom web portal at the same time
• Fixes an issue where a subset of users received a 402 error when updating credit card information
• Fixes an issue where alternative hosts were not displayed in the webinar details
• Fixes an issue where hosts were unable to enable pre-assigned Breakout Rooms after the meeting had been scheduled
• Minor bug fixes

Previous Releases

Note: The information in the past release notes may have been superseded by subsequent release notes. Please review all current release notes carefully.

September 17, 2020

Changes to existing features

• Re-enable Call Me and toll-free options for Webinar attendees
  We have re-enabled the ability to control whether Webinar attendees have access to Call Me and toll-free dial-in options. If this setting was previously enabled in the Zoom web portal, attendees can now join by Call Me. This setting can be enabled in account, group, or user settings if the account has an audio conferencing add-on.

September 13, 2020

New and enhanced features

• Web client features
  • Support for Breakout rooms pre-assignment
    The web client will now support pre-assigned Breakout rooms.
  • Support for Internal account members to admit external participants in Waiting Room
    Internal account members can now admit external participants from the web client, if this setting is enabled by the meeting host.

Resolved issues

September 8, 2020

Changes to existing features

• Disable Call Me and toll-free options for Webinar attendees
  We have temporarily disabled the Call Me and toll-free options for webinar attendees and plan to re-enable them in the next few weeks. In the meantime, attendees may connect to Webinar audio through the Zoom desktop client, web client, or mobile app. Webinar hosts and panelists can still join by telephone, as well as through computer audio.

September 6, 2020

Changes to existing features

• Meeting/Webinar hosts must be signed in when initiating live streaming
  Hosts initiating live streaming services will now need to be signed in to the Zoom web portal in order to live stream their meeting or webinar.

New and enhanced features

• Administrator features
  • External authentication
    Account owners and admins can now configure their identity provider to authenticate users via SSO who are joining meetings and webinars. This feature is available for Business, Enterprise, and Education accounts with Single Sign-on (SSO) configured.

Resolved issues

August 30, 2020

Changes to existing features

• Default paid Audio Conferencing settings for webinar attendees to off
  The Audio Conferencing settings for webinar attendees, allowing webinar attendees to use toll-free and fee-based toll numbers and Call Me, will now be defaulted to off. Account owners and admins can re-enable these options in the Zoom web portal, under the Telephone section of Account Settings.

Resolved issues

• Fixes an issue where upcoming meetings and webinars did not appear in the desktop client after the calendar integration settings were locked for their account

August 27, 2020

Resolved issues

• Fixes an issue where users on mobile devices could not complete registration for webinars with Paypal enabled

August 26, 2020

Resolved issues

• Fixes an issue where a subset of users received an error when entering their company domain to sign in to the Zoom web portal

August 25, 2020

Resolved issues

• Fixes an issue where the Meetings page of the Zoom web portal would not load in Internet Explorer
• Minor bug fixes

August 23, 2020

Changes to existing features

• Cloud recording passwords now called Passcodes
  Cloud recording passwords will now be called Passcodes to prevent confusion with your individual user password, which should never be shared.

New and enhanced features

• Administrator features
  • Report of recordings without a passcode
    Account owners and admins can now view a report of all recordings without a passcode. The report is available under the Reports of Account Management. This is a one-time report, with information pulled at the time of the release and will not be updated.
  • Select Germany, the Netherlands, and Ireland as data centers for meetings/webinars hosted by your account
    Germany, the Netherlands, and Ireland will now be listed as individual data centers that can be enabled or disabled for hosting real-time meeting and webinar traffic. This will allow account owners and admins more granular control over where their meetings are hosted. If the Europe data center was enabled, Germany, the Netherlands, and Ireland will be enabled. This is available in account, group, and user settings and can be locked at the account or group level.
  • Upload virtual backgrounds for a group or an individual user
    Account owners can now upload and manage virtual backgrounds for a group on the Zoom web portal. Individual users can upload and manage virtual backgrounds for their own use.
  • Calendar and Contacts section under Account Settings
    Account settings related to calendar and contacts can now be found in the Calendar and Contacts section of the Meeting Tab within Account Settings. Account owners and admins can set the default calendar provider and pick calendar and contact access permissions. These settings can also be locked.
  • Limit which domains can integrate calendar and contact services
    Account owners and admins can now limit which domains can integrate calendar and contact services within Account Settings. Once this setting is enabled, admins can enter which domains are allowed to integrate these services.
  • Setting to prompt user to integrate Office 365 each time they sign in
    Account owners and admins can now enable a setting to prompt users to integrate Office 365 each time they sign in. This will prompt them each time they sign in to Zoom until the integration is completed.
  • Enhanced Office 365 calendar sync
    Users can now sync their Office 365 calendar without requiring full mailbox access.
  • Display certificate expiration date on the Single Sign-on page
    The Single Sign-on page will display the certificate expiration date, warning admins that the certificate will soon expire and allowing them to proactively update the certificate, preventing login issues. Account owners and admins will also receive an email notification 30 days before the certificate will expire.
  • Update users’ names in the webinar attendee report
    If a user changes their name during a webinar, it will now update in the webinar attendee report.
  • Search or download chat history for up to one year for an individual user
    Account owners and admins can now search and download chat history for up to one year for an individual user.
• User features
  • Custom languages for language interpretation
    You can now add custom languages in addition to the default languages provided. Any number of custom languages can be added in the Zoom web portal, but only 5 custom languages can be used in any given meeting or webinar. The interpreter and participants accessing the custom languages will need to be on client 5.2.1 or later to use custom languages.
  • Post webinar survey and reporting
    Webinar hosts can now create a post webinar survey in the Zoom web portal and launch this survey at the end of their webinar. Webinar hosts can also access a report of the survey results in the Zoom web portal.
  • Enhanced Meetings page
    The Meetings page of the Zoom web portal has been enhanced for improved navigation and usability, including the addition of a date range filter to more easily find upcoming meetings.
  • Call Me for Webinar attendees
    Webinar attendees can now use the call me feature for audio. Hosts can enable this option under the Call Me setting on the web, which requires the Audio Conferencing add-on. This feature requires client version 5.2.2 or later. 
  • Language interpretation in Meeting Templates
    Language interpretation settings will now be included as part of saved meeting templates.
  • Open local recordings from the Zoom web portal
    Users can now locate and open their local recordings from the Recordings tab of the Zoom web portal. This will automatically launch their Zoom desktop client.
  • Maximum meeting duration of 30 hours
    The maximum meeting duration has increased from 24 hours to 30 hours.
  • Zoom Room automatically becomes co-host
    The Zoom Room will now automatically become co-host if it was originally scheduled as the host of the meeting and joined after the alternative host, or if the Zoom Room rejoins the meeting after assigning a different host.
• Developer features
  • Added new TSP webhook events.
    • user.tsp_created
    • user.tsp_updated
    • user.tsp_deleted
  • Added account level Chat Channel APIs.
    • POST /v2/chat/users/{userId}/channels
    • GET /v2/chat/users/{userId}/channels/{channelId}
    • PATCH /v2/chat/users/{userId}/channels/{channelId}
    • DELETE /v2/chat/users/{userId}/channels/{channelId}
    • GET /v2/chat/users/{userId}/channels/{channelId}/members
    • POST /v2/chat/users/{userId}/channels/{channelId}/members
    • DELETE /v2/chat/users/{userId}/channels/{channelId}/members/{memberId}
    • Added new account level Chat Message APIs.
    • PUT /v2/chat/users/{userId}/messages/{messageId}
    • DELETE /v2/chat/users/{userId}/messages/{messageId}
  • Added new SIP Trunk APIs.
    • GET /v2/accounts/{accountId}/sip_trunk/trunks
    • POST /v2/accounts/{accountId}/sip_trunk/trunks
    • DELETE /v2/accounts/{accountId}/sip_trunk/trunks/{trunkId}
    • GET /v2/accounts/{accountId}/sip_trunk/callout_countries
    • POST /v2/accounts/{accountId}/sip_trunk/callout_countries
    • DELETE /v2/accounts/{accountId}/sip_trunk/callout_countries/{countryId}
    • GET /v2/accounts/{accountId}/sip_trunk/internal_numbers
    • POST /v2/accounts/{accountId}/sip_trunk/internal_numbers
    • DELETE /v2/accounts/{accountId}/sip_trunk/internal_numbers/{numberId}
  • Added new Dashboard APIs.
    • GET /v2/metrics/satisfaction
    • GET /v2/accounts/{accountId}/metrics/satisfaction
  • Added new Zoom Room APIs.
    • PUT /v2/rooms/{roomId}/devices/{deviceId}/app_version
    • GET /v2/rooms/{roomId}/devices
    • GET /v2/rooms/digital_signage
  • Add new Webinar template API.
    • GET /v2/users/{userId}/webinar_templates
  • Included “X-RateLimit-Type: Daily-limit” and “Retry-After” fields in the response header of Create and Update Meeting APIs.
    • POST /v2/users/{userId}/meetings
    • PATCH /v2/meetings/{meetingId}
  • Added new request field(“type”) in List Webinars APIs.
    • GET /v2/users/{userId}/webinars
  • Added new response fields(“host_email”,“assistant_id”) in Meeting APIs.
    • POST /v2/users/{userId}/meetings
    • GET /v2/meetings/{meetingId}
  • Added new response field(“host_email”) in Webinar APIs.
    • POST /v2/users/{userId}/webinars
    • GET /v2/webinars/{webinarId}
  • Added new request fields(“show_callout_internal_number”,“show_zoom_provided_callout_countries”, “show_zoom_provided_numbers”) in Update Sip Trunk Settings APIs.
    • PATCH /v2/accounts/{accountId}/sip_trunk/settings
  • Added new response fields(“service_effective_date”,“next_invoice_date”,“status”) in Get Plan Information API.
    • GET /accounts/{accountId}/plans
  • Added new response field(“sub_account_privileges”) in Get Role Information API.
  • Added new request field(“sub_account_privileges”) in Update Role Information API.
  • Added new field(“join_url”) in Meeting Registration Approved event.
    • meeting.registration_approved
  • Added new request field (“language”) in Add Meeting Registrant API.
    • POST /v2/meetings/{meetingId}/registrants
  • Added new error messages in Create, Update, Activate User APIs.
    • POST /v2/users
      • 2033 Your request to add a basic user was not approved because you have already reached the maximum basic user limit allowed in your account. For additional help regarding this issue, contact the Zoom Customer Support team.
    • PATCH /v2/users/{userId}
      • 2033 Your request to convert the user type to basic was not approved because you have already reached the maximum basic user limit allowed in your account. For additional help regarding this issue, contact the Zoom Customer Support team.
    • PUT /v2/users/{userId}/status
      • 2033 Your request to activate the basic user was not approved because you have already reached the maximum basic user limit allowed in your account. For additional help regarding this issue, contact the Zoom Customer Support team.
  • Added new field(“allow_recovery_deleted_cloud_recordings”) in Account Setting APIs.
    • GET /v2/accounts/{accountId}/settings
    • PATCH /v2/accounts/{accountId}/settings
  • Added new field(“host_delete_cloud_recording”) in Account and User settings APIs.
    • GET accounts/{accountId}/settings
    • PATCH accounts/{accountId}/settings
    • GET users/{userId}/settings
    • PATCH users/{userId}/settings
  • Added new fields(“meeting_reactions”, “show_a_join_from_your_browser_link”, “recording_disclaimer”, “allow_participants_to_rename”, “required_password_for_shared_cloud_recordings”) in Account Settings, Group Settings, User Settings and Lock Settings APIs.
    • GET accounts/{accountId}/settings
    • PATCH accounts/{accountId}/settings
    • GET accounts/{accountId}/lock_settings
    • PATCH accounts/{accountId}/lock_settings
    • GET groups/{groupId}/settings
    • PATCH groups/{groupId}/settings
    • GET groups/{groupId}/lock_settings
    • PATCH groups/{groupId}/lock_settings
    • GET users/{userId}/settings
    • PATCH users/{userId}/settings
  • Added new fields(“who_can_share_screen”,“who_can_share_screen_when_someone_is_sharing”, “ask_participants_to_consent_disclaimer”, “ask_host_to_confirm_disclaimer”) in Account/Group/User settings APIs.
    • GET accounts/{accountId}/settings
    • PATCH accounts/{accountId}/settings
    • GET groups/{groupId}/settings
    • PATCH groups/{groupId}/settings
    • GET users/{userId}/settings
    • PATCH users/{userId}/settings
  • Added new field(“screen_sharing”) in User settings APIs.
    • GET users/{userId}/settings
    • PATCH users/{userId}/settings
  • Added new fields (“service_effective_date”, “next_invoice_date” and “status”) in Get Plan Information API.
  • Added new field(“required_password_for_existing_cloud_recordings”) in Account/Group settings APIs.
    • GET accounts/{accountId}/settings
    • PATCH accounts/{accountId}/settings
  • Added new value(action=“recover”) in Update meeting status API.
    • PUT /v2/meetings/{meetingId}/status
  • Added new value(setting_type=“signage”) in Zoom Room APIs.
    • GET /v2/rooms/account_settings
    • PATCH /v2/rooms/account_settings
    • GET /v2/rooms/locations/{locationId}/settings
    • PATCH /v2/rooms/locations/{locationId}/settings
    • GET /v2/rooms/{roomId}/settings
    • PATCH /v2/rooms/{roomId}/settings
  • Added new fields(“registrants_confirmation_email”, “template_id”) in Create Webinar APIs.
    • POST /v2/users/{userId}/webinars
  • Added new error message("4137 The IM Group APIs are no longer available.") in IM Group APIs.
    • GET /v2/im/groups
    • POST /v2/im/groups
    • GET /v2/im/groups/{groupId}
    • PATCH /v2/im/groups/{groupId}
    • DELETE /v2/im/groups/{groupId}
    • GET /v2/im/groups/{groupId}/members
    • POST /v2/im/groups/{groupId}/members
    • DELETE /v2/im/groups/{groupId}/members/{memberId}

Resolved issues

• Fixes an issue where external users were automatically added to the primary account with associated domain and forced Single Sign-On login, when they should have been forced to change their email address within Zoom
• Fixes an issue where the account owner and admins could not see how many recordings they were bulk deleting from Recording Management
• Fixes an issue where a subset of users were unable to add Zoom Rooms as a webinar panelist
• Fixes an issue where the meeting details report had missing email addresses
• Fixes an issue where account owners and admins received an error message when trying to invite a subset of users to their accounts
• Fixes an issue where editing a recurring meeting scheduled with no fixed time removed the alternative hosts
• Fixes an issue where a subset of webinar registration pages would not load
• Fixes an issue where a subset of users were unable to add new polls
• Fixes an issue where the registration report listed “null” for some attendees’ approval status when Paypal payment was required
• Fixes an issue where a subset of users received 404 errors when trying to register to view on-demand recordings
• Fixes an issue where a subset of users can login with Google even if the option is disabled
• Fixes an issue where the cloud recording usage report showed an incorrect amount of data being used
• Fixes an issue where data from the month of March is not shown when viewing some data in Dashboard
• Fixes an issue where an on-demand webinar incorrectly showed as full capacity
• Fixes an issue where duplicating a webinar changed the order of the polls
• Fixed a bug that did not allow users to register for a Webinar.
  • POST /v2/webinars/{webinarId}/registrants
• Fixed a bug that prevented alternative hosts from receiving invitation email for a Webinar.
  • POST /v2/users/{userId}/webinars
  • PATCH /v2/webinars/{webinarId}
• Fixed API call logs misconfiguration.
• Fixed a bug that caused incorrect activation link to be included in the invitation email of a newly created Sub Account.
• Fixed a bug where “Meeting does not exist” error was displayed incorrectly in Get Webinar Q&A Report API.
  • GET /v2/report/webinars/{webinarId}/qa
• Fixed a bug where Zoom Room Alert webhook was not being delivered at certain times.
• Fixed a bug that allowed a host to create invalid PMI meetings even when the host did not have a PMI.
  • POST /v2/users/{userId}/meetings
• Fixed a bug that allowed users to schedule meeting for a past start date and time.
  • POST /v2/users/{userId}/meetings
• Minor bug fixes

August 19, 2020

Resolved Issues

August 17, 2020

New and enhanced features

• Setting to request permission to unmute
  Account owners and admins can now enable a setting to request permission to unmute, allowing the host to request permission to unmute meeting participants and webinar panelists. Permissions, once given, will apply in all meetings scheduled by the same person. This setting is available at the account, group or user level and can be locked at the account or group level. This requires client 5.2.0, which is planned for release in early August.

August 16, 2020

New and enhanced features

• General availability
  Zoom Phone is available in 25 more countries.
• Expanded calling to more destinations
  Account owners and admins can enable calling to more destinations. Certain destinations may require admins to contact support to enable. They can also allow calling to “high-risk” prefixes that are otherwise blocked by default. This feature can be enabled by Zoom if you have a legitimate reason to call these destinations.
• Role management
  Account owners and admins can use the role management feature to create Zoom Phone roles and edit each role to control Zoom Phone privileges. For example, they can customize a call queue admin role with privileges to certain settings of specific call queue(s).This enhancement replaces the site admin, call queue manager, and auto receptionist operator roles that could be assigned while customizing the site, call queue, or auto receptionist.
• Support for variable-length site codes and extensions
  Account owners and admins can set variable-length site codes and extensions at the site level. For example, site A with site code 10 and extensions that are 4-digits long in the range of 1000 to 1999; and site B with site code 5 and extensions that are 5-digits long in the range of 20000 to 30000.
• Enhancement to directory backup routing rules
  Account owners and admin can set internal directory routing rules. For example, if the account has variable-length site codes and extensions as stated in the previous example, a rule can prepend site code 5 if a user dials a 5-digit number beginning with 2. This allows users in another site to call users in site B without dialing the site code.
• Control access to personal audio library
  Account owners and admins can control phone users' access to their personal audio library, which is used to change their voicemail greeting and hold music. This new policy setting can be changed at the site level. By default, phone users’ personal audio library is enabled. If disabled, all users in the site will use the site’s default audio.
• Set default custom audio
  Account owners and site admins can set default voicemail greeting, message greeting, hold music, and audio while connecting. These defaults can be set at the site level.
• More options for call queues’ max wait time
  Account owners and admins can set the max wait time to 10, 15, 20, 25, 30, or 45 seconds.

Resolved Issues

August 9, 2020

New and enhanced features

• Administrator Features
  • Standardized naming of Zoom Rooms devices
    Standardized naming will now be applied to Zoom Room devices in the web portal.
  • Setting to require Zoom Rooms devices to be MDM managed
    Account owners and admins can now require all Zoom Rooms devices to be MDM managed. Devices which are not MDM managed will not be able to sign in. 
• Developer Features
  • Added a new field(“custom_attributes”) to User Updated event.
  • Added a new field(“include_fields”) to the request body of List Users API.
  • Added a new response field(“custom_attributes”) to the request body of List Users API.
  • Added a new field(“callout_countries”) that allows a parent account to set Zoom Phone BYOC call-out countries for a Sub account.
    • POST /accounts/{accountId}/plans
    • POST /accounts/{accountId}/plans/addons
    • PUT /accounts/{accountId}/plans/addons
    • GET /accounts/{accountId}/plans

Resolved Issues

• Fixes an issue were a subset of accounts were unable to downgrade their number of licenses
• Fixed a bug that caused internal plan code to be displayed in the response body of Get Plan Usage API call.
  • GET /accounts/{accountId}/plans/usage
• Minor bug fixes

August 2, 2020 

New and enhanced features

• Setting for Video Filters
  Account owners and admins can enable or disable a setting for video filters, which allows meeting participants to use filters to alter the look of their video with color grading, foreground and frame filters. If the meeting host has filters disabled, participants in the meeting will not be able to use filters. This setting will be on by default. It is available at the account, group, or user level and can be locked at the account or group level. 

Resolved issues

• Fixes an issue where webinar hosts were unable to add panelists in Internet Explorer
• Fixes an issue where participants admitted to a meeting from the Waiting Room by someone other than the host were stuck joining and not able to enter the meeting
• Minor bug fixes

July 26, 2020

Resolved issues

July 19, 2020

Changes to existing features

• Meeting and webinar passwords now called Passcodes
  Meeting passwords will now be called Passcodes to prevent confusion with your individual user password, which should never be shared.
• Integrations on Zoom Marketplace
  Zoom Marketplace is now the preferred place for integrations. New setup of the Epic, Panopto, and Zapier Integrations will need to be done through Marketplace. Previously setup integrations are still accessible through the integrations tab. Existing integrations are encouraged to start using Marketplace integration apps instead of older versions.
• Waiting Room moved to Security section when scheduling
  When scheduling a meeting, the Waiting Room setting is now available under a Security heading. Zoom recommends Waiting Room, passcode or both to secure your meeting.

New and enhanced features

• Administrator features
  • Email notifications when cloud recording is available for alternative host
    Users can now choose to send email notifications to the alternative host when the cloud recording for that meeting/webinar is available. This setting is available at the account, group, and user level.
  • Setting for webinar passcodes
    Account owners and admins can enable or disable a setting for webinar passcodes separately from meeting passcodes. This setting is available at the account, group, or user level and lock this setting at the account or group level. If this setting is enabled and locked at the account or group level, it can also be applied to previously scheduled webinars by checking the option below the setting.
  • Configure Waiting Room options without enabling the setting
    Account owners and admins can now configure the Waiting Room options, such as adding approved domains, without enabling the setting. This allows admins to configure these default settings without forcing Waiting Room for all users. Users can enable Waiting Room with these admin configured options at the user or individual meeting level.
  • Auto-save whiteboard content when screen sharing is stopped
    Account owners and admins can now choose to automatically save whiteboard content when screen sharing is stopped. Whiteboard content can be saved as a PDF or a PNG file. This setting is available at the account, group or user level when the whiteboard setting is enabled and can be locked at the account or group level. This requires client 5.2.0, which is planned for release in early August.
  • Scheduled Digital Signage content
    Account owners and Zoom Rooms admins can schedule a window of time when they would like specific Digital Signage content to display, including if it should end on a specific date. This requires the Zoom Rooms client 5.1.0 which is planned for early August.
  • Enable screen sharing, whiteboard and annotation at the room and location level
    Account owners and Zoom Rooms admins can enable screen sharing, whiteboard, and annotation at the room and location level in the Zoom web portal.
  • Unenroll or delete devices from Zoom Device Management
    Account owners and Zoom Rooms admin can unenroll or delete devices from Zoom Device Management (ZDM) through the Zoom web portal.
  • Enhancements to Windows patch installation with Zoom Device Management
    Account owners and Zoom Rooms admins can now choose if they want to automatically install Windows patches in Room settings. They can also search for Windows patches to more easily locate the patch they would like to install.
  • Sync Zoom Rooms for Windows device name
    If the account owner or admin updates the name of the Windows device on the device, it will now update in the Zoom web portal as well.
  • Manage multiple calendar resources for Zoom Rooms
    Account owners and admins can add or delete multiple Zoom Rooms calendar resources simultaneously.
  • Share files with Microsoft SharePoint
    Account owners and admins can enable the Microsoft SharePoint integration, which will enable attendees to share files from SharePoint through in-meeting chat. This feature requires the Zoom client 5.2.0 which will be released in August.
  • View toll-number changes in the operation logs
    Account owners and admins can view changes to available toll numbers in the operation logs on the Reports page of the Zoom web portal.
  • Country/region in telephone report
    The telephone report will list the host’s country/region.
• User features
  • Profile phone number verification with a phone call
    In addition to the option to verify with SMS, users can choose to verify with a phone call to successfully save their phone number in the Zoom web portal under Profile.
  • Download cloud recordings on iOS and iPadOS
    Users on iOS and iPadOS can now download cloud recordings to their devices from the Zoom web portal in Safari. This feature requires iOS or iPadOS 13 or higher.
• Integration features
  • Philippine Peso support for Paypal integration
    Philippine Pesos are a supported currency for Paypal integration.
• Developer features
  • Added new Zoom Room Webhook Events.
    • zoomroom.checked_in
    • zoomroom.checked_out
  • Added a new API to support Zoom Room check in and check out features.
    • PATCH /v2/rooms/{id}/events
  • Added a new API to support in-meeting start and stop recording features.
    • PATCH /v2/live_meetings/{meetingId}/events
  • Added a new field (“account_name”) to the Create a Sub Account API.

Resolved issues

• Fixes an issue where admins could not update a user’s email address when the user was signing in with Single sign-on (SSO)
• Fixes an issue where admins received an error when trying to manually add multiple users
• Fixes an issue where a subset of users were unable to download webinar registration reports
• Fixes an issue where a subset of users received error code 100 when trying to sign in with Single sign on (SSO)
• Fixes an issue where users could not save Meeting Templates if Personal Meeting ID was disabled
• Fixes an issue where webinar reminder emails were sent in the wrong language for a subset of users
• Fixes an issue where the host could not add panelists if the meeting had been converted from a webinar and the panelist had previously been added as an alternative host
• Fixes an issue where users were not showing as contacts if they did not set a password
• Fixes an issue where some Zoom Rooms for macOS were not displaying meetings from Google Calendar after waking from sleep
• Minor bug fixes

July 12, 2020

New and enhanced features

• Administrator features
  • Enable AES-256 bit encryption for Zoom Phone devices
    Account owners and admins can upgrade to SRTP with AES-256 bit encryption for specific sites and models. By default, AES-128 bit is enabled. Admins must enable AES-256 bit in the web portal. Learn more about Zoom Phone Encryption.
  • Call monitoring (listen, whisper, barge, takeover)
    Account owners and admins can enable call monitoring features for phone users. Phone users can: listen to a call without the parties being aware; speak to a phone user in a call without other parties being aware; join a call and speak to all parties; or take over the call from another user.
  • Call park
    Users can place a call on hold and generate a retrieval code. Any other Zoom Phone user can use the retrieval code to answer the call. Admins can set routing rules if parked calls are not answered after a specified amount of time
  • Create a shared directory of external contacts
    Account owners and admins can create a shared directory of external contacts. They can add contacts one at a time or batch import contacts using a CSV file. This is not supported on desk phones.
  • Singapore data center option
    Account owners and admins can opt in to use a Singapore region data center for real-time meeting and webinar traffic.
• User features
  • Customize speed dial and busy lamp field for devices
    Users can add line keys for speed dial and busy lamp field (BLF). Speed dial allows users to easily dial a number by pressing a line key. BLF allows users to see the call status of another internal line.
  • Call park
    Users can place a call on hold and generate a retrieval code. Any other Zoom Phone user can use the retrieval code to answer the call. Admins can set routing rules if parked calls are not answered after a specified amount of time.

Resolved Issues

June 28, 2020

New and enhanced features

• Administrator features
  • Report of upcoming meetings without a password or Waiting Room
    Account owners and admins can now view a report of all upcoming meetings without a password or Waiting Room, including meetings scheduled with PMI and on-going recurring meetings. The report is available under the Reports of Account Management, in the Active Host report queue. This is a one-time report, with information pulled at the time of the release and will not be updated.
  • IM setting to show or hide users’ presence status to their external contacts
    Account admins now have the ability to show or hide their users’ presence status to external contacts. This setting can be found in the Zoom web portal, under IM Settings.
  • New security heading for meeting settings
    All password related settings, Waiting Room settings, and the settings to only allow authenticated users to join meetings will now be moved under the Security heading of the account, group, and user settings to allow users to more easily enable security options for their meetings and webinars.
  • Setting to sign in with Apple ID on iOS
    Users can sign in with Apple ID on the iOS app (version 5.1.1 or higher). Account owners and admins can disable this feature in the Zoom web portal, under Advanced then Security.
• User features
  • User Profile Phone Verification and Privacy Disclosure
    All users must now verify their phone number via SMS in order to successfully save their phone number in the Zoom web portal under Profile. Upon verification, users will be shown a privacy disclosure that their phone number will be visible to their Zoom contacts on their profile.
  • External contact email invitation privacy disclosure
    When users send or accept an external contact invitation, they will be shown a privacy disclosure explaining that their profile information and, depending on the account IM Settings, their presence status will be visible to the external contact upon successful connection.
• Integration features
  • Always embed meeting password on Workplace by Facebook
    If using Zoom’s integration with Workplace by Facebook, Zoom will always embed the meeting password in the meeting link, even if the web setting to embed the password is disabled.
• Developer features
  • Added a new field(“meeting_authentication”) in the payload of User Settings Updated webhook.
  • Added new response fields(“audio_device_from_crc”,“audio_device_to_crc”,“video_device_from_crc”,“video_device_to_crc”,“as_device_from_crc”,“as_device_to_crc”) in the Dashboard Participants QoS APIs.
    • GET /v2/metrics/meetings/{meetingId}/participants/{participantId}/qos
    • GET /v2/metrics/webinars/{webinarId}/participants/{participantId}/qos
    • GET /v2/metrics/meetings/{meetingId}/participants/qos
    • GET /v2/metrics/webinars/{webinarId}/participants/qos
  • Added a new response field(“email”) in the List Meeting Participants API.
    • GET /v2/metrics/meetings/{meetingId}/participants
  • Added a new response field(“location_id”) in the List Zoom Rooms API.
  • Added a new response field(“pmi”) in the List User Schedulers API.List Schedulers API.
    • GET /v2/users/{userId}/schedulers
  • Added a new response field(“custom_attributes”) in the Get User Details API.
  • Added a new request field(“custom_attributes”) in the Update a User API.
  • Added a new response field(“custom_attributes”) in Get Active Host Reports API.
  • Deprecated the “page_number” field and replaced it with “next_page_token” in the Batch List APIs.
    • GET /v2/accounts
    • GET /v2/meetings/{meetingId}/recordings/registrants
    • GET /v2/h323/devices
    • GET /v2/im/groups/{groupId}/members
    • GET /v2/users/{userId}/meetings
    • GET /v2/meetings/{meetingId}/registrants
    • GET /v2/users/{userId}/webinars
    • GET /v2/webinars/{webinarId}/registrants
  • Enabled assistants to retrieve meeting host’s settings by identifying the assistants with their OAuth token.
    • GET /v2/users/{userId}/settings
  • Added support for both User ID and User Email in the following User Level APIs. Developers are no longer required to pass the me keyword for these APIs.
    • GET /v2/users/{userId}/settings
    • PATCH /v2/users/{userId}/settings
    • PUT /v2/users/{userId}/password
    • GET /v2/users/{userId}/assistants
    • POST /v2/users/{userId}/assistants
    • DELETE /v2/users/{userId}/assistants
    • DELETE /v2/users/{userId}/assistants/{assistantId}
    • POST /v2/users/{userId}/picture
    • GET /v2/users/{userId}/token
    • DELETE /v2/users/{userId}/token
    • GET /v2/users/{userId}/permissions
    • GET /v2/users/{userId}/schedulers
    • DELETE /v2/users/{userId}/schedulers
    • DELETE /v2/users/{userId}/schedulers/{schedulerId}
    • PUT /v2/users/{userId}/email
    • GET /v2/users/{userId}/meetings
    • POST /v2/users/{userId}/meetings
    • GET /v2/users/{userId}/webinars
    • POST /v2/users/{userId}/webinars
    • GET /v2/users/{userId}/recordings

Resolved issues

• Resolves an issue where some Mac users were prompted to install Zoom each time they joined a meeting
• Resolves an issue where some users would receive an error when attempting to update their display name on the Zoom web portal
• Resolves an issue where some users were unable to edit branding of the Meeting Schedule email
• Resolves an issue where some webinar registrants did not receive the confirmation email
• Resolves an issue where users were unable to update their time zone if Personal Meeting ID was disabled
• Resolves an issue where the QoS data for Device to/from CRC was not included in downloaded reports (CSV)
• Resolves an issue where some users received an error when trying to download a report from Dashboard
• Resolves an issue where the post webinar survey field ignored case on the configured links, causing some links to be invalid
• Fixed the bug that caused all available call-out counties to be returned in the response even when an account subscribed to the Phone base plan with only specific call-out countries.
  • POST /v2/accounts/{accountId}/plans
• Fixed an error where a clear message was not being displayed when users tried to use expired PMI meetings.
  • POST /v2/users/{userId}/meetings
• Fixed the bug where the value of ‘mute_upon_entry’ in the Create a Meeting API was not being inherited from the Account Settings.
  • POST /v2/users/{userId}/meetings
• Fixed the bug where the PMI property was still being displayed when a meeting scheduled with PMI was updated to a recurring meeting with the value of “use_pmi” field set to “false”.
  • PATCH /v2/meetings/{meetingId}
• Fixed the bug that caused incorrect values to be displayed for the ‘created_at’ field in the response of the List Users API.
• Fixed the bug that prevented chat messages sent by Client from being updated using the Update a Chat Message API.
  • PUT /v2/chat/users/me/messages/{messageId}
• For the following APIs, we replaced incorrect errors with improved error messages(listed below) that will be displayed in scenarios where an account with the maximum permitted number of users, tries to add another user.
  • POST /v2/users
    • Your request to add a basic user could not be approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to add another user.
    • Your request to add a new {userType} user could not be approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} paying users. Please purchase additional licenses or contact the Zoom support team to provision additional users in your account.
  • PATCH /v2/users/{userId}
    • Your request to convert the user type of this {userType} user to a basic user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to convert a paying user to a basic user.
    • Your request to convert the user type of this basic user to a {userType} user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} paying users. Please purchase additional licenses or remove existing paying user(s) from your Users list or the Pending Users list before attempting to convert a basic user to a paying user.
  • PUT /v2/users/{userId}/status
    • Your request to activate the user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to activate this user.
• Minor bug fixes

June 14, 2020

Changes to existing features

• Limited outbound caller ID options
  When selecting their outbound caller ID, phone users can only choose phone numbers from the main auto receptionist by default. Previously, phone users could choose numbers from any auto receptionist.
• CSV fields for importing phone users
  When importing phone users, the CSV contains fields for first name and last name. Previously, the CSV only had a single field for first and last name.

New and enhanced features

• Administrator features
  • Setting to disable email and password login
    Account owners and admins can now disable logging into Zoom with an email address and password. This setting can be found in the Zoom web portal, under Advanced then Security.
  • Setting to disable participant annotation
    Account owners and admins can now disable participant annotation from the Zoom web portal. The participant who is sharing their screen can still annotate, but all other participants will be prevented from annotating if this setting is enabled. This setting is available at the account, group, and user level.
  • Meeting password requirements options
    The account owner or admin can now enable minimum password requirements for meetings, including requiring both uppercase and lowercase letters or cannot contain consecutive characters (such as “12345” or “abcde”). For these settings to be enforced, users will need to be on Zoom client 5.1.0 or later.
  • Configure allowed domains for bypassing the Waiting Room
    Account owners and admins can now add domains which can bypass the Waiting Room. If a user is logged in to their Zoom account with an email address at this domain, they will bypass the Waiting Room and join directly into the meeting.
  • Export single sign-on (SSO) SAML logs
    Account owners and admins can now export SSO logs to troubleshoot issues.
  • Manage virtual backgrounds for the account
    Account owners and admins can now add virtual backgrounds to the Zoom web portal for all users on their account. If the virtual background setting is locked, users will only have access to the admin uploaded virtual backgrounds and will not be able to add their own from the Zoom client. This setting is available at the account and group level and requires Zoom client version 5.1.1.
• User features
  • Italian and Vietnamese language support
    The Zoom web portal will now use Italian or Vietnamese by default, based on the user’s browser settings. Users can also manually select Italian or Vietnamese from a drop down list of languages in the web portal footer.
• Phone features
  • Set account-level data retention policy
    Account owners and admins can set the amount of time that Zoom Phone user data is retained in the system. This data includes call logs, ad hoc / automatic call recordings, voicemail recordings/transcriptions.
  • Disable voicemail transcription
    Account owners and admins can change a policy setting to disable voicemail transcription for a phone user, site, account (single site).
  • Disable voicemail
    Account owners and admins can change a policy setting to disable the voicemail inbox for a phone user, site, or account (single site).
  • Nomadic emergency services
    Nomadic emergency services provide the ability to dynamically detect and report a user's location for emergency calling. Account owners and admins define locations, specifying a street address, IP addresses ranges, and/or wireless access point identifiers. When a phone user places an emergency call from within a defined location, the associated emergency address will be sent to emergency responders. For sites in the United States and Canada, this dynamic location data can be sent to both the public safety answering point (PSAP) and to an internal safety response team.
  • Upload CSV file for nomadic emergency services
    Account owners and admins can upload a CSV file to add locations and specify the associated IP address ranges, wireless access point identifiers, and emergency addresses.
  • Personal locations for nomadic emergency services
    Account owners and admins can enable users to define locations and specify an emergency address. The Zoom client will automatically save the IP address or wireless access point identifiers for the location. When a phone user places an emergency call from a defined location, the associated emergency address will be sent to emergency responders.
  • Sort users
    Account owners and admins can sort users when adding them to Zoom Phone.
  • Control selectable outbound caller IDs
    Account owners and admins can control if phone users can change their outbound caller ID to a direct number that is assigned to a call queue, auto receptionist, or shared line group.
  • Enhancements to call queue membership
    Account owners and admins can assign multiple managers to a call queue. They can also remove managers from call queues and create call queues with no members.
  • Enhancements to call queue routing options
    Account owners and admins can change routing options so that inbound calls are disconnected instead of routed to voicemail. They can also set the call queue’s business hours to override members’ own business hours.
  • Set call queue as an internal safety response team
    When account owners and admins set a call queue as an internal safety response team, they will be prompted to change business hours and overflow settings for the associated call queue. This call queue will be labelled as an internal safety response team and some settings will be restricted when emergency calls are routed to the call queue.
  • Control privileges for call queue managers
    Account owners and admins can control if call queue managers can enable or view automatic recordings for the call queue. They can also control if managers can grant access for phone users to view the call queue’s recordings
  • Set default language of audio prompts
    Account owners and admins can set the default language of audio prompts for call queues and auto receptionists. This overrides the site-level setting.
  • Set display name for phone numbers
    Account owners and admins can set a display name for phone numbers. This makes it easier for phone users to identify numbers when selecting an outbound caller ID number.
  • Customize voicemail greeting for IVR
    Account owners and admins can customize the voicemail greeting when routing to the current auto receptionist’s voicemail inbox.
  • Forward calls to an external number
    Account owners and admins can configure an IVR menu to forward calls to an external phone number. They can also set a call queue to overflow to an external number. Calls will be metered at the plan rate.
  • Enhancement to dial-by-name directory
    If the dial-by-name directory is enabled, account owners or admins can create the directory by excluding or including phone users.
  • Hyperlink for all call queues and auto receptionists display names
    All display names for call queues and auto receptionists are hyperlinked so account owners and admin can easily access the associated settings.
  • Main company number not required for setup
    During the initial Zoom Phone setup, account owners and admins are not required to set a main company number. This can be done after the initial set up.
  • Set phone numbers as outgoing or incoming
    Account owners and admins can set phone numbers to be outgoing or incoming numbers. Outgoing numbers can only be used to make calls. Incoming numbers can only be used for receiving calls.
  • Change the main company numbers to pending number
    Account owners and admins can change the main company number to a number that is in the process of being ported to Zoom Phone. If the pending number is verified, they can also use the pending number as the outbound caller ID.
  • Disable announcement for ad hoc recordings
    Account owners and admins can disable the announcement that plays before an ad hoc recording is started. The announcement is enabled by default. They can change this policy setting at the phone, site, or account (single site) level.
  • Number ordering form
    Account owners and admins can use the web portal to submit a request to obtain phone numbers when they can’t directly purchase them. Previously, they had to use an external form to request numbers.
  • Hot desking for desk phones
    Account owners and admins can enable phone users in the account to temporarily use a desk phone by entering their voicemail PIN. This allows phone users to easily use shared devices.
  • Set overflow options for common area phones
    Account owners and admins can route inbound calls to common area phones if the call is not answered.
  • Personal locations for nomadic emergency services
    Users can define locations and specify an emergency address. The Zoom client will automatically save the IP address or wireless access point identifiers for the location. When a phone user places an emergency call from a defined location, the associated emergency address will be sent to emergency responders.
  • Address suggestion when changing emergency address
    When a phone user changes their emergency address, they will see a suggested address. They can choose to use the suggested address or the address they entered.
  • Accept or decline delegation responsibilities
    Users who have been assigned as a delegate can accept or decline the delegation responsibilities before calls are forwarded to them. The delegate will appear as pending until they accept or decline.
• Developer features
  • Added a new API to retrieve call queue recordings
    • GET /v2/phone/call_queues/{callQueueId}/recordings
  • Added new APIs for Shared Line Group Management
    • POST /v2/phone/shared_line_groups -PATCH /v2/phone/shared_line_groups/{sharedLingGroupId}
    • GET /v2/phone/shared_line_groups
    • GET /v2/phone/shared_line_groups/{sharedLineGroupId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}
    • POST /v2/phone/shared_line_groups/{sharedLineGroupId}/members
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/members/{memberId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/members
    • POST /v2/phone/shared_line_groups/{sharedLineGroupId}/phone_numbers
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/phone_numbers/{phoneNumberId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}
  • Added a new API for Auto Receptionist Management
    • POST /v2/phone/auto_receptionists
  • Added a new response field(“country”) to the List Sites and Get A Site APIs
    • GET /v2/phone/sites
    • GET /v2/phone/sites/{siteId}
  • Added a new response field(“calling_plans”) to the List Users API
  • Added a new response field(“site_admin”) to the Get A User Profile API
    • GET /v2/phone/users/{userId}
  • Added a new response field(“next_page_token”) to replace page_number for the below APIs
    • GET /v2/phone/users/{userId}/call_logs
    • GET /v2/phone/call_logs
    • GET /v2/phone/user/{userId}/recordings
    • GET /v2/phone/users/{userId}/voice_mails
  • Allow free trial plan to be upgraded to Pro or Higher plans via API.
    • PATCH /accounts/{accountId}/plans/base/status
  • Added a new field(“ttl”) to Get ZAK Token API
    • GET /users/{userId}/token
  • Added a strict limit for number of basic users in an account. An account can only have a maximum of 9999 users including pending users.
    • POST /users
    • PATCH /users/{userId}
    • PUT /users/{userId}/status
  • Added a new field value(“option”:“security”) in Account Setting APIs
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
  • Added new fields(“have_upper_and_lower_characters”,“consecutive_characters_length”,“weak_enhance_detection”) in Account and User Setting APIs
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /users/{userId}/settings

Resolved issues

• Resolved an issue where attempting to edit a subset of meetings in the Zoom web portal redirected the host to a webinar page instead
• Resolved an issue where some users did not have the option to remove scheduling privilege
• Resolved an issue where the join link in a webinar confirmation email required some users to be directed back to the registration page
• Resolved an issue where some users were not receiving emails related to manage domains
• Resolved an issue where ‘Require Encryption for 3rd Party Endpoints (H323/SIP)’ also affected Meeting Connector connections for on-premise accounts
• Fixed the bug that incorrectly caused “No permission” error while retrieving webinar absentees.
  • GET /v2/past_webinars/{webinarId}/absenteese
• Fixed the bug where auto-create user option was allowing existing users to be automatically pulled into an account.
• Fixed the issue that caused certain PMI settings to be overridden when using Create a Meeting API.
  • POST /users/{userId}/meetings
• Fixed the bug that returned incorrect security password settings via Get Account Settings API.
  • GET /accounts/{accountId}/settings
• Minor bug fixes

May 31, 2020

Changes to existing features

• AES 256-bit GCM encryption
  Zoom is upgrading to the AES 256-bit GCM encryption standard, which offers increased protection of your meeting data in transit and resistance against tampering. This provides confidentiality and integrity assurances on your Zoom Meeting, Zoom Video Webinar, and Zoom Phone data. GCM encryption requires Zoom client or Zoom Rooms version 5.0 to join any meeting. Learn more.

New and enhanced features

• Administrator features
  • Setting to save screen sharing and whiteboard annotations
    Account owners and admins can now enable or disable a setting to save screen sharing and whiteboard annotations. This setting is enabled by default. It is available at the account, group, and user level and can be locked at the account or group level.
• Web client features
  • Report a user during a meeting
    The meeting host can now report a user during a meeting by clicking on the Security icon, then Report. This feature will generate a report which will be sent to the Zoom Trust and Safety team to evaluate any misuse of the platform and block a user if necessary. 
  • Require consent if the host mutes and then unmutes a participant
    If the host mutes and then unmutes a participant individually, the participant will now receive a prompt, asking them to consent to be unmuted. 
• Developer Features
  • Added a new API to get Call Queue Recordings
    • GET /v2/phone/call_queues/{callQueueId}/recordings
  • Added new APIs for Shared Line Group Management
    • POST /v2/phone/shared_line_groups
    • PATCH /v2/phone/shared_line_groups/{sharedLingGroupId}
    • GET /v2/phone/shared_line_groups
    • GET /v2/phone/shared_line_groups/{sharedLineGroupId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}
    • POST /v2/phone/shared_line_groups/{sharedLineGroupId}/members
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/members/{memberId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/members
    • POST /v2/phone/shared_line_groups/{sharedLineGroupId}/phone_numbers
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}/phone_numbers/{phoneNumberId}
    • DELETE /v2/phone/shared_line_groups/{sharedLineGroupId}
  • Added a new API for Auto Receptionist Management
    • POST /v2/phone/auto_receptionists
  • Added a new field(“show_previous_occurrences”) to Get a Webinar API.
    • GET /webinars/{webinarId}
  • Added new response field(“next_page_token”) to replace page_number for the following APIs:
    • GET /v2/phone/users/{userId}/call_logs
    • GET /v2/phone/call_logs
    • GET /v2/phone/user/{userId}/recordings
    • GET /v2/phone/users/{userId}/voice_mails
  • Added a new response field(“country”) to the List Sites And Get a Site APIs
    • GET /v2/phone/sites
    • GET /v2/phone/sites/{siteId}
  • Added a new response field(“calling_plans”) to the List Users API
  • Added a new response field(“site_admin”) to the Get A User Profile API
    • GET /v2/phone/users/{userId}

Resolved issues

• Removed “Duplicate Key” error that was returned incorrectly while using the following APIs:
  • GET /v2/chat/users/me/contacts
  • GET /v2/chat/channels/{channelId}/members
• Fixed a bug that caused “No permission” error when account owners were trying to update their own meeting recording settings.
  • PATCH /meetings/{meetingId}/recordings/settings
• Minor bug fixes

May 23, 2020

Resolved issues

• Resolved an issue where Dashboard data was delayed or missing

May 21, 2020

Changes to existing features

• New default screen sharing settings for accounts with single Pro licenses
  Accounts with single Pro licenses will now have the screen sharing setting Who can share? defaulted to Host Only. The meeting host will be able to change this setting in their meeting settings or during the meeting in progress, from the Security icon.

New and enhanced features

• Administrator features
  • Setting to require a password for Personal Audio Conference
    Account owners and admins can now enable a setting to require a password for Personal Audio Conferences. This setting is available at the account and group and can be locked at the account or group level. This setting will be visible at the user level so that users can see if it is enabled for their Personal Audio Conferences.
• User features
  • Setting to allow participants to join from multiple devices for meetings with registration
    If registration is enabled for a meeting, the host can now choose if they want to allow participants to join from multiple devices. This is under the Registration Options in the meeting details.
• Developer features
  • Added support for private recordings to be downloaded using OAuth access token.
    • Account-Level Apps will need “recording:read:admin, recording:write:admin, recording:parent” scopes.
    • User-Level Apps will need “recording:read, recording:write” scopes.
    • A user with recording management permission can view private recordings recorded by another user in the same account.
  • Added a new field (show_previous_occurrences) to Get a Meeting API.
    • GET /meetings/{meetingId}
  • Added a new field(waiting_room) in Account Settings and Lock Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /accounts/{accountId}/lock_settings
    • PATCH /accounts/{accountId}/lock_settings
  • Added new fields (guest_only_to_place_in_waiting_room,auto_admit_participants_with_specified_domains,admit_participants_with_specified_domains) in Account, Group, User Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /groups/{groupId}/settings
    • PATCH /groups/{groupId}/settings
    • GET /users/{userId}/settings
    • PATCH /users/{userId}/settings
  • Added new fields(room_connector_list,meeting_connector_list) in Create a Sub Account and Update Account Options APIs.
    • POST /accounts
    • PATCH /accounts/{accountId}/options

Resolved issues

• Fixed an issue where unknown was shown for a user’s type in Dashboard
• Fixed an issue where .zip files downloaded from Reports and Dashboard would not open with certain programs
• Fixed an issue where a subset of meetings requested the password when it was embedded in the invite link
• Fixed an issue where “password” was not being auto-generated even when “Require a Password When Scheduling New Meetings” option was turned on for free accounts in the case where “Create a Meeting API” was being called using PMI without a “password” field.
  • POST /users/{userId}/meetings
• Fixed the issue where SIP Trunk related plans were not being displayed in the response of Get Plans API.
  • GET /accounts/{accountId}/plans
• Fixed the issue where the same email address was being used for two different user IDs.
• Minor bug fixes

May 11, 2020

Resolved issues

• Fixed an issue where a subset of users were unable to live stream their webinars
• Minor bug fixes

May 9, 2020

Changes to existing features

• Updated password and security settings for free and basic accounts
  To provide additional security and privacy for Zoom meetings and webinars, we are updating our default password settings for free and basic accounts. Zoom will require passwords for meetings and webinars, including previously scheduled events. Additionally, Waiting Room will be enabled by default for Personal Meeting ID (PMI) and screen sharing will be limited to “host only” by default. Learn more.
• Enhanced privacy on the Zoom Rooms page
  The Room passcode will now be masked with asterisks (*). Full details will only be shown when the user explicitly clicks on the “show” option.

New and enhanced features

• Administrator features
  • Associated (managed) domain enhancements
    Managed domains have now been renamed associated domains. Account owners and admins can now choose if they want to have unassociated existing Zoom accounts automatically join their account or be forced to change the email address associated with the account or delete the account entirely. Additionally, once an associated domain is added, the owner can choose to send notifications to any existing Zoom accounts with email addresses at that associated domain telling them that they must take action.
  • Setting to Save meetings and webinar recordings as WORM (Write Once, Read Many) state
    Account owners and admins can now add a web setting to save meetings and webinar recordings as WORM (Write Once, Read Many) state and configure a retention time range. By enabling this setting, the recordings cannot be edited or deleted until the specific retention time expires. This setting is available at the account level and is off by default. Contact Zoom Support to have this feature enabled.
  • Enhancements for Dashboard
    The data center will now be listed at the individual attendee level in Dashboard.
  • Complexity requirements for voicemail PINs
    Account owners and admins can require voicemail PINs to meet complexity requirements. For example, the PIN can’t contain the user’s extension, repeated digits, a sequence of numbers, or numbers dialed in a straight line on the keypad.
  • Security disclaimer for contact center integration
    Accounts owners and admins will see a disclaimer when adding a contact center partner that doesn’t support TLS/sRTP.
  • Disclaimer for caller ID name
    Account owners and admins will see a disclaimer when changing the account’s or site’s caller ID name. The disclaimer states: “Caller ID name will be applied to US/CA toll numbers. This is a ‘best effort’ service with limitations.”
• User features
  • Privacy disclaimer for emergency address
    Users will see a disclaimer when adding an emergency address. The disclaimer states: “This address will be shared with your account’s administrator(s). In the event of a 911 call, it may be shared with the Public Safety Answering Point and with members of the account’s Internal Safety Response Team.”
• Developer Features
  • Added new API RateLimiter response headers.
    • X-RateLimit-Category
    • X-RateLimit-Type
  • Added a new field(“password_requirement”) in Account Settings APIs that shows the enhanced password rules set for a Zoom login password.
    • GET /v2/accounts/{accountId}/settings
    • PATCH /v2/accounts/{accountId}/settings
  • Enhanced the validation of user password to follow the password rule settings enabled on Account Security settings.
    If an admin has set enhanced password rules, the password field in the following APIs must meet those requirements. The requirements can be retrieved from the password_requirement field that will be available in the response of Get Account Settings API.
    • POST /v2/users
    • PUT /v2/users/{userId}/password
    • POST /v2/accounts
•  

Bug fixes

• Resolves an issue where the Outlook add-in was not working on shared calendars
• Fixed a bug that prevented these two fields(“contact_name”, “contact_email”) from being updated when using the Update a Webinar API.
  • PATCH /v2/webinars/{webinarId}
• Fixed the issue where the field(“last name”) last name was previously set as a required field instead of optional in the Add a Webinar Registrant API.
  • POST /v2/webinar/{webinarId}/registrants
• Fixed the issue where wrong value was being returned for the “custom_data_center_regions” field when calling Get Account Lock Settings API.
  • GET /accounts/{accountId}/lock_settings
• Minor bug fixes

May 3, 2020

New and enhanced features

• Administrator features
  • Setting to disable PMI
    Account owners and admins can now disable the use of Personal Meeting ID (PMI), forcing users to choose the option to generate a meeting ID automatically when scheduling a meeting. If this setting is disabled, it will disable the use of PMI completely, including for previously scheduled meetings. Users will need to edit previously scheduled meetings to use an automatically generated meeting ID and resend the meeting invitation. This setting is available at the account, group, and user level and can be locked at the account and group level. PMI can also be disabled for Zoom Rooms. 
• Web client features
  • AES 256-bit GCM encryption
    Zoom is upgrading to the AES 256-bit GCM encryption standard, which offers increased protection of your meeting data in transit and resistance against tampering. This provides confidentiality and integrity assurances on your Zoom Meeting, Zoom Video Webinar, and Zoom Phone data. The web client will support GCM encryption when it is automatically enabled for all accounts on May 30. When GCM encryption is enabled, the web client will indicate this with an icon.
  • Show the connected data center
    Users can see which data center they are connected to by clicking on by clicking on the info icon at the top left of the window.
  • Promote and demote webinar attendees
    The web client will now support promoting and demoting attendees during a webinar.
• Developer features
  • Enhanced User and Meeting APIs to follow “Disable PMI” setting applied on Account, Group and User settings.
    • GET /meetings/{meetingId}
    • POST /users/{userId}/meetings
    • PATCH /meetings/{meetingId}
    • GET /meetings/{meetingId}/invitation
    • GET /users
    • GET /users/{userId}
    • PATCH /users/{userId}
  • Added a new field(“personal_meeting”) in Account, Group, User Settings, and Lock Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /accounts/{accountId}/lock_settings
    • PATCH /accounts/{accountId}/lock_settings
    • GET /groups/{groupId}/settings
    • PATCH /groups/{groupId}/settings
    • GET /groups/{groupId}/lock_settings
    • PATCH /groups/{groupId}/lock_settings
    • GET /users/{userId}/settings
    • PATCH /users/{userId}/settings 

Resolved issues

• Fixed a bug that didn’t allow an admin’s password to be updated using the Update Password API.
• Fixed a bug that didn’t allow a user whose name was entered in Kanji characters to be registered if the length of the name field was more than 5 characters.
• Minor bug fixes

April 29, 2020

New and enhanced features

• Developer features
  • Added new fields (meeting_password_requirement,recording_password_requirement) in the User Settings API.
    You should use this API to check if password requirements have been set for an account, and ensure that your meeting, webinar and recording passwords meet those requirements. If the “meeting_password_requirement” field is not present in the response of the Get User Settings , it means that the admin/owner has not enabled this requirement. In this case, the password must follow the default requirements, i.e., password may only contain the following characters: [a-z A-Z 0-9 @ - _ *] and can have a maximum of 10 characters.
    • GET /users/{userId}/settings 

Resolved issues

• Resolved an issue where a subset of users on ChromeOS were unable to join meetings
• Minor bug fixes 

April 27, 2020

Resolved issues

• Resolved an issue where users needed to be authenticated and on the same account to view cloud recordings even if that setting is not turned on by admin or host

April 26, 2020 

Changes to existing features

• Disable the setting Only authenticated users can join meetings from Web client by default
  The setting Only authenticated users can join meetings from Web client will now be turned off by default. This change applies to all accounts and can be re-enabled at the account, group, or user level. 
• Minimum password length of 6 characters for meeting and shared recording passwords
  The minimum password length for both meeting and shared recording passwords will now be 6 characters. 
• Removing same domain matching for all customers
  All customers that share the same domain but belong in different accounts will no longer be able to communicate with each other unless previously added as external contacts. To continue communicating, they can add them as external contacts or link their accounts together into one organization.

New and enhanced features

• Administrator features
  
  • Add expiration date for shared cloud recordings
    Users can now choose to expire the link for a cloud recording after a set number of days or on a custom date. This setting is available for individual recordings and at the account, group, and user level and can be locked at the group or account level. 
• User features
  • Select data center regions when scheduling a meeting
    Users can now select which data center regions they would like their in meeting traffic to use when scheduling on the Zoom web portal. 
• Web client features
  • Rename meeting hosted with Personal Meeting ID (PMI)
    Meetings hosted with Personal Meeting ID (PMI) can now be renamed during the meeting to help the host more easily identify recordings.
• Developer features
  • Added an additional parameter “password” to the Meeting Created Event.
  • While creating a meeting or a webinar, the “password” field must follow the “Meeting password requirement” setting enabled on the account settings page.
    • POST /users/{userId}/meetings
    • PATCH /meetings/{meetingId}
    • POST/users/{userId}/webinars
    • PATCH /webinars/{webinarId}
  • The “password” field to access a recording must follow the “Recording password requirement” setting enabled on the account settings page.
    • PATCH /meetings/{meetingId}/recordings/settings
  • Enhanced the rate limit on Change User Email API. A maximum of 3 email update requests are permitted for a single user in one day.
  • Enhanced the User APIs to ignore the “.” sign which is before the “@” symbol for a gmail account as dots do not matter in a gmail account:
    • POST /users
    • GET /users/{userId}
    • DELETE /users/{userId}
    • PATCH /users/{userId}
    • PATCH /users/{userId}/settings
    • GET /users/{userId}/settings
    • PUT /users/{userId}/email
  • Added new fields(“custom_data_center_regions”, “personal_meeting”) in Account Settings, Group Settings, User Settings and Lock Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /accounts/{accountId}/lock_settings
    • PATCH /accounts/{accountId}/lock_settings
    • GET /groups/{groupId}/settings
    • PATCH /groups/{groupId}/settings
    • GET /groups/{groupId}/lock_settings
    • PATCH /groups/{groupId}/lock_settings
    • GET /users/{userId}/settings
    • PATCH /users/{userId}/settings
  • Added new fields(“data_center_regions”) in Account Settings, Group Settings and User Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
    • GET /groups/{groupId}/settings
    • PATCH /groups/{groupId}/settings
    • GET /users/{userId}/settings
    • PATCH /users/{userId}/settings
  • Added new fields(“meeting_password_requirement”,“recording_password_requirement”) in Account Settings APIs.
    • GET /accounts/{accountId}/settings
    • PATCH /accounts/{accountId}/settings
  • Added new fields(“additional_data_center_regions”) in Meeting and Webinar APIs
    • POST /users/{userId}/meetings
    • PATCH /meetings/{meetingId}
    • POST /users/{userId}/webinars
    • PATCH /webinars/{webinarId}

Resolved issues

• Resolved an issue where a subset of users were unable to download their telephony reports
• Resolved an issue with Lastpass automatically filling in the incorrect password
• Fixed the null pointer exception error that was thrown while users called the Create Chat Channel API
• Fixed the issue where a custCreate user previously could not be searched by email domain in the web portal
• Fixed the issue where participant location was being returned as “null” via Dashboard Meeting Participant API
• Minor bug fixes

April 22, 2020

Resolved issues

April 20, 2020

Resolved issues

April 19, 2020

Changes to existing features

• Remove searching for same domain contacts
  Users will no longer be able to search by full name for contacts with the same domain if they are not on the same account or organization. To continue chatting with contacts outside of their Zoom account, they can add them as external contacts.
• Enhanced privacy design on user profile page
  Personal information, such as email address, personal meeting ID and phone number, will be partially masked with asterisks (*). Full details will only be shown when the user explicitly clicks on the “show” option.
• Skype for Business (Lync) users will join webinars as attendees by default
  Users joining a webinar with Skype for Business (Lync) will now join as attendees by default.

New and enhanced features

• Administrator features
  • Select data center regions for meeting and webinar traffic
    Users on paid accounts can now customize which data center regions they use for their real-time meeting and webinar traffic. You can opt in or out of each specific data center region for data in transit. Your default region, which is the region where your account was provisioned, will be locked. When you opt out of a region, the regional dial-in numbers will be disabled for your meetings and webinars. Zoom Conference Room Connector (CRC) endpoints in disabled regions will also not be able to connect to your meetings or webinars. This setting is available at the account, group, and user level and can be locked at the group or account level. Data routing selections do not apply to Zoom Phone.
  • Additional data center details in Dashboard
    Dashboard will now list if any data center connected to an HTTP Tunnel (HT).
  • Link accounts to an organization
    In IM Management settings, account owners and admins can now link multiple Zoom accounts together to create an organization. Once linked as an organization, these accounts will be able to search contacts, chat, meet, and make phone calls (if eligible for Zoom Phone) with each other.
  • Setting to allow Zoom Room under the same account as host to share
    Account owners and admins can now enable or disable a setting to allow Zoom Rooms to share into the meeting when they’re on the same account as the host.
  • Setting to allow host to report participants to Zoom
    Account owners and admins can now enable a setting to allow the host to report participants to Zoom. This feature will generate a report which will be sent to the Zoom Trust and Safety team to evaluate any misuse of the platform and block a user if necessary. This setting is available at the account, group, and user level and can be locked at the group or account level. This setting requires the Zoom client version which will be released on April 26, 2020. 
  • Setting to show participants’ profile pictures