Jambot 8.1.4

Add Jambot with the control level you prefer.

Both links install the same bot and slash commands. Administrator is simplest. Required permissions is narrower and includes the current permission set used by moderation, tickets, Deep Work threads, generated files, verification, and temporary invites.

Simplest setup

Administrator

Best when you want moderation, tickets, verification, backups, raid protection, GrandJam, and Jambot administrator tools to work without manually adjusting individual permissions.

Continue with Administrator

Discord permission integer: 8

Narrower setup

Required permissions

Uses the current Jambot permission bitfield. It includes Create Instant Invite for one-use admin invites, plus the thread and attachment permissions GrandJam needs for Deep Work and generated files.

Continue with required permissions

Discord permission integer: 10292755164407

What the narrower link includes

Permissions match the current feature set.

Create Instant Invite for Jambot admin one-use temporary server invites
Attach Files so GrandJam can deliver code and project artifacts
Create Public Threads, Send Messages in Threads, and thread management for Deep Work workspaces
View channels, send messages, embed links, reactions, history, and mentions
Manage messages, channels, webhooks, roles, nicknames, server settings, and expressions
Kick, ban, timeout, create and manage ticket channels, and view the Audit Log where features require it

After installation

Five checks prevent most permission errors.

Move the Jambot role above every role or member it must manage.
Run /permissions-check.
Run /access add-role for each normal staff role that should use Jambot commands.
If your server has been granted GrandJam, run /grandjam console and /grandjam thinking to choose AI and Deep Work behavior.
For support tickets, run /tickets setup and then /tickets panel.

GrandJam server AI remains disabled until a Jambot admin grants it. Installing Jambot does not automatically enable AI.