Use a short-lived, signed capability for room admission, then enforce every media and moderation action on the server. Do not treat a token as a promise that a permission update reached every participant.
Choice Validation path Revocation behavior Fan-out consequence
Signed capability Local signature and claim checks Usually valid until expiry No authorization-store dependency at join; changes still need a control path
Opaque session ID Lookup on each admission or action Immediate when the shared record changes Strong consistency depends on the store and its availability
Backend proxy for every action Application server decides inline Immediate at the decision point Simplest policy authority, but every operation crosses that service
Recommendation: mint a signed room token on the application server, keep its lifetime deliberately short, and use an ordered server-side control stream for changes after admission.…