Skip to content
StreamerCatalyst Docs

Authentication & permissions

StreamerCatalyst connects to your channel through your Twitch account. This page explains what you approve when you sign in, which permissions are asked for later and why, how StreamerCatalyst hears about things happening on your channel, and who can do what in your dashboard. For each module’s exact list of permissions and Twitch events, see Permissions by module.

Signing in

Section titled “Signing in”
  1. Go to streamercatalyst.com and click Connect with Twitch.
  2. Twitch shows the permissions StreamerCatalyst is asking for. Approve them.
  3. You land in your dashboard.
  • Twitch handles the login. You sign in on Twitch’s own page, and StreamerCatalyst never sees your Twitch password. StreamerCatalyst will never ask you for it.
  • One connection for everything. Every module shares the same Twitch connection, so you only sign in once.
  • Sessions last up to 7 days. Your session is kept in a secure cookie that the page’s scripts can’t read. After 7 days, sign in again. Sign out is at the bottom of the sidebar.
  • Changing your Twitch username breaks nothing. StreamerCatalyst identifies you by your Twitch account ID, not your username, and picks up the new name automatically. You don’t need to reconnect. Public links built from your username, such as your tip page, switch to the new name, so replace any old link you’ve posted.

Your Twitch account’s email address comes with the sign-in. StreamerCatalyst stores it encrypted and uses it for account, billing and service emails.

Twitch permissions (scopes)

Section titled “Twitch permissions (scopes)”

Twitch calls each permission a scope. StreamerCatalyst asks for them in two groups.

Baseline scopes, at sign-in. These let every module read and react to your channel: chat, subs, bits, follows, Channel Points redemptions, polls, predictions, Hype Trains, goals, charity campaigns, your ad schedule, your moderation settings and history, and so on. They also let the bot post in your chat and send native shoutouts and chat announcements.

On-demand scopes, when you set up the feature that needs them. Permissions that let StreamerCatalyst change something on your channel are left off the sign-in screen. They’re asked for the first time you set up the feature that uses them, so a feature you never use never gets the permission.

Scope Asked for when you…
channel:manage:redemptions save an Events rule with the Channel Points trigger, so StreamerCatalyst can create and fulfil the reward
channel:manage:vips turn on Enable VIP commands in chat (Modomation → User Management), so it can add and remove VIPs
moderator:manage:automod turn on AutoMod capture (Modomation → AutoMod Suggestions), so it can act on held messages
channel:manage:ads turn on Snooze ads on raid (Modomation → Channel Events)
channel:manage:broadcast save Chatters’ Built-in commands with !game or !title switched on, so chat can change your category and title (the card also shows a Grant button while it’s missing)
clips:edit turn on Chatters’ !clip built-in command and save, so chat can create clips of your stream (the row also shows a Grant button while it’s missing)

Here’s what happens when a feature needs an on-demand scope:

  1. You save the setting as usual. It’s stored first.
  2. You’re taken to Twitch to approve the one extra permission.
  3. You come back to the page you were on.

If you decline on Twitch, your setting stays saved, but the feature can’t act until you grant the permission.

Only the broadcaster can grant a permission. If a moderator saves a setting that needs one, they see “The broadcaster has to authorize one more Twitch permission before this can run”. A moderator who signs in again only changes the permissions on their own Twitch account, not the channel’s.

Signing in again never drops a permission you’ve already granted. Each sign-in asks for the baseline set plus every on-demand scope your channel already holds.

The full list of scopes, with the reason for each, is in the Privacy Policy and on each module’s permission page.

Missing a permission?

Section titled “Missing a permission?”

If your connection is missing a baseline scope, the Dashboard and Settings show “Missing N Twitch scope(s) — some features may not work” with a Re-authorize link. Clicking it takes you back through Twitch’s approval screen. This usually happens when StreamerCatalyst starts needing a permission your existing connection didn’t include. As with on-demand scopes, only the broadcaster can fix it.

Twitch events (EventSub)

Section titled “Twitch events (EventSub)”

StreamerCatalyst learns what’s happening on your channel through Twitch EventSub: Twitch sends a notification for each follow, sub, cheer, raid, redemption, chat message, stream start and so on. Each notification is checked to be genuinely from Twitch before any module uses it.

You never set this up yourself. StreamerCatalyst subscribes to the events your plan’s modules need, plus the ones your features need once you set them up. For example, a redemption rule adds that reward’s redemptions. It creates, checks and repairs these subscriptions automatically: when you sign in, when your plan changes, when you turn a feature on or off, and in regular background checks.

To see them, open Settings → Modules and click Health on any module. It lists:

  • OAuth Scopes: ✓ granted, ✗ missing, or “granted when you set this up” for an on-demand scope you haven’t needed yet.
  • EventSub Subscriptions: ✓ when the subscription is in place. A subscription that needs a missing scope says which one and offers re-authorize. You may also see Not on your plan — no subscriptions expected, Reconnect your Twitch account to check subscriptions, or Could not reach Twitch — status unknown.

This is the first place to look when a module isn’t reacting to something on stream.

Who sends chat messages

Section titled “Who sends chat messages”

Each channel chooses which account posts its bot messages. The broadcaster chooses in Chatters → Bot Setup or in the Get set up checklist:

  • Speak as me: messages come from your own account. Nothing to set up.
  • StreamerCatalyst bot: the shared @StreamerCatalyst account posts for you.
  • My own bot account: a separate account you own, which you authorize once from Bot Setup by signing in to Twitch as that account.

With either bot, give it the moderator role in your channel (for example /mod streamercatalyst) so it can post freely. Twitch only lets a moderator send chat announcements, so if the bot isn’t a mod, announcements go out from your account instead.

  • Fallback: if the bot you chose isn’t connected, messages are sent from your own account.
  • Moderation actions always use your account. The choice affects chat messages only. Actions like adding a VIP or acting on AutoMod are always made with your own account.

See Chatters: bot identity for the verified bot badge and how Shared Chat sessions are handled.

Roles

Section titled “Roles”
Role Who In short
Broadcaster The channel owner who connected their Twitch account Everything, including billing, referrals, granting Twitch permissions, the bot identity, payouts and outside accounts
Lead Mod A moderator the broadcaster promotes in Settings → Lead moderators, or one detected from their Twitch Lead Moderator badge Can read and change module configuration. Can’t manage billing, referrals, the time zone or other Lead Mods
Mod A Twitch moderator for the channel who signs in to StreamerCatalyst Can read dashboards and live data, and do each module’s day-to-day work (in Chatters, for example, custom commands and Auto Chats)

Moderators sign in with their own Twitch account and switch into channels they moderate from the Channels you moderate strip on their Dashboard. A moderator session lasts up to 4 hours. Promoting someone to Lead Mod only changes their access inside StreamerCatalyst, never their role on Twitch. See Roles and permissions for the full detail.

Support access

Section titled “Support access”

StreamerCatalyst staff can view your account to help with a support request. That session is read-only unless full access is specifically granted, it ends after 4 hours, and you get an Admin viewed your account notification each time. A read-only support session can’t save changes, and no support session can change your billing.

Other accounts you can connect

Section titled “Other accounts you can connect”

Some modules connect to services other than Twitch. Each one is authorized on that service’s own page, not through your Twitch permissions:

  • Discord: add the StreamerCatalyst bot to a server you manage with Add to Discord. See Discord.
  • Tipping payouts: connect a Stripe payouts account from Tipping → Payments. Stripe collects your identity and bank details directly. Broadcaster only. See Tipping.
  • Tiltify: connect from the Integrations page through Tiltify’s own sign-in. No Tiltify password is stored. Broadcaster only. See Integrations.
  • Your own bot account: see Who sends chat messages.

Viewer sign-ins

Section titled “Viewer sign-ins”

A few public pages let viewers sign in with Twitch. Each one asks Twitch for no permissions at all: it only confirms who the viewer is. None of them creates a StreamerCatalyst account or a dashboard session.

Security

Section titled “Security”
  • Tokens are encrypted. The Twitch access tokens that let StreamerCatalyst act for you, and your sign-in sessions, are encrypted (AES-256-GCM) before they’re stored.
  • Your password stays with Twitch. StreamerCatalyst never sees it and will never ask for it.
  • Your overlay URLs and bot API key are secrets too. Every overlay URL carries your widget token. If one leaks, use Revoke all overlay URLs in Widgets (see Widget token). The Chatters bot API key can be replaced with Regenerate (see Bot API).
  • Revoking access. You can disconnect StreamerCatalyst at any time from your Twitch Connections settings. Once access is revoked, StreamerCatalyst can no longer act on your channel. Your automations stop, and you may get an email titled “Action needed: reconnect your Twitch account”. To reconnect, sign in again with Connect with Twitch.

For what’s stored and for how long, see the Privacy Policy.

Permissions by module

Section titled “Permissions by module”

Each module has a page listing the scopes it uses (and when each is asked for) and the Twitch events it relies on:

Module Permissions page
Platform (sign-in, roles, Lead Mod detection) /auth/platform/
AI Personas /auth/ai/
Events /auth/events/
Chatters /auth/chatters/
Modomation /auth/modomation/
Stream Planner /auth/stream-planner/
Numbers /auth/numbers/
Widgets /auth/widgets/
Discord /auth/discord/
Tipping /auth/tipping/
Integrations /auth/integrations/