Docs / Permissions Thea needs

Permissions Thea needs

The site invite requests a specific set of permissions (not Administrator). /help and /about also link an Administrator re-invite if the bot stops responding after a permission change. Nothing here is speculative. Each row maps to a real feature in the bot.

Permissions and what needs them

View Channels / Read History / Send Messages

Everything Thea says: chat replies, slash command responses, images, GIFs, room messages.

Embed Links / Attach Files

Embeds for commands, avatars, generated images, GIFs and voice-message files.

Manage Messages

/clearhistory deletes your messages and Thea's replies in a channel. Without it, the command fails cleanly.

Manage Webhooks

Character avatar replies and room chat post through a webhook so messages look like the character. Without it, replies fall back to Thea's own name.

Manage Roles

Optional character ping roles (toggle in /settings → Character pings). Without it, role sync is skipped. Chat still works.

Add Reactions / Use External Emojis

Reaction GIFs and the block-a-GIF reaction flow.

Mention Everyone

Requested on the invite, but Thea is built with allowed mentions off. She never pings @everyone or @here.

Connect / Mute / Deafen Members

Voice-related capabilities listed on the invite. Text chat, economy and rooms do not need them.

Moderate Members / Change Nickname / Manage Events / Private Threads

Present on the site invite for forward compatibility. Core chat features do not depend on them today.

Gateway intents

Message Content (privileged)

The text of messages, required for Thea to read what you type in allowed channels and DMs.

Server Members (privileged)

Joins, leaves and role changes: welcome messages and character role sync.

Default intents

Everything else Discord sends by default (messages, reactions, etc.).

You do not configure intents

Intents are set on Thea's bot application by the developer, not in your server. They are listed here so you know what the bot can see. Message Content and Server Members are privileged intents, and Discord only grants them to verified apps.

Role hierarchy

Discord refuses any action against a member whose highest role sits above Thea's highest role, regardless of permissions. Character ping roles are created under Thea's role; if you need Thea to manage roles higher up, drag Thea's role above them in Server Settings → Roles. Chat and economy never need hierarchy.

Diagnosing a permission problem

1

Check the channel

Right-click the channel → Edit Channel → Permissions → Thea. Channel overwrites beat server permissions. A category deny overrides a server allow.

2

Check allowed channels

Thea only replies in channels added with /setup (or in DMs). No response in a normal channel usually means the channel was never set up. Run /setup add #channel.

3

Re-invite if needed

If features broke after someone edited Thea's role permissions, re-invite from the link in /about (Administrator) or re-check each permission above in Server Settings → Roles.

4

Ask in support

Still stuck? Bring the channel name, what you expected and what happened to the support server.

Commands used on this page

  • /help: List all available commands organized by category.
  • /about: Bot info including version, server count and the re-invite link.
  • /setup: Add, list or remove channels Thea may chat in. Manage Server required.
  • /clearhistory: Delete your messages and Thea's replies in a channel.
  • /settings: Personal toggles: text/voice chat, webhook avatars, role pings.