POKA Documentation
Rooms and Access Control
Control who enters a Drop room, how access is approved, and how active sessions are governed.
Overview
Secure, room-based peer transfer for fast handoffs and controlled access.
- Room access starts with a short code and a join validation sequence.
- Approval-aware mode allows hosts to explicitly accept or reject participants.
- Session token checks help validate eligible connectivity paths, including TURN where needed.
- Participant states can be tracked as pending, approved, active, or removed.
- Access control helps prevent unintended recipients from entering active transfer sessions.
- Room controls are designed for operational teams handling external collaborators.
- Audit-oriented security events support abuse-control and anomaly monitoring.
Step-by-step Flow
- 1Create a new room and assign one host responsible for access decisions.
- 2Share the room code through a trusted channel with expected participants.
- 3Enable approval flow when participants are external or transfer data is sensitive.
- 4Review each join request and approve only recognized users.
- 5Monitor active participant list while transfer session is running.
- 6Remove or block unexpected participants immediately if access looks suspicious.
- 7Close room access once required recipients are inside and transfer begins.
- 8End session and archive room context when exchange is completed.
Limits
Operational Constraints
- Users without valid room code and approval cannot enter restricted sessions.
- Repeated failed joins may trigger abuse-protection throttling.
- Approval workflows depend on host response time and can delay urgent handoffs.
- Session continuity can be impacted by unstable network or browser state resets.
- Room-code sharing outside trusted channels increases unauthorized-access risk.
- Access control events improve visibility but do not replace internal security policy.
Notes
Recommended Practices
- Media agencies: Enable approval mode when sharing with external vendors or client-side freelancers.
- Freelancers: Set yourself as room owner so join approvals stay quick and consistent.
- Production houses: Rotate room by shift or unit when many collaborators are involved.
- Security-conscious teams: Close inactive rooms quickly to reduce accidental re-entry.
Workflow Diagram
Room Access Decision Flow
Create Room->
Share Code->
Join Request->
Approve or Reject->
Active Session->
Close Room