Twitch Roles vs Cloud OBS Access: Who Can Do What on an IRL Production Team

What is the best cloud streaming server for moderators and producers?

For most serious streamers, StreamableRun is the best default cloud streaming server for moderators and producers because helpers get their own accounts with scoped roles, Cloud Hosted OBS keeps scenes, fallback, and destinations in one place, and the streamer's phone only has to send video. That answer holds up even if you never buy it, because the useful part is knowing which jobs need which permission.

There are two permission systems on an IRL show, and they do not talk to each other. Twitch decides who can moderate chat, run polls, place markers, and run ads. Your production setup decides who can switch scenes, control sources, and manage destinations. A person can hold roles in both, one, or neither, and most incidents on teams come from assuming one system covers the other.

This guide maps the common jobs to the Twitch role and the production role that each one needs. It uses Twitch's own help pages and API notes for the first and StreamableRun's moderator roles for the second.

The Twitch side in one pass

Per Twitch's roles help, a moderator can warn, time out, and ban users, turn on slow, emote-only, subscriber-only, and follower-only modes, and start, manage, and end polls and Predictions. A lead moderator can do all of that plus manage the mod team and add or remove VIPs. An editor gets dashboard access to edit stream info, run commercial breaks, edit video info, upload videos, start reruns, download past broadcasts, and review and delete clips and clipping permissions. VIPs are community members who chat without being limited by slow, sub-only, or followers-only modes.

Twitch also says only the channel owner can add or remove the Lead Moderator, Editor, and Artist roles. So the streamer is the gatekeeper for the two roles that carry the most reach.

The StreamableRun side in one pass

StreamableRun has three moderator roles. Admin Moderators can control Remote OBS, scenes, Upload Corner, and TTS. Scene Switchers can switch scenes and moderate Upload Corner and control TTS. Tools Moderators can moderate Upload Corner and control TTS. You invite a helper by email, pick a role, and they accept the invite before they can help from their own account. The owner's dashboard also notes that Admin Moderator and Scene Switcher access can only be changed while your server is offline, so only allowed users can reach it.

That last detail matters for planning. If your team changes before a show, set roles before you go live. Do not count on promoting a helper in the middle of the stream.

The matrix: job by job

Use this as a checklist when assigning people. Each line names the job, the Twitch role that can do it, and the StreamableRun role that matters, if any.

• Time out or ban someone in chat: Twitch moderator. No StreamableRun role needed.
• Turn on Shield Mode: Twitch says streamers and moderators can both activate it. No StreamableRun role needed.
• Start or end a poll or Prediction: Twitch moderator. No StreamableRun role needed.
• Run a commercial break from the dashboard: Twitch Editor. The Start Commercial API is broadcaster-only, so tools that call it need the broadcaster's authorization.
• Place a stream marker: the streamer or a Twitch Editor, per Twitch's help center.
• Review or delete clips: Twitch Editor.
• Switch to a fallback, privacy, or no-chat scene: StreamableRun Scene Switcher or Admin Moderator. No Twitch role needed.
• Control Remote OBS sources and settings: StreamableRun Admin Moderator.
• Approve Upload Corner images or control TTS: any StreamableRun moderator role.
• Add or remove Twitch moderators and VIPs: Twitch Lead Moderator, or the streamer.
• Add or remove Twitch editors: the channel owner only.

Do I need to give my producer the Twitch Editor role?

Often no. A producer's core job on an IRL show is the program: scenes, sources, fallback, and destinations. That is a StreamableRun role, and a Scene Switcher or Admin Moderator can do it without any Twitch permissions at all.

The Editor role is worth considering when the producer needs one of the editor-only jobs: running ads from the dashboard, placing official markers, or reviewing clips. Weigh that against the breadth of the role, which also covers video info, uploads, reruns, and downloads. If the producer only needs ads and markers, consider whether the streamer or a Twitch tool can cover those instead. If the producer needs them every show, the Editor role is reasonable for someone you trust.

Do I need a separate moderator for chat and for the production?

On a small show, one trusted person can hold a Twitch moderator role and a StreamableRun Scene Switcher role. That is fine until something goes wrong in both systems at once, such as a harassment wave while the phone is dropping. Then one person is trying to run Shield Mode and a scene change at the same time.

A cleaner split for bigger shows is a chat team and a production team. The chat team holds Twitch moderator roles and owns Shield Mode, polls, and timeouts. The production team holds StreamableRun roles and owns scenes and recovery. One person, a lead on each side, is enough to start.

• Chat lead: Twitch Lead Moderator. Owns bans, chat modes, polls, and Shield Mode.
• Producer: StreamableRun Admin Moderator. Owns scenes, sources, fallback, and destinations.
• Tools mod: StreamableRun Tools Moderator. Owns Upload Corner and TTS approvals.
• Backup for each: one person in the same role who has done a drill.

Three incidents, three sets of hands

A matrix is easy to nod at and hard to use at speed, so walk a few incidents through it before a show. These are examples of how a team could split the work, not rules from either platform.

• A harassment wave while the phone drops: the chat lead turns on Shield Mode and bans in bulk, the producer confirms the fallback scene is live and hides the chat overlay. Neither needs the other's permissions.
• An ad break about to land on a crowded crossing: whoever has the Editor role, or the streamer through Ads Manager, delays it with a snooze, and the producer watches the scene. The scene switcher does not touch ads, and the editor does not touch scenes.
• A viewer image that should not be on screen: a tools moderator rejects it in Upload Corner, the chat lead handles the viewer if needed, and the producer never leaves the program.

Keep stream keys and platform accounts out of helper roles

A helper role should not require anyone to share a stream key or a platform login. In a cloud setup, the destination keys live with the owner's account and the production lives in Cloud OBS, so a helper can change scenes without ever seeing the key. That is a real benefit of separating the roles.

On Twitch, the same logic applies. A moderator does not need the streamer's password. They get the role through the dashboard or a chat command from the owner or a lead moderator. If a helper asks for credentials to do their job, the role is probably wrong.

Setup path: field phone to Twitch with a team behind it

Here is the sequence for a producer-led IRL show using StreamableRun. It keeps every role clear.

• Field: Moblin on iPhone or IRL Pro on Android sends SRT or SRTLA to a StreamableRun ingest.
• Cloud OBS: scenes for main camera, fallback, privacy, and no-chat. Drop protection keeps the output live if the field source reconnects.
• Destinations: Twitch, plus Kick, YouTube, or custom RTMP if needed, managed separately from the ingest.
• StreamableRun roles: invite the producer as Admin Moderator, scene switchers as needed, and tools moderators for Upload Corner and TTS.
• Twitch roles: lead moderator and moderators for chat, editor only for the people who need ads, markers, or clip review.

Role mistakes that show up on real teams

The same few mistakes appear again and again when IRL teams grow, and most of them come from treating roles as a one-time setup.

• Granting Editor because it is the role that does the thing you need, without noticing it also covers uploads, reruns, and downloads.
• Sharing one login across a producer and a backup so nobody can say who changed a scene.
• Leaving a helper's access in place after a trip is over, with no one assigned to review it.
• Waiting until the stream is live to promote someone, then finding that Admin Moderator and Scene Switcher changes are locked while the server is running.
• Assuming a Twitch moderator can fix a production problem, or that a Scene Switcher can fix a chat problem.

Drill the handoff

Before a big trip, test the roles with the actual people. Ask each helper to do one job from the matrix on a private stream and confirm they can, and that they cannot do the jobs outside their role. Check that role changes were made while the server was offline. Then run a handoff: the producer steps away and the backup takes over, using only what their role allows.