Normal TTS playback
View Channel lets Bozos see the VC, Connect lets it enter, and Speak lets it transmit generated audio. If Connect is denied, the bot cannot join. If Speak is denied, it may appear in the VC but remain silent.
Text-channel access still matters
Commands and eligible TTS messages also need the normal text-channel access required for Discord interactions and message handling. A bot can have perfect voice permissions but still fail in a text channel that blocks it.
Voice Preview permissions
/voicepreview does not play its preview through the VC. It replies privately with native Discord voice messages. The channel where the command is used must allow Bozos to Attach Files and Send Voice Messages.
Auto-Join permissions
When enabling /auto-join, Bozos checks View Channel, Connect, Speak and Send Messages for that VC. The user configuring it also needs Manage Server, and Bozos must already be connected to the same VC.
Why server permissions can look correct but still fail
Discord channel and category overrides can replace the permissions inherited from a role. A global Allow can still be defeated by an explicit deny on the specific VC or its synchronized category.
Quick fix checklist
- Open the affected voice channel's permissions.
- Check the Bozos TTS role/bot member for View Channel, Connect and Speak.
- If Auto-Join is failing, also confirm Send Messages.
- If
/voicepreviewis failing, inspect the text channel and allow Attach Files + Send Voice Messages. - Check category-level overrides if several channels are affected.
- Run the command again from the same VC as Bozos TTS.
Do not confuse command access with voice access
A successful /help response only proves that Discord interactions work in that channel. Test the exact feature and exact VC that is failing.