Veeting Rooms 6.11.47 – October 2026

Veeting Corporate: Moderated Chat

White-label administrators can now switch on chat moderation for their meetings. A participant's chat message no longer goes straight to the room: it is held until a moderator approves or rejects it, and while it waits it is visible only to its author and to those who may moderate. For example, in a webinar or a public briefing, an audience question can be reviewed before the room sees it.

Moderating is a permission of its own, assigned by an account administrator and held by the organizer by default. A moderator's own messages are approved automatically, so an announcement from the chair is never delayed, and speaker messages can optionally be auto-approved for panel formats.

A companion option hides who wrote which chat message. Ordinary participants appear as "Anonymous" to everyone except those who may moderate chat, while anyone who held the chat-moderation permission when they sent a message keeps their name.

Both options are off by default and are enabled per white-label instance. A change takes effect in meetings that are already running.

Veeting Corporate: Room-Control Systems

A room-control system, such as Q-SYS and similar wall panels, can now control a running Veeting meeting with API calls. A control script can activate a collaboration tool, page through the shared presentation, assign tools and participants to specific screens, lock the room, clear the chat, stop a screen share, switch presentation mode, end a scheduled meeting and read back the current state so the panel can light its own buttons. The room system controls are off by default and can be enabled per white-label instance.

Room screens now also keep themselves up to date. A display marked as unattended in its address, whether a room screen in TV mode or any other screen given the new autoApplyUpdates setting, updates itself.

Veeting Rooms: Closing the Current Meeting of a Recurring Series

A recurring meeting can now be closed early. The list of upcoming meetings now offers "Close meeting" for recurring meetings as well. Closing ends only the meeting in progress and frees the room; later meetings in the series are not affected.

Veeting Rooms: Account Defaults for the Meeting Password

Two new account settings control the meeting password for newly scheduled meetings. "Add the meeting password to the meeting link by default" lets invitees join with one click, without typing the password. "Hide the meeting password in email invitations by default" leaves the password out of the invitation email and the calendar file. The scheduling form starts from the account setting, and the organizer can still change it for each meeting. Existing meetings are not changed.

An organizer's explicit choice of no registration form is now kept even when the account defines a default form. Previously, the account default silently replaced it.

Veeting Rooms: Backstage TV Link

The meeting summary now offers a backstage TV link. A TV screen opened with this link can enter the room up to 60 minutes before the start and shows the stage while the webinar countdown is still running. It has no other rights: it is neither a moderator nor a speaker, and it never receives chat messages that are awaiting moderation.

Veeting Rooms: Early Access for Interpreters, and the Lobby

In meetings with language channels, interpreters who join with their interpreter link can now enter up to 60 minutes before the start, like moderators and classroom speakers. Everyone else can enter 15 minutes before the start. Moderators can manage the lobby from 60 minutes before the start. A participant who arrives too early sees when the meeting starts, and the page reloads automatically.

Veeting Partners: New Chat Webhooks and Chat Contributions APIs

Two new events, onChatMessageCreated and onChatMessageModerated, let an external system follow a meeting's chat and its moderation decisions. Both can be subscribed to from the account and white-label settings pages.

A new Contributions API-key scope lets an external system add chat messages to a meeting without being given access to the administrative meetings API. It is granted from the API-key editor at white-label level, so an integration can post into chat on the narrowest possible permission.

Pages that embed a Veeting meeting now receive the moderation state of each chat message and a separate event for every moderation decision, so an integration can tell a held message from a released one and follow decisions as they are made.

Veeting Partners: New Customer Hostnames Must Use a CNAME

New and changed customer hostnames must now be set up as a CNAME. Hostnames already in service continue to work unchanged.

Veeting Partners: Stricter TLS Requirements

The set of accepted TLS cipher suites has been narrowed. Veeting now negotiates only modern suites that offer forward secrecy and authenticated encryption. Current browsers and operating systems are unaffected.

Fixes and Improvements

• Recurring meetings that run past midnight (UTC) now stay open until they end.
• The meeting room, its lobby and the in-room functions now stay available until the meeting's actual end, including its last minute. Previously the lobby stopped being availabel during the last 60 seconds of the meeting.
• Breakout rooms now move with their meeting when it is rescheduled.
• Simplex Editor: partially recorded meetings are now transferred as well, with slides and video aligned on a common timeline