Team & permissions
Most streamers run AveloBot solo, but you can hand parts of the dashboard to your moderators or co-admins without giving them the broadcaster account. The Team page (/settings/team) is where you invite them, set their role, and choose exactly what each role is allowed to manage.
Only the workspace Owner sees this page.
Roles
| Role | What it means |
|---|---|
| Owner | The Twitch broadcaster the workspace belongs to. Always has every permission. There is exactly one Owner per workspace and the role can't be changed or removed. |
| Admin | Trusted co-streamer or manager. By default has every permission, but you can revoke individual ones. |
| Moderator | Channel moderator. By default can manage chat-content things (commands, counters, events, quotes, timers, premium overview) but not the Twitch channel connection, Spotify integration, or StreamElements integration. |
Higher roles don't automatically inherit lower-role permissions: the matrix is per-role and you decide what each role can do.
Adding a member
- Open
/settings/teamand click Add member. - Enter the Twitch login (lowercase, e.g.
mychannelmod). AveloBot resolves it via the Twitch Helix API; if the user has never signed in to AveloBot, an account is created on the spot. - Pick Admin or Moderator.
- Save.
The new member must log in to AveloBot at least once for the role to take effect — they sign in with their own Twitch account just like you did.
Changing a role
Use the role dropdown in the Members table. Owner is read-only. Role changes apply on the affected member's next login (a banner at the top of the Team page reminds you of this).
Removing a member
Click the trash icon next to the member's row and confirm. They lose access on their next request after re-login. Their identity isn't deleted from Twitch — only their membership in your workspace.
Permission matrix
The lower table on the Team page lets you toggle each capability per role. Owner is implicitly all-on and isn't shown.
| Permission key | What unlocks for the role | Default for Admin | Default for Moderator |
|---|---|---|---|
commands.manage | The Commands sidebar item and /commands page (built-in defaults & custom commands). | On | On |
counters.manage | The Counters sidebar item and /counters page. | On | On |
events.manage | The Event Responses sidebar item and /events page. | On | On |
quotes.manage | The Quotes sidebar item and /quotes page. | On | On |
timers.manage | The Timers sidebar item and /timers page. | On | On |
premium.manage | The AveloBot Premium sidebar item and /premium page. | On | On |
channel.manage | Settings → Channel (/channel) — the Twitch connection itself. | On | Off |
spotify.manage | Settings → Spotify (/settings/spotify) and the Spotify operational pages (Playlists, SR Blacklist). | On | Off |
donations.manage | Settings → Donations (/settings/streamelements). | On | Off |
The three integration permissions default to off for Moderators on purpose: connecting/disconnecting Twitch, Spotify, or StreamElements affects the whole workspace, and most channels prefer to keep that with the broadcaster or admins.
A toggle changes both what the member can read and what they can save. If a permission is off, the corresponding sidebar entry is hidden entirely on the member's next page load.
When toggle changes apply
Permission updates are written immediately, but cached on the member's auth session. The member sees the new state the next time they log in (or after their session expires). The Team page shows an info banner reminding you of this.
Tip: keep the Owner the integrations holder
Even if you fully trust your admins, it's usually cleanest to leave channel.manage, spotify.manage, and donations.manage with the Owner only — those are the connections that get the workspace its data, and you don't want them flipped accidentally.