Setting up channels

#mod-logs

Moderation events: bans, kicks, warns, timeouts, message edits, deletions. The Logs module assigns it.

#server-logs (optional, if you want them separate)

Server events: changes to channels, roles, threads, webhooks, integrations. Worth separating if your server is large and the moderation logs fill up quickly.

#voice-logs

Connections, moves and mutes in voice channels. It tends to be noisy, so it's best kept apart.

#ticket-logs and #ticket-transcripts

Logs: the module's events (opened, closed, reassigned). Transcripts: the full HTML of each ticket when it's closed. Keep them private — the transcript contains the whole conversation.

#welcome and #goodbye

For join/leave announcements. They can be the same channel or separate ones. Make sure the bot can write and embed links.

#suggestions

Where the Suggestions module posts its embeds. Allow only the bot to write, and let everyone else vote with reactions.

#giveaways

A recommended channel to keep giveaways in one place. It isn't mandatory: each giveaway can go to whichever channel you specify.

#boost-announcements

For the Boost module's messages when someone boosts the server.

#commands (optional)

A dedicated channel for command spam. From Integrations → Roody you can restrict commands so they can only be used here.

Ticket category

The tickets module needs a category to create each ticket's channel in. Recommendations:

• The bot needs Manage Channels and Manage Permissions at category level (not just on the child channels).
• Restrict the category to the staff roles configured in the module.
• If you have several ticket types (support, reports, shop), create one category per type and assign it from the dashboard.

Voice category for music

Not mandatory, but creating a category for the voice channels you play music in makes permissions easier: Connect and Speak for Roody and for the authorised users.