Team & permissions

The Team page (/settings/team) lets you grant moderators and co-administrators access to your dashboard without sharing your broadcaster account. Each member is invited with their own Twitch login, assigned a role, and granted exactly the dashboard areas that role is permitted to manage.

Only the workspace Owner has access to this page.

Roles

Role	Description
Owner	The Twitch broadcaster to whom the workspace belongs. Always holds every permission. Each workspace has exactly one Owner; the role cannot be reassigned or removed.
Admin	A trusted co-administrator, such as a co-streamer or channel manager. Holds every permission by default; individual permissions can be revoked.
Moderator	A channel moderator. By default permitted to manage chat content (commands, counters, events, quotes, timers, the Pro overview). Not permitted by default to manage the Twitch, Spotify, or StreamElements connections; the Owner can grant these explicitly.

Higher roles do not automatically inherit lower-role permissions. Each (role, capability) pair is configured independently in the permission matrix.

Adding a member

1. Open /settings/team and click Add member.
2. Begin typing the Twitch login (minimum two characters). The field is an autocomplete: AveloBot queries Twitch and suggests up to six matches, showing each candidate's avatar, display name, login, language, and a LIVE badge with the current category if they are currently streaming. Members already in your workspace are greyed out and marked already a member.
3. Select the desired candidate, or enter the full login manually if it does not appear in the suggestions.
4. Select Admin or Moderator.
5. Save. AveloBot resolves the login via the Twitch Helix API; if the user has not previously signed in to AveloBot, an account is created automatically.

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

Select the new role from the dropdown in the Members table. The Owner row is fixed; ownership cannot be transferred through this interface. Role changes take effect 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. Access is revoked on the member's next AveloBot request. The Twitch account itself is not affected — only the membership in your workspace is removed.

Permission matrix

The lower table on the Team page allows you to toggle each capability per role. The Owner has all permissions implicitly and is therefore not shown in the matrix.

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
pro.manage	The AveloBot Pro sidebar item and /pro page (Pro feature catalogue and overview).	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 by design. Connecting or disconnecting Twitch, Spotify, or StreamElements affects the entire workspace, and these actions are typically reserved for the broadcaster or for administrators.

A toggle controls both read and write access. When a permission is disabled, the corresponding sidebar entry is hidden from the member on the next page load.

When toggle changes apply

Changes are persisted immediately, but the member's active session retains the previous permissions until the next login or until the session expires. If a permission change does not appear to take effect, the member is most likely still using a session that predates the change. A banner above the matrix on the Team page notes this behaviour.

Recommendation: keep integration permissions with the Owner

Even when you fully trust your administrators, it is generally advisable to leave channel.manage, spotify.manage, and donations.manage enabled only for the Owner. These permissions control the connections that supply the workspace with data, and an inadvertent disconnect during a live stream is a significant disruption.