Streamer dashboard

Channel Permissions

Channel permissions decide who can touch your channel. You can invite helpers to manage settings, or authorise a single person to post alerts from their own account — and every write operation is recorded, so you can tell afterwards who did what.

What it solves

Once a channel grows, settings stop being a one-person job: editors, managers and chat MODs each need part of the access, and none of them needs all of it. Making everyone equal to you is convenient, but the price is that no mistake is ever traceable. This page gives out just enough access, plus a complete activity log.

The role hierarchy

Roles form a single hierarchy — each one contains the ones below it:

Owner ⊇ Admin ⊇ Editor ⊇ MOD ⊇ Sender

RoleWhat they can do
Owner Everything. Whoever created the channel is the owner; it cannot be assigned, and only the owner handles billing and channel transfer.
Admin Close to the owner: all settings, plus member management and payment credentials. Cannot act on the owner.
Editor All feature settings (commands, AI bot, modules, tips, channel management), but no member management and no payment settings.
MOD View the chat log and manage blocked words; for alerts, the same scope as a sender.
Sender May only post their own alerts, from their own account, inside Alert automation.

MOD comes from two places

  • Assigned by hand — you set someone to MOD in the member list. This is a site-local access level only: no Twitch API is called, and it does not make that person a moderator on Twitch.
  • Synced from Twitch — with Auto-grant MOD on, anyone /mod-ed on Twitch automatically gets the MOD role here, badged in the list to show where it came from. This switch is off by default: turning it on means every Twitch moderator gains write access to your alert settings, which reaches further than it first sounds — so the decision is left to you.

The two coexist and never overwrite each other. A Twitch-sourced MOD can only be removed with /unmod on Twitch, and after an /unmod anyone who already held a manually assigned role (editor, say) keeps it.

Senders and joined accounts

These two get confused constantly, but they are separate steps:

  1. You grant the Sender role = "I allow you to post in my channel from your own account".
  2. They join = they actually move in, spending a slot from their own channel-join quota.

With only the first step done, nothing is posted from their account yet. The Joined accounts tab lists the people who have completed the second step. There is a quota on both sides: how many channels one account may join, and how many accounts may join your channel.

  • Active — working normally.
  • Frozen — when a plan expires or a quota drops, the excess is frozen automatically (newest first). Frozen is not deleted: the data stays, it is only inactive, and renewing thaws it automatically.
  • Grandfathered — data that predates the quota, exempt from automatic freezing but unable to grow.

Remove and block are destructive

This is the part of the page to be careful with:

  • Remove kicks the account out of the channel and deletes the alerts they created here, notifying them. Those alerts do not come back if the person rejoins later.
  • Block does a full remove first (alerts deleted, person notified) and then adds them to a blocklist so they cannot join again.
  • A plain remove does not hold against a Twitch moderator: if they are still your Twitch MOD and auto-grant is on, they simply get the MOD role again. To keep someone out for good, use Block.

Both actions ask for confirmation. Blocked accounts can be unblocked from the Joined accounts tab.

Invitations and join requests

An invited member is notified and has to accept before anything takes effect (until then the status is Pending). Inviting an account to act as this channel's bot is a separate consent — it means their account sends every command reply on your behalf — so it is confirmed separately and listed separately. An active bot grant can then be picked as the sending account on the Commands page.

Activity log

Every write operation an authorised member performs in your channel is recorded: who, when, what, and whether it succeeded or was refused. The database keeps 180 days; the activity log page shows the last 60 days on the free plan and the full 180 days on Pro.

There is also an Automated actions log, which lists only the automatic punishments that did not take effect or failed — successful ones are deliberately left out. It exists to answer "why wasn't that account stopped?", not to be a full ledger.

Common misconceptions

  • Roles here are never pushed back to Twitch. Making someone a MOD on this site does not make them a moderator in your Twitch chat; and /mod-ing someone on Twitch only affects your roles here if auto-grant is on.
  • "Sender" is not "joined". The role is permission only. They still have to join before a slot is consumed and before anything is actually posted from their account.
  • There is no view-only role. The smallest role is Sender, which can already create its own alerts. A genuinely read-only case does not exist today.
  • Strangers cannot post. An early version had an "allow strangers" setting; it has been removed. Anyone posting from their own account in your channel must be someone you explicitly authorised.