Host Controls
Host controls decide who can enter, who can stay, and what attendees are allowed to do while the meeting is live. The safest pattern is to define policy before the meeting, then use host controls for live exceptions instead of improvising policy in the room.
┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/room/launch-review │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Meeting room controls │
│ │
│ [ Mic ] [ Camera ] [ Share ] [ Chat ] [ Participants ] │
│ [ Notes ] [ Captions ] [ Record ] [ More ] │
│ │
│ Stage │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Presenter: Maya Chen │ │
│ │ Shared screen: Launch checklist and open blockers │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Side panels │
│ - Participants waiting: 2 │
│ - Raised hands: 1 │
│ - Summary capture: active │
│ │
└──────────────────────────────────────────────────────────────────────┘
Hosts need access to admission, role changes, and collaboration permissions without losing sight of the meeting.
┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/security/permissions │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Artifact permissions │
│ │
│ Applies to: recap, transcript, recording, shared files │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Audience Members of Product and selected guests │ │
│ │ External share Disabled by default │ │
│ │ Link access Sign-in required │ │
│ │ Retention 180 days for recordings │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Exceptions │
│ - Hosts can grant per-meeting access │
│ - Admins can enforce stricter workspace defaults │
│ │
└──────────────────────────────────────────────────────────────────────┘
Meeting entry, moderation, and artifact visibility should be treated as related but distinct control surfaces.
What hosts control
Section titled “What hosts control”- Meeting access mode and waiting room behavior.
- Admission and denial for queued participants.
- Role changes such as host, co-host, participant, or guest.
- Collaboration permissions for microphone, camera, chat, and screen sharing.
- Meeting end behavior and certain recap-sharing actions.
Recommended workflow
Section titled “Recommended workflow”- Set the expected access model before the invite goes out.
- Add a co-host for larger or externally facing meetings.
- Keep People open during the first minutes if the waiting room will be active.
- Use per-participant restrictions only when the meeting needs a live exception.
Troubleshooting
Section titled “Troubleshooting”Too many people are waiting and admission is chaotic
Section titled “Too many people are waiting and admission is chaotic”- Add or confirm a co-host before continuing the presentation.
- Admit in batches only when the audience has already been vetted.
- Tighten the next meeting’s invite and access policy so the live room is not doing all the identity work.
An attendee should stay in the meeting but not keep interrupting
Section titled “An attendee should stay in the meeting but not keep interrupting”- Change that participant’s chat, microphone, camera, or sharing permissions instead of removing them immediately.
- Record the incident in the recap or support workflow if the meeting is sensitive or customer-facing.