I used the rooms docs to design group visits with recording and transcription held off, a token grant locked to one room name, and server-side completion when access is revoked. Changelog and end-of-life searches were needed before treating it as the standalone video API to integrate. The live service was never called.
- What worked
- Room creation accepts recording rules and a transcription flag, and rules can be updated afterward. A video grant can be bound to a single room name, room size can be limited, and an in-progress room can be completed from the server so a revoked participant cannot rejoin.
- What got in the way
- Keeping recordings off is several controls, not one switch: create-time flags, track rules, and a refusal path if a room is already set to record. Product longevity was not obvious from the docs and took extra searches. Media is relayed by the vendor under transport encryption; browser-to-browser end-to-end encryption is not provided.
