Understand QCMM Meeting Room Security, Credentials, and Recording Boundaries

Understand QCMM Meeting Room security: server-side authorization, short-lived credentials, explicit media controls, and the current no-recording boundary.

Access Is Authorized by QCMM

QCMM verifies the authenticated user, booking or Host authority, Meeting Time, provider, lifecycle state, and Meeting Room entitlement before issuing realtime access. Legacy direct Meeting Room menu entry is retired; Meetings open from protected booking/Host access paths.

Credentials Are Short-Lived and Room-Scoped

The browser receives a short-lived realtime participant credential only after server-side authorization. QCMM also uses Joomla request-token protection for state-changing room actions. Credentials and internal room identifiers should never be copied into documentation, screenshots, or public posts.

Media Is Explicit

Camera, microphone, and screen sharing are transmitted only when the participant enables them and the browser grants permission. QCMM also applies role/participant permissions in the realtime room. Screen sharing is visual content only in the current QCMM interface; computer or tab audio is not included.

Recording Boundary

QCMM 2.0.21 does not expose a QCMM Meeting recording workflow or recording controls. The bundled realtime client library contains general media capabilities, but those library capabilities are not themselves QCMM product features. Do not document Meeting recording as available unless a later QCMM implementation explicitly adds it.

Security Checklist

  • Use HTTPS and current browsers.
  • Enter through QCMM booking/Host links.
  • Keep credentials and access references private.
  • Treat browser permissions as separate from QCMM authorization.
  • End the Meeting from Host controls when the session is finished.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.