Realtime Room Admission Control Using Scoped Tokens and Client Trust Signals

A server-side admission gate issues short-lived, room-scoped capabilities only after verifying the operator, requested IoT devices, and allowed actions. Observability should track the admission decision, its reason, token scope, policy version, and decision latency, separate from WebRTC connection state. Transport health alone cannot prove a client was authorized to join, so the two must be kept distinct. Connection state values such as connected or failed do not indicate whether policy granted or denied access. Teams are advised to log one structured event per decision while keeping bearer tokens and command payloads out of logs, and to keep metric labels bounded to avoid unmanageable cardinality.