Give a moderator access

You can let someone manage your bot without giving them your account. Access is granted per person, it is revocable, and every action taken under it is recorded.

Twitch moderators arrive on their own

Pyre checks your Twitch moderator list periodically and adds new moderators automatically, at whatever you have set as your default access level. Out of the box that default is Editor. You can turn the sync off on the Team page if you would rather add everyone yourself.

Two things follow from it being a sync rather than a one time copy: someone you un-mod on Twitch loses their Pyre access on the next sweep, and someone whose level you changed by hand keeps your change instead of being reset to the default.

Moderators on YouTube and Kick do not arrive this way, because neither platform offers a moderator list an app can read. Invite them.

Invite someone

Open Team on your own channel.
Create an invite link. Choose the access level, how many hours it stays valid, and optionally a label so you remember who it was for.
Copy the link. It is shown once.
Send it. They accept by signing in with the Twitch account that will be moderating, because the grant binds to a real Twitch identity. Your channel then appears in their channel selector.
Check the Change log on the Team page whenever you want to see what has been done and by whom.

The three levels

Level	Can do
Read-only	See the delegated surfaces and change nothing
Editor	Everything above, plus creating and editing commands, timers and quotes
Manager	Everything above, plus filters, chat modes, variables and blocked terms, and the live queue controls for songs, text to speech and alerts

Reading is the same at every level: a Read-only moderator can see your commands, your filters, your chat log and your queues. The levels differ only in what they may change.

Editor is the content tier, and the boundary is deliberate. A command, a timer or a quote is reviewable and reversible after the fact. Skipping the track that is playing, or rejecting a paid request, is a live act with an audience watching, so it sits with Manager.

Chat log is readable at every level and writable at none. Deleting somebody’s chat history is a support action, never a delegated one.

What a moderator can never do

Some things stay with the channel owner structurally. There is no level and no toggle that reaches them:

Grant management. The Team page itself is owner only, so a delegate can never give anyone else access, or widen their own.
Money. Tips and the payout account.
Your public profile.
Your connections, so nobody can detach or re-point the platform accounts the bot runs on.
Configuration behind the live controls. Song request settings, the song blocklist, and every text to speech setting including voices, tiers, rewards and minimum tip. A moderator may work the queue; they may not change the rules the queue runs by.
Alert configuration, including firing a test alert. Someone who can approve a real tip alert cannot invent a fake one.

Whole sections simply do not appear on a channel you moderate: Connections, Team, Tips, Public profile, Loyalty & Giveaways, Test console, Import, Activity log, Overlays & Widgets, Clips, and Schedule & Social.

Fine tuning access

Three live operations areas can be widened or narrowed per person, on top of their level: Song queue control, Text to speech transport and Alert queue.

Each has three settings. Allow and Deny decide it outright. The third option follows the person’s level, and it tells you what that means before you pick it, reading for example “Use the access level (Editor: no)”.

You can set these as your own defaults for everyone newly invited or synced, and also per person. A setting you make on one person always wins over the default, including when you change the default later.

Removing access

Revoke the grant on the Team page. It takes effect on their next request, and their channel selector no longer offers your channel. The Change log keeps what they did, which is the point of having one.