Use room-scoped, expiring tokens when a media editor must keep collaborative cursors accurate after membership changes; reserve a shared join link for sessions where possession of the URL is intentionally enough to enter. TL;DR: the decisive constraint is not connection setup. It is whether the server must distinguish one participant, device, role, and expiry from another while a video call and editor presence share a room.
A link is wonderfully cheap in developer attention. Paste, click, join. But once everyone presents the same secret, the authorization layer has little evidence for explaining who is still allowed to publish presence. A token adds an issuance step and validation code, yet it gives the room boundary explicit inputs.
This is a lifecycle problem. WebRTC defines browser-side real-time connection APIs, but an application still has to arrange signaling and decide who may join its session.…