Use a short-lived, room-scoped participant token minted by your server. Keep room creation, role selection, and cursor permissions behind an authenticated Express endpoint. Let the browser carry media and cursor traffic, but never let it choose its own claims.
Short answer: create the room in your application database, derive permissions from the signed-in user and course enrollment, then issue a token that names one room, one participant, and an expiry of minutes rather than days. The media service or WebRTC gateway verifies that token. Your editor still treats cursor updates as untrusted input.
Decision note: which trust boundary fits a one-person SaaS?
Boundary Token issued by Browser can influence Best fit Main cost
Application server Your API after session and enrollment checks Display name and device metadata only Classroom rooms tied to an existing account You own key rotation and audit trails
Dedicated identity service A separate authorization component A narrowly defined scope request Multiple…