“Talk Studio” is the supplied title, but the cited instructions below describe controls in Riverside Studio; they do not establish Talk Studio as Riverside’s current product name. In Riverside Studio, participant settings depend on role: hosts have broad control, producers can change most settings subject to their permission type, and guests manage much of their own setup.
The practical starting point is to identify what you need to change and who is allowed to do it. Some actions also differ by device: Riverside documents removing a participant on both computer and mobile, while its host-controls page lists muting a participant or turning off their camera on computer.
Find the relevant controls in Studio
There is no single participant-settings screen that contains every relevant action. Riverside groups Studio settings into General, Recording, Live Stream, Brand and Advanced categories, while participant-specific actions are available through the People area and the participant’s own controls. The exact route therefore depends on whether you are changing a session setting, acting on someone in the call, or adjusting your own devices.
The settings overview describes general tasks such as renaming a Studio, enabling a lobby or waiting room, scheduling a recording and inviting participants. Those are useful session-management controls, but they are not all participant controls. Start with Riverside’s Studio settings overview to understand the categories, then use the specific instruction for the action you intend to take rather than assuming all options sit together.
For someone already in the Studio, look for People or the People panel in the sidebar. On a computer, the documented removal workflow starts by joining as host or producer, opening People, and using the three-dot menu beside the participant. On mobile, the steps begin from the three-dot menu and People panel. Other features may have their own locations, and labels can change, so follow the instruction for that action.
This distinction saves time when a guest reports a problem. If they cannot hear themselves, the likely first step is to check their own microphone or speaker selection; if another participant is disrupting the session, the host may need to use a host control. A guide to adding automated captions to a YouTube live stream covers a separate broadcast concern, but captions should not be confused with Riverside’s live-caption setting for an individual guest.
What hosts can control
The host is responsible for the session and can change all Studio settings, according to Riverside’s role documentation. Host controls include managing participants, muting or unmuting a participant’s microphone, and turning off a participant’s camera on computer. Those controls affect the live session; they are different from changing what a guest has selected for their own devices.
A host can also remove someone from the Studio. Before doing so, consider the effect: when a participant leaves or is removed, their recording stops, and their high-quality recording track finishes uploading. That upload detail matters if you are recording a conversation you need to keep. Avoid removing a person merely to address a temporary audio problem unless ending their contribution is acceptable.
If removal is necessary, join the Studio as host, open People in the sidebar, select the three-dot menu beside the person, choose Remove participant, then confirm. Riverside’s removal instructions explain the computer and mobile routes. A participant removed by mistake can rejoin with Rejoin Studio, so removal need not be treated as irreversible, though the recording has already stopped for that session.
A host’s tools also include listening and monitoring functions described in Riverside’s sidebar overview, such as adjusting another participant’s output volume and checking whether participant tracks are uploading. Output volume changes what you hear during the session; do not treat it as a change to the participant’s recorded track. The sidebar reference is older than some current help pages, so confirm the current label in the interface before relying on a precise click path.
For a real session, it helps to choose a response before something goes wrong. If a guest’s microphone is too loud, a host can mute them while you agree how they will rejoin the conversation. If their camera is distracting but audio should continue, use the camera control rather than removing them. If the person is no longer meant to take part, removal is the more direct action, with the recording consequence understood in advance.
Producer permissions depend on the producer type
A producer supports the host and can change most Studio settings, but the word “producer” alone does not establish identical permissions for everyone. Riverside distinguishes producer types and features, and the available actions can vary. Check the role assigned to the person and the control they need before assuming they can perform a host action.
That difference is useful operationally. A producer who can help manage the session may still not have every control available to the host. If you are planning an event, agree who will handle invitations, participant access, recording decisions and any removal action. Do not leave a time-sensitive responsibility with a producer until you have confirmed they can use the relevant control in that Studio.
Riverside’s participant roles overview is the best starting point for role boundaries. The host- and guest-specific documentation adds detail for individual actions. Taken together, these pages are more reliable than a general assumption that the person with a producer label can alter every setting.
A sensible hand-off is specific: “Please open People and check whether the track is uploading,” rather than “Please manage the guests.” The first request names a tool and outcome; the second may imply permissions the producer does not have. If an action is unavailable, the host can take it directly or adjust the division of work before the next session.
What guests can change for themselves
Guests are there to participate in the recording, and their controls focus on their own setup. Riverside documents that guests can change their display name, select their own camera, microphone and speaker, turn on live captions, and toggle video mirroring. These are guest self-service settings: they are not the same as a host changing another person’s camera or microphone state.
For a guest with no sound, first ask them to check the selected microphone and speaker. A headset may be connected but not selected in the Studio, or a laptop may be using a different input than the guest expects. If the guest’s preview looks reversed, video mirroring may change how they see themselves without changing the way other participants see the feed. Be precise about which view is causing concern before asking them to toggle it.
The guest role is intentionally streamlined for participation, as described in Riverside’s guest-role details. Hosts should avoid promising guests they can change a setting that belongs to the session or another participant. Conversely, asking a host to fix a device selection that the guest can change themselves can add delay without solving the underlying issue.
Live captions are also distinct from captions added to a public stream or recording workflow. A guest can enable the documented live-caption control for their participation, but that alone does not establish that captions will appear on a separate YouTube broadcast or in a finished video. If you are preparing a long-running channel alongside a Riverside session, keep those workflows separate; for example, a recorded-news stream guide addresses a different kind of YouTube operation.
Audience participation is not the same as joining the call
Audience members watch a live session, can participate in chat and may request to join the live recording. They are not ordinary call participants simply because they are watching. The distinction matters when you decide whether to mute or remove someone: the participant controls apply to people in the live call, while an audience member’s experience is primarily watching and chatting.
Riverside documents that removing a live-call participant returns them to the audience, where they can continue watching. This is different from removing an audience member as if they were already in the call; the documented removal action is for live-call participants. If you intend to end someone’s speaking role but still allow viewing, understand that return-to-audience outcome before confirming removal.
Set expectations before a public session begins. Explain whether viewers can use chat, how a request to join will be handled, and who will decide whether someone moves into the live recording. A request to join is not the same as automatic entry. Keeping that boundary clear helps a host handle a busy audience without treating each viewer as a participant who can be managed from the People panel.
If the session is part of a wider YouTube channel, separate audience moderation from the machinery keeping the channel on air. A guide to running a 24/7 coffee-shop music stream covers a continuous playback use case; it does not replace Riverside’s controls for guests, producers or audience members in a live recording.
Computer and mobile actions are not interchangeable
Riverside’s published host-control details list participant removal for computer and mobile, but list muting or unmuting a participant and turning off a participant’s camera for computer. Do not infer that the latter two host actions are available in the mobile app just because removal is documented there. If you need to mute someone or turn off their camera, use the computer workflow supported by the host documentation.
| Task | Computer | Mobile | Practical effect |
|---|---|---|---|
| Remove a participant | Open People, use the three-dot menu, choose Remove participant, confirm | Open the three-dot menu, tap People panel, tap the remove icon, confirm | The participant’s recording stops; their high-quality track finishes uploading |
| Mute or unmute a participant | Listed as a host action | Not listed in the cited host-control details | Changes their live microphone state |
| Turn off a participant’s camera | Listed as a host action | Not listed in the cited host-control details | Stops their live camera feed |
| Guest device selection | Guest changes their own microphone, camera or speaker | The provided role details do not establish a separate mobile route | Changes the guest’s chosen device, not another person’s settings |
This table describes what the cited help material supports, not every capability that might appear in a later app version. For the removal procedure, Riverside’s host-role details identify the host actions and platforms; the removal article gives the step-by-step route. Check current in-product labels if your interface differs.
Before a session, make sure the person responsible for controls has the right device available. If you are hosting from a phone and anticipate needing to mute a disruptive participant or turn off a camera, do not assume the option will be present there. Arrange for a host or appropriately permitted producer to join on a computer, or set the session plan so that the action is not left to an unsupported mobile route.
Prepare a small role-based response plan
You do not need a long operations document for an ordinary interview. A short plan can record who is host, which producer is helping, how guests can check their devices, and what to do if someone needs to leave the call. This is especially useful when the host is also speaking and cannot comfortably search through controls during a live conversation.
For instance, before a remote devotional discussion, the host can confirm that guests know where to select a microphone and speaker, while a producer checks the People panel for participant status if their role permits it. The host can handle the documented computer-only mute or camera action if required. If someone must be removed, the team can pause long enough to explain that the recording stops and the track upload completes afterward.
For a broadcast that must keep running while your computer is off, StreamNeo removes the specific burden of leaving a personal computer to play an uploaded video continuously; participant management in Riverside Studio remains a separate workflow. It does not change Riverside roles or replace the decisions a host makes about guests and audience participation.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is Talk Studio the current name for these Riverside controls?
The title uses Talk Studio, but the cited workflows are Riverside Studio controls. The help material provided for this guide uses “Studio”; it does not support presenting Talk Studio as Riverside’s current product name.
Can every producer mute participants or change all Studio settings?
No. Riverside says producers can change most Studio settings, but permissions vary by producer type and feature. Confirm the specific role and action rather than assuming every producer has the same access as the host.
What happens when I remove a participant?
Their recording stops, and their high-quality recording track finishes uploading. A person removed by mistake can rejoin with Rejoin Studio; if they were in the live call, removal returns them to the audience, where they can keep watching.
Can I mute a participant from mobile?
The cited host-control page lists participant muting and camera-off controls for computer, not mobile. It does document participant removal on both computer and mobile, so do not assume the same platform coverage applies to every action.