Shared Chat joins participating communities during a collaboration, but it does not erase channel ownership. Twitch documents that a ban can prevent participation during the shared session while its lasting channel effect remains tied to the channel that applied it. Agree on escalation and review lasting actions after the session.
Permanent follow-up reflects the channel's own decision rather than an assumption about session-wide behavior.
In this guide
Before you start
- The participating channel owners and their existing moderation teams.
- A planned collaborative session with Shared Chat available.
- A private coordination channel for moderation decisions.
Identify the result you need
Begin with the collaboration's purpose and the communities involved. A moderator may recognize regular viewers from one channel while encountering others for the first time. Agree on the behaviors that require immediate action and who makes ambiguous channel-specific decisions.
Shared Chat, Shared Viewership and a shared broadcast picture are distinct features. Twitch's shared-viewership documentation ties the combined audience presentation to a genuine collaboration using Stream Together and Shared Chat; it does not turn every channel's earnings or progress metrics into one pooled account.
Work through the setup
Confirm the owner controls
Have the participating broadcasters use the supported Shared Chat entry point, including the /sharedchat command where appropriate. Confirm the intended collaborators rather than sharing account access.
Look for: The collaboration uses each channel's actual permissions and identity.
Brief moderators on scope
Explain which actions affect the active session and which channel retains the lasting action. Agree who communicates a serious incident to the other channel owners.
Look for: Moderators can act promptly without assuming every decision becomes a permanent ban everywhere.
Observe ordinary messages
During a planned rehearsal or opening segment, check that channel-origin cues are clear and that the team can identify its own community's context.
Look for: The shared conversation is understandable without moderators guessing where a message originated.
Review after the session
Check any important moderation action with the relevant channel owner. Make a separate, explicit channel decision if continued restriction is warranted.
Look for: Permanent follow-up reflects the channel's own decision rather than an assumption about session-wide behavior.
Check the actual result
Do not test moderation by surprising a real viewer with a ban. Use ordinary message flow and the platform's documented permissions to verify the workflow. If the team needs a rehearsal involving a test account, make it explicit and controlled.
Keep a small incident note with the time, action and responsible channel. Avoid exporting whole chat histories into a public document. The goal is enough context for a consistent response, not a second database of community members.
Make the next session predictable
At the end, confirm that the shared session has ended as intended and tell viewers where the conversation will continue. A collaborator leaving video and a community leaving Shared Chat can be different events in the production.
Review shared-viewership numbers in the context documented by Twitch. Do not present a combined collaboration audience as proof that an individual channel met a separate monetization or programme threshold.
Still stuck?
A helper cannot start Shared Chat
Check the broadcaster-level access for the supported command or control. Do not hand out an account password to solve a role mismatch.
A viewer returns after the collaboration
Review which channel applied the lasting action and the session's scope. Make any further channel restriction explicitly through its owner or authorized moderators.
Combined viewership differs from channel metrics
Use Twitch's Shared Viewership definitions. Collaboration presentation and individual channel metrics are not interchangeable.
Sources & references
Documentary review of current first-party help pages and indexed first-party excerpts, checked November 4, 2026. The diagnostic sequence and rehearsal examples are original editorial guidance; Foxdip did not operate a private account, run these broadcasts or measure performance. Expected results are checks for the reader to perform, not claimed test results.
- Twitch — Shared Chat ↗Checked 2026-11-04
- Twitch — Chat Commands ↗Checked 2026-11-04
- Twitch — Shared Viewership ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗