Getting started · Build 7.2.1

Set up Rallybit in a few minutes.

Start with activity and community tools, then grant only the moderation and security permissions for modules your staff actually enables.

1. Invite the bot

Use the official invite button from the Rallybit homepage. Select a server where you can manage apps.

Core permissions.View Channels, Send Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Use External Emojis, and Mention Everyone or Roles.

Moderation and security permissions.Manage Messages, Moderate Members, Kick Members, Ban Members, Manage Nicknames, Manage Roles, Manage Channels, Manage Webhooks, Manage Server, and View Audit Log are required only by their matching modules. Rallybit does not require Administrator.

2. Enable the required intents

In the Discord Developer Portal, enable Server Members Intent for account-age checks and member moderation. Enable Message Content Intent when using invite filtering, blocked terms, or message edit/delete security logs. Presence Intent is not required.

3. Configure activity checks

Choose the message and response

Use /setactivitytext, /setmode, and either the reaction or button settings.

Choose duration and participant target

Use /setduration and /setwinner.

Set staff and logs

Use /setperm and /setlogs, then run /activitycheck once in a test channel.

4. Configure automatic quizzes

Run /quiz setup and choose a text channel, interval, category, answer time, and an optional role such as @Chat Revive. Then enable the schedule with /quiz auto enabled:true. You can change or disable the role later with /quiz pingrole.

5. Configure community notifications

Run /community pingrole and select a role such as @Chat Revive. Pulses notify that role by default, while icebreakers remain silent unless staff choose notify_role:true. Run /community settings to review the setup.

6. Test community tools

Use /community icebreaker for a conversation prompt and /community pulse for an aggregate mood pulse. Pulse history stores totals rather than individual response identities.

7. Test moderation privately

Use /mod panel on a test member or staff alt. The panel is private by default. Each action checks the moderator's permission and both role hierarchies before Discord receives the request.

8. Configure security safely

Start with /security logs channel and /security audit. Create the honeypot with /security trap setup, then configure the account-age gate and only the anti-nuke modules your server needs. Run /security overview after each change. The trap defaults to banning every human account except the server owner; trusted-role bypass is optional and disabled by default.