To give someone access to Streamlabs live-stream tools, invite them through the Streamlabs Dashboard’s Shared Access settings and choose the role or permissions they need. This is separate from making that person a moderator in YouTube, Twitch or another platform’s chat; one grant does not make the other.
The practical sequence is to decide what tasks the person will handle, add them under Account Settings > Shared Access, select an appropriate access level and send the invitation privately. Streamlabs says its invitation expires after 72 hours, so the invitee should accept it promptly.
Choose the access the person needs
Start with the task, not the title “moderator”. A person who removes spam in chat may only need a platform chat role. Someone who will manage Streamlabs alerts or Media Share needs access to the relevant Streamlabs tools as well. A trusted helper may need both, but you must grant each separately.
Think through a normal shift. Will the helper skip an alert that is stuck, review a Media Share request, or adjust a Cloudbot setting? Or will they only time out a viewer in YouTube chat? Naming the actual tasks helps you avoid giving broad account access when a narrower permission will do.
For example, if a volunteer is helping with a devotional stream overnight, you might need them to review song requests and handle chat disruption. The platform role addresses chat moderation; Streamlabs Shared Access addresses the dashboard tools they need. Neither should be assumed to include the other.
It can help to write down the boundary before inviting someone: “Can review incoming requests and skip an alert; cannot change account credentials or manage other users.” Keep the boundary specific enough that you can tell whether the person needs a Streamlabs role, platform role, or both. Revisit it if their duties change.
If you are configuring the wider channel rather than permissions alone, a 24/7 ambient YouTube stream setup guide can help you think about the operational tasks that continue while you are away. It does not change the access rules: identify each tool and assign the relevant permission directly.
Understand Shared Access roles
Streamlabs documents three Shared Access choices: Moderator, Administrator and Custom. The names describe access within Streamlabs, not a chat status on YouTube or Twitch. Streamlabs’s Shared Access instructions describe the Moderator role as providing Dashboard access and the ability to skip or repeat alerts, control Media Share and access Cloudbot.
Administrator access is substantially broader. Streamlabs says this role includes platform access tokens and stream keys, while donation settings and Shared Access settings are excluded. The same support article says shared users cannot see the settings page. Treat those details as Streamlabs’s documented role behaviour, not as a permanent promise that every screen will remain unchanged. Check the current vendor guidance before granting a role, especially if the account contains sensitive credentials.
Custom is for a narrower or unusual combination of tasks. Rather than choosing it because it sounds safer, inspect the available permission boxes and select only what the person needs. If the required permissions are not clear, pause and check Streamlabs’s current documentation instead of guessing.
| Choice | What to consider | Typical fit |
|---|---|---|
| Moderator | Streamlabs documents dashboard tools for alerts, Media Share and Cloudbot | A trusted helper who needs those moderation tools |
| Custom | Select the specific permissions needed for the assigned tasks | A helper whose duties are narrower or do not match the preset |
| Administrator | Much broader account access, including platform tokens and stream keys according to Streamlabs | Only someone who genuinely needs broad control and is trusted with sensitive access |
Use the least access that still lets the person complete the work. A person who only handles chat should not receive Administrator access just because they are called a moderator. A person who needs Streamlabs tools may still not need access to credentials or broader account controls.
Keep platform roles separate
A platform moderator role grants authority in that platform’s chat. Streamlabs Shared Access grants access to Streamlabs dashboard features. If your helper needs both, configure both. Streamlabs’s Twitch moderator guide describes Twitch’s Roles Manager and the /mod USER chat command as ways to assign Twitch moderation; it discusses Shared Access separately for dashboard permissions.
Do not confuse a human moderator with Cloudbot authorization. Cloudbot is Streamlabs’s bot, and it needs its own permission to act in a platform’s chat. Streamlabs’s Cloudbot setup guide describes different authorization steps by platform, including YouTube Studio’s Community settings for adding Streamlabs as a moderator. Authorizing the bot does not invite a human to your dashboard.
Likewise, Cloudbot command settings can determine which chat roles may use particular commands. Those settings affect bot behaviour, not the permissions granted to a human through Shared Access. Keep the three jobs distinct in your checklist: platform role for chat, Cloudbot authorization for the bot, and Shared Access for Streamlabs tools.
This distinction matters when diagnosing a missing control. If the helper can access Streamlabs but cannot moderate YouTube chat, check the platform’s role assignment. If Cloudbot is not acting in chat, check its authorization and relevant bot settings. Adding more Shared Access permissions will not solve either issue by itself.
Open Shared Access in Streamlabs
Sign in to Streamlabs.com with the account that owns or controls the Streamlabs dashboard. Open the Dashboard, go to Account Settings, then select Shared Access. The account owner should perform this step, because the invitation and its permissions determine what another person can do.
The menu labels and layout can change, so if you do not see the same route, consult Streamlabs’s current Shared Access support article rather than using a similarly named chat or bot setting. Check that you are in the account intended for the channel. If you manage more than one channel or login, inviting someone from the wrong account can grant access to the wrong set of tools.
Before selecting Add User, decide which email or account the invitee will use and confirm it with them. This prevents a common handover problem: the link goes to one person, but they try to accept it while signed into another account. Agree on the account first, then send the invitation through a private channel.
A clear preparation step is to record the helper’s name, the tasks they will cover and the date you plan to review access. You do not need a complicated policy. A short note can remind you why a permission was granted when the volunteer’s duties change or the channel’s schedule is reorganised.
Add a moderator or custom user
From Shared Access, select Add User. Streamlabs presents role choices including Moderator, Administrator and Custom. Choose the option that matches the work you identified, rather than treating the word “moderator” as a substitute for deciding what dashboard access is needed.
For a person handling alerts, Media Share or Cloudbot, review the documented Moderator scope and confirm that it suits the task. For a narrower job, choose Custom and select the specific permissions that are relevant. Use Administrator only if the helper needs its broader access, including the sensitive items Streamlabs says that role can expose.
Confirm the invitation in the dashboard and make sure the person you intended is the recipient. Do not paste the generated invite link into a public chat, a community post or a group where unintended people could use it. Send it directly to the named person, and let them know which account they should use to accept it.
For a continuous channel, the handover can be as simple as saying: “Please use the account we agreed, accept the Streamlabs invite, and tell me once you can see the dashboard tools needed for the overnight shift.” Avoid sending passwords or stream keys in the same message as the invitation. Access should be granted through the intended account workflow, not by sharing the owner’s login.
Assign only the needed permissions
Custom access is useful when the person’s duties are specific. Work backwards from the task list: if they only need to skip or repeat alerts, do not add unrelated controls simply because they are available. If they need to manage a Cloudbot function, check which particular permission covers it in the current interface rather than assuming all bot controls are interchangeable.
Media Share is a useful example of why the task matters. Streamlabs says a trusted person needs at least Moderator rights for Media Share. The owner can review pending requests in the Dashboard’s Recent Events queue; whether requests are shown automatically or held for review affects how much oversight is needed. See Streamlabs’s Media Sharing setup guidance for its current workflow.
If you want a helper to review requests before they appear on stream, agree what they should approve and what they should leave for you. Access does not settle the editorial decision. For a music or ambience channel, a request might be technically available but still unsuitable for the channel’s purpose; the moderation process should make that distinction explicit.
Consider the sensitivity of each role, not just convenience. Streamlabs documents that Administrator includes platform tokens and stream keys, so limit that role to someone who needs that breadth and understands how to protect access. When the work ends, or a volunteer leaves, return to Shared Access and remove their access rather than relying on an old invite being forgotten.
If the helper is also responsible for the continuous video itself, keep tool access separate from playback reliability. For example, a guide to preventing black frames between looped videos addresses the stream’s visual continuity, while Shared Access determines who can manage selected Streamlabs functions. Permissions do not fix a faulty playlist or a source that stops playing.
Send and accept the invitation
After you confirm the role and permissions, Streamlabs generates an invitation link. Send it directly to the trusted invitee. Include a brief note identifying the channel and the account they should use, but do not include credentials or share the link where anyone else can take it.
The invitee accepts the invitation using the link and then accesses the shared account from their own Shared Access area. Streamlabs describes the acceptance path as selecting Accept Invite, then using View My Access or their Dashboard’s Shared Access page to choose Access Account. The invitee should confirm that they are signed into the intended account before accepting.
Once they have access, ask them to verify only the tools they need for the task. If they cannot see a particular tool, check whether the permission was selected and whether they have entered the shared account, rather than sending the owner’s login details. If chat moderation is also part of the job, verify the platform role separately in that platform’s own settings.
For Cloudbot, the helper’s dashboard access is still distinct from the bot’s channel authorisation. If the bot must perform chat actions, ensure the bot itself has the appropriate platform access; Streamlabs documents platform-specific steps. A human’s Shared Access invitation does not authorise Cloudbot, and Cloudbot’s authorisation does not grant the human dashboard access.
Handle the invite link and expiry
Streamlabs currently documents that a Shared Access invitation link expires after 72 hours. That is the relevant timing to plan around: tell the person when to expect the link, send it when they are available to accept, and ask them to let you know if it has expired. Do not assume an old link remains valid.
If the invitation expires, return to Shared Access and follow the current dashboard process to invite the person again. Avoid trying to reuse a stale link or forwarding it through several people. The invitation is intended for the named, trusted invitee, so resend it privately and confirm that they accept using the agreed account.
After acceptance, access is not a one-time decision. Streamlabs says the owner can return to Shared Access to edit permissions or revoke access. Review the list when someone’s responsibilities change, when a temporary cover period ends, or when you no longer work with that person. A permission that was sensible during a particular event may not be needed afterwards.
A simple review can ask three questions: does the person still need access, do they still need the same tools, and is their platform chat role still appropriate? Answer each in the system where it was granted. Removing Shared Access does not necessarily change a platform’s chat role, just as removing a chat role does not necessarily remove dashboard access.
If your own stream uses a fixed video loop, keep the operational handover equally clear. A playlist-order troubleshooting guide covers a playback issue, not account permissions, but it illustrates why written responsibilities matter: a helper should know whether they are expected to monitor tools, the video source, chat, or some combination.
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
Does Streamlabs Shared Access make someone a YouTube chat moderator?
No. Shared Access grants access to selected Streamlabs dashboard features. Assign a YouTube chat role separately through YouTube’s current channel and community settings, and verify that role there.
If I make someone a Twitch moderator, can they use my Streamlabs tools?
Not by virtue of the Twitch role alone. If they need Streamlabs dashboard tools, invite them through Shared Access and select the appropriate permissions as a separate step.
How long does the Streamlabs invitation link last?
Streamlabs’s current Shared Access support article says the invitation expires after 72 hours. If the person does not accept in time, create or send a fresh invitation using the current dashboard workflow.
Can I change or remove access later?
Streamlabs says the owner can return to Shared Access to edit permissions or revoke access. Review any separate platform chat role as well, because changing dashboard access does not itself manage platform moderation status.