RecruitBoardRecruitBoard
RECRUITBOARD · COMPLETE BEGINNER GUIDE

Set up RecruitBoard, one step at a time.

Every section tells you where to click, whether a Discord command is needed, and exactly what permissions the bot needs. Follow the steps in order and test each feature before moving on.

Start at Step 1 ↓

Public setup guide · No login required to read

First, how to change Discord channel permissions: Right-click a channel → Edit Channel → Permissions → add the bot's role (or the bot member) → allow the permissions listed in that guide section → Save Changes. For ticket categories, right-click the category → Edit Category → Permissions. Discord role permissions and channel overrides both matter. Never share your bot token.

RecruitBoard is a web-based Discord management platform

RecruitBoard is NOT a traditional slash-command bot. Set up and manage your server, application forms, support tickets, security and other features using the RecruitBoard web dashboard. The only customer Discord slash command used for application panels is /application-panel.

Before using /application-panel:

  1. Invite the correct RecruitBoard bot to your Discord server and grant its required channel permissions.
  2. Visit recruitboard.app and sign in with Discord.
  3. Select the server you want to configure and set up its channels and staff roles.
  4. Open Application Panels, create and save at least one application form, add your questions, and make sure the form is enabled.
  5. Allow the bot to synchronise. In the Discord channel where you want the application panel, run /application-panel and select the configured form if prompted.
  6. Check that the panel appears. Your members then use its buttons to apply; they do not need commands.

All other normal setup and management is carried out through the website and Discord's interactive buttons.

Get RecruitBoard Premium — invite the separate Premium bot

The Free bot does not become the Premium bot automatically. To use Premium features, you must invite the RecruitBoard Premium bot to the server you want to upgrade and activate Premium for that server through the website.

  1. Choose your Discord server and make sure you have permission to add apps.
  2. Click Invite RecruitBoard Premium Bot below and authorise it for the correct server.
  3. Return to the RecruitBoard web dashboard, select that server, and complete Premium activation or subscription as required.
  4. Configure Premium features on the website. You do not need additional slash commands.

1. Invite the bot to your Discord server

BEFORE YOU CONTINUE — STEP 1
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Invite through the website/Discord authorisation screen.

🔐 Required bot permissions / channel access

Bot must be invited with permissions appropriate to the features you enable; do not grant Administrator just for convenience.

  1. Use the Invite Bot to Server button on RecruitBoard.
  2. Choose a server where you have permission to add applications and approve Discord's authorisation screen.
  3. Make sure the bot appears online and has access to the channel where you plan to post the panel. It needs permission to view that channel, send messages, embed links .
If your server is not shown on Discord's invite screen, check that you have permission to manage or add apps to that server.

2. Sign in and choose your server

BEFORE YOU CONTINUE — STEP 2
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Sign in on the website and choose the correct server.

🔐 Required bot permissions / channel access

You need permission to manage the Discord server to configure its settings.

  1. Sign in to RecruitBoard using Discord.
  2. Open Your Discord servers and select the server you manage.
  3. On Overview, check the Bot bridge and Last sync cards. Once the bot is connected and syncing, its channels, roles and forms will appear here.

3. Set up Channels & Roles on the website

BEFORE YOU CONTINUE — STEP 3
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Select channels and roles on the website; save the settings.

🔐 Required bot permissions / channel access

Review channel: deny View Channel to @everyone; allow your staff role and the bot View Channel, Send Messages, Embed Links and Read Message History. Log channel: allow the bot View Channel, Send Messages and Embed Links. For accepted roles: bot needs Manage Roles and its highest role above the role it assigns. Ticket categories: bot needs Manage Channels and relevant channel access.

Go to Overview → Channels & Roles and choose the following options:

  1. Application Review Channel: where submitted applications are sent for staff review.
  2. Log Channel: where application activity is recorded.
  3. Staff Role: the role authorised to review applications.
  4. Accepted Role: the role assigned to successful applicants.
  5. Interview Ticket Category: where private interview channels are created.
  6. Staff/User Ticket Category: where private conversations with applicants are created.

Click Save Settings, then allow the bot to sync. Make sure the bot has permission to access the selected channels and manage the roles or tickets it needs.

4. Manage your application forms on RecruitBoard

BEFORE YOU CONTINUE — STEP 4
⌨ Discord commands

No Discord command needed to create or edit questions.

📍 Where to do it

Use Application Panels / form editor on the website.

🔐 Required bot permissions / channel access

Forms are configured on the website. For later posting, the bot needs View Channel, Send Messages and Embed Links in the chosen public application channel.

  1. Open Application Panels from your server dashboard.
  2. Select the application form or panel you want to manage.
  3. Use the web form editor to configure its questions and application settings.
  4. Allow the bot to sync your changes before testing the application panel in Discord.
Application forms are managed through the RecruitBoard web dashboard. You do not need to use Discord slash commands to create or edit their questions.

5. Publish your application panel using /application-panel

BEFORE YOU CONTINUE — STEP 5
⌨ Discord commands

/application-panel — the only application-panel slash command. Set up a form on the website FIRST.

📍 Where to do it

First create and enable the form in the RecruitBoard website dashboard; then run /application-panel in the Discord channel where you want to post it.

🔐 Required bot permissions / channel access

Public #applications channel: the bot needs View Channel, Send Messages, Embed Links and Read Message History. Members need View Channel to see the panel and use its Apply Now button. Keep the staff review channel private.

  1. In Discord, create or select a public text channel such as #applications.
  2. Give the bot View Channel, Send Messages, Embed Links and Read Message History.
  3. Sign in to the RecruitBoard website, select your server and open Application Panels.
  4. Create and save your application form, configure its questions and ensure it is enabled/open. Set up the review channel and staff roles as described in Steps 3 and 4.
  5. Allow the bot to synchronise your saved settings.
  6. Go to your chosen Discord application channel and type /application-panel. Select the form if Discord prompts you, then submit the command.
  7. Confirm the application panel appears. Members click its Apply Now button and complete the application; they do not need slash commands.
Important: Running /application-panel before creating and enabling a form on the website will not complete the setup. RecruitBoard is web-based; the command only posts the already-configured application panel.

6. Review and manage applications

BEFORE YOU CONTINUE — STEP 6
⌨ Discord commands

No Discord command required for normal review.

📍 Where to do it

Staff use the review buttons; use the Applications page on the website to inspect submissions.

🔐 Required bot permissions / channel access

Private review channel: bot needs View Channel, Send Messages, Embed Links and Read Message History; staff need View Channel and permission to use review controls. Do not allow @everyone to view applicants' answers.

  1. An applicant selects Apply Now and answers the questions in Discord DMs.
  2. Submitted applications appear in your configured review channel.
  3. Authorised staff can use the review controls to Accept, Decline or Open Ticket with User.
  4. Use RecruitBoard's Applications page to view synced submissions, answers and decisions.

7. Create a Support Ticket panel

BEFORE YOU CONTINUE — STEP 7
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Create, enable and save the support panel on the website. The bot publishes it on sync.

🔐 Required bot permissions / channel access

Public ticket panel channel: bot needs View Channel, Send Messages, Embed Links and Read Message History. Private ticket category: bot needs Manage Channels, View Channel, Send Messages, Embed Links, Read Message History and Manage Roles for access updates. Staff role needs access to private tickets.

RecruitBoard can also manage private Discord support tickets. Each server can create its own support departments and ticket panels, independently of application forms.

  1. Open Support Tickets from your server's sidebar.
  2. Under Create Ticket Panel, enter a panel name (for example, General Support) and a description, then create it.
  3. Choose the Ticket Panel Channel (the public text channel where members will see the Open Ticket button), such as #bot-support.
  4. Choose the Private Ticket Category, where the bot creates a separate private text channel for each ticket.
  5. Choose the Support Staff Role, which determines which staff can access and manage the ticket.
  6. Tick Enable panel and click Save Panel Settings.
The bot publishes or updates the public support panel on a successful synchronisation (normally around two minutes). Support tickets do not require a Discord slash command.

8. Customise the public Support Ticket embed

BEFORE YOU CONTINUE — STEP 8
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Edit and save the public panel embed on the website.

🔐 Required bot permissions / channel access

Public ticket panel channel: bot needs View Channel, Send Messages, Embed Links and Read Message History. Channel permission overrides must not block it.

On the Support Tickets page, edit the panel's Discord Panel Embed Customisation settings:

  1. Embed Title: the heading members see in the public ticket panel.
  2. Embed Message: your support information, instructions and opening hours. Discord Markdown, emojis and line breaks are supported.
  3. Embed Footer: optional branding or support team credit.
  4. Embed Colour: choose the colour of the Discord embed.
  5. Button Text: customise the text shown on the button members click to open a ticket.

Save the panel settings and allow the bot to synchronise. An existing panel message should be updated instead of requiring a new panel.

9. Customise the welcome embed inside each ticket

BEFORE YOU CONTINUE — STEP 9
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Save the private opened-ticket embed on the website; open a NEW ticket to test.

🔐 Required bot permissions / channel access

Private ticket channels: bot needs View Channel, Send Messages, Embed Links and Read Message History. Attach Files if the ticket workflow uses attachments.

Under Ticket Opened Embed Settings, customise the message the bot posts inside the new private ticket channel. These settings are separate from the public ticket panel.

  1. Set the Opened Ticket Embed Title.
  2. Write the Opened Ticket Embed Message, explaining what information the member should provide and what happens next.
  3. Optionally set the Opened Ticket Footer and Opened Ticket Colour.
  4. Use placeholders such as {user}, {username}, {ticket_id}, {panel_name} and {server} to personalise the welcome message.
  5. Click Save Ticket Opened Embed, then create a new ticket to test the changes.
The public panel embed and private opened-ticket embed are different messages. Changes to the opened-ticket embed apply to newly created tickets; they do not rewrite existing ticket conversations. The old pre-ticket questions form is no longer required.

10. Open, manage and delete Support Tickets

BEFORE YOU CONTINUE — STEP 10
⌨ Discord commands

No Discord command needed for standard ticket buttons.

📍 Where to do it

Members click Open Ticket; staff use Claim, Close and Reopen; authorised admins can Delete.

🔐 Required bot permissions / channel access

Public panel: View Channel, Send Messages and Embed Links. Private ticket channels: Manage Channels, Manage Roles, View Channel, Send Messages, Read Message History, Embed Links and Attach Files. Members and staff must have the appropriate private-channel access.

  1. A member clicks the button on the public support panel. The bot creates a private ticket channel for that member and the selected support staff.
  2. Staff use Claim to take responsibility for the ticket.
  3. Use Close Ticket to close it, or Reopen Ticket to restore the member's access.
  4. Discord server administrators can select Delete Ticket and confirm permanent deletion.
  5. Before deletion, the bot attempts to send the ticket opener a transcript by Discord DM. If the transcript cannot be collected or delivered, deletion is cancelled. Attachment links are included, but attachment files are not copied into the transcript.
Deleting a ticket permanently removes its Discord channel and its saved ticket record. Keep any information you need before deleting. Ticket transcripts depend on the member being able to receive DMs from the bot.

11. Give the bot the correct Support Ticket permissions

BEFORE YOU CONTINUE — STEP 11
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Configure permissions in Discord Server Settings → Roles and the channel/category permission overrides.

🔐 Required bot permissions / channel access

At server level grant Manage Channels and Manage Roles to the bot role for ticket creation/access changes. In ticket channels grant View Channel, Send Messages, Read Message History, Embed Links and Attach Files. Avoid granting Administrator as a workaround.

The bot needs Manage Channels to create and delete ticket channels, and Manage Roles to change channel permission overwrites when tickets close or reopen. It also needs View Channels, Send Messages, Read Message History, Embed Links and Attach Files.

  1. In Discord, open Server Settings → Roles and check the roles assigned to the RecruitBoard bot.
  2. Grant the bot Manage Channels and Manage Roles at server level. A dedicated bot role is preferable to granting these powerful permissions to all support staff.
  3. Ensure the bot can access the public panel channel and the private ticket category, without category or channel overrides blocking it.
  4. If Discord returns 50013 Missing Permissions, inspect the bot's effective permissions and role assignments, not just the app settings in Integrations.
Discord application command permissions do not grant the bot permission to create channels or edit ticket access. Do not grant Administrator permanently just to work around missing permissions.

12. Set up the free Anti-Spam Trap

BEFORE YOU CONTINUE — STEP 12
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Enable and save Anti-Spam Trap on the website; test with a NON-staff account.

🔐 Required bot permissions / channel access

Trap channel: bot needs View Channel, Read Message History, Send Messages, Embed Links and Manage Messages. Kick mode additionally requires Kick Members, with the bot role above the member. Message Content intent may be required; avoid testing kick mode on real members.

Anti-Spam Trap is available to every RecruitBoard server, including free accounts. It protects a designated Discord text channel by removing messages posted by ordinary members and taking the moderation action you select.

  1. From your server's sidebar, open Anti-Spam Trap (Free).
  2. Create a dedicated text channel in Discord, such as #do-not-chat-here. After the next bot sync, select it under Trap channel.
  3. Tick Enable Anti-Spam Trap.
  4. Choose what happens when an ordinary member posts:
    • Delete Message + Kick Immediately: the bot removes the message and attempts to kick the member.
    • Delete Message + Warn: the bot removes the message, attempts to send a private Discord DM and posts a public warning mentioning the member in the trap channel. The public warning is removed after about 30 seconds.
  5. Customise the Permanent warning embed (up to 3,500 characters). This is the notice the bot posts in the protected channel to explain that members must not send messages there.
  6. Customise the Custom warning message (up to 1,500 characters). This is used for the private DM and public warning in Delete Message + Warn mode.
  7. Click Save Anti-Spam Settings and allow approximately two minutes for the bot to synchronise. Check that the warning embed appears in your chosen channel.
Permissions and safety: The bot needs View Channel, Read Message History, Send Messages, Embed Links and Manage Messages. Kick mode also needs Kick Members, and the bot's role must be above the member's role. Enable the Message Content privileged intent in the Discord Developer Portal if required. Server owners, administrators, members with Manage Server, and members holding your configured Staff Role are exempt. A blocked DM does not prevent the public warning. Test with a non-staff account before enabling kick mode for your community.

13. Welcome & Goodbye: greet new members (Free)

BEFORE YOU CONTINUE — STEP 13
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Configure welcome/goodbye text or embed and save on the website; test with a genuinely new join/leave.

🔐 Required bot permissions / channel access

Welcome and goodbye channels: bot needs View Channel, Send Messages and Embed Links for embeds. For role-on-join: Manage Roles with bot role above target role. Private welcome DMs can be blocked by member privacy settings.

Use Welcome & Goodbye to send a personalised greeting when somebody joins and a farewell when somebody leaves. Standard welcome and goodbye messages are available on both Free and Premium bots.

  1. Open Welcome & Goodbye from your server's sidebar.
  2. Enable Send a message when a user joins the server and choose the Welcome Message Channel. This is the channel where your greeting will be posted.
  3. Choose Text message for a normal Discord message or Embed message for a styled Discord embed. Use the message editor to write your greeting and insert supported placeholders such as {user} and {server}.
  4. For an embed, customise its accent/stripe colour, author name and image, title, message, thumbnail, additional fields and footer where available. Use Preview to check the layout.
  5. Enable Send a message when a user leaves the server, choose the separate Goodbye Message Channel and write the farewell text. Use the supported username placeholder shown in the editor, such as {user.idname}, to personalise it.
  6. Optionally enable a private welcome message for new members. Discord privacy settings may prevent the bot from delivering DMs.
  7. Optionally enable Give a role to new users and choose the role. The bot needs Manage Roles, and its highest role must sit above the role it assigns.
  8. Click Save, allow the bot to synchronise and test with a new joining member. A member leaving can be used to check the goodbye message.
Channel permissions: The bot must be able to View Channel, Send Messages and Embed Links in the chosen welcome and goodbye channels. It may also need Attach Files to send a Premium welcome card. The two channels can be different. If a channel is missing from the list, wait for a successful sync and refresh the page.

14. Premium Welcome Card Designer

BEFORE YOU CONTINUE — STEP 14
⌨ Discord commands

No Discord command needed.

📍 Where to do it

Design and save the Premium welcome card on the website; test with a genuinely new member.

🔐 Required bot permissions / channel access

Welcome channel: bot needs View Channel, Send Messages, Embed Links and Attach Files. Premium must be active and the card enabled.

Premium only: Add a personalised image card to the normal welcome message or embed. The Premium bot generates the final card using the joining member's avatar and details.

  1. On Welcome & Goodbye, enable Send a personalised welcome card when a member joins. Keep the welcome message enabled and select its destination channel.
  2. Enter a Card title and Card subtitle. Supported placeholders include {server}, {user} and {member_count}.
  3. Choose the Welcome card font and a Card text colour. The same selected font is used for the title and subtitle. The preview uses sample member details.
  4. Upload a Custom background image (JPG, PNG or WebP, maximum 4 MB), or retain your existing saved background. Use Remove background only when you want to clear it.
  5. Adjust Overlay opacity with the slider and use the available text-position controls/sliders to place the title and subtitle where they look best on the background.
  6. Check the live card preview, click Save and test with a real joining member in Discord.
Preview versus Discord: The website uses sample data, while the Premium bot renders the actual member's avatar and text. For a close font match, the selected font must also be installed in the bot's runtime. If a font is unavailable, the generated card may use a fallback. Check the actual Discord result after saving.

15. Premium Bot Personalizer — set up your own Discord bot

BEFORE YOU CONTINUE — STEP 15
⌨ Discord commands

No Discord command needed for Personalizer setup.

📍 Where to do it

Create your own Discord application, invite it, then verify and request activation in the website's Bot Personalizer.

🔐 Required bot permissions / channel access

Customer bot needs access to every channel it will operate in. For application panels: View Channel, Send Messages, Embed Links. For tickets: Manage Channels, Manage Roles and ticket-channel permissions. For welcome cards: Attach Files. For nickname: Change Nickname. Place the bot role above roles it must assign.

Give your recruitment bot its own identity using your Discord application. You need an active Premium subscription for the selected server and permission to manage that server.

  1. Create your Discord application. Open the Discord Developer Portal, choose New Application, give it a name and open its Bot settings.
  2. Configure the bot. Enable the Presence Intent, Server Members Intent and Message Content Intent settings shown in the RecruitBoard setup checklist. Keep Requires OAuth2 Code Grant disabled. Save your changes.
  3. Invite your customer bot. In the application's OAuth2 URL Generator, select bot and applications.commands. Choose the permissions needed for your enabled features, open the generated invite and select this server. The customer bot can remain offline until activation. Give it access to the channels it will use; role assignment also needs Manage Roles and a bot role above the roles it assigns.
  4. Gather your own application's credentials. Copy the Application ID from General Information, the Client Secret from OAuth2 and the Bot Token from Bot. Discord may require you to reset a secret or token to reveal a new value. Changing a token invalidates the old one.
  5. Save the setup securely. Return to this server's Bot Personalizer, click Set Up Custom Bot, confirm both checklist settings and enter those three credentials. Click Verify & Save Setup. Use your customer application's credentials, not RecruitBoard's shared bot credentials.
  6. Request activation. Click Request activation review after saving successfully. RecruitBoard reviews the connection and queues approved activation. Saving credentials alone does not start your bot. Your current bot remains active while approval is pending.
  7. Check activation. Once your connection shows active, check that your customer bot is online in Discord. RecruitBoard hosts it for you; you do not need your own hosting, environment-file changes or console commands.
  8. Choose its nickname and colour. Enter a Server-specific bot nickname, select the Premium embed accent colour and click Save personalisation. An active bot normally picks up changes within one minute. The nickname applies to this server, while the accent is used on supported newly generated recruitment embeds.
  9. Upload your logo. Under Customer bot logo, select a PNG, JPG or WebP image up to 10 MB, with dimensions from 64 to 1024 pixels per side. Confirm the avatar change and click Upload bot logo. Check the preview and applied status after sync. Discord may delay frequent avatar changes.
Disconnecting your custom bot
  1. Open Bot Personalizer for the correct Discord server and find Disconnect Custom Bot.
  2. Tick the confirmation box, then click Disconnect Custom Bot. RecruitBoard queues the shutdown automatically; you do not need console commands or a host restart.
  3. Refresh the page until it confirms that your custom bot connection is disconnected. While it is queued or stopping, keep the bot in your Discord server and leave its token and application unchanged. If the page says inspection is required or does not complete, contact RecruitBoard support rather than submitting repeated requests.
  4. Do I need to kick the bot? Disconnecting stops the RecruitBoard-hosted custom session but does not remove the bot account from Discord. Once disconnection is confirmed, you can remove the custom bot from your server if you no longer want it listed: in Discord, find your customer bot in the member list, right-click it and choose Kick, then confirm. You need permission to kick members and a role above the bot. Removing it is optional if you intend to reconnect later.
  5. Keep RecruitBoard Premium in the server. Remove only your own custom bot, not the main RecruitBoard Premium bot. Handling returns to the standard Premium bot; it must remain invited and have the required channel and role permissions.
  6. Deleting the Discord application is optional. Only delete it in the Developer Portal after disconnection has completed and you are certain you no longer need it. Kicking the bot from a server does not delete its application. Deleting the application prevents using it again.

Your RecruitBoard applications and saved settings are retained. Disconnecting does not cancel your Premium subscription or delete your Discord application.

Keep credentials private: Enter your token and client secret only into the secure RecruitBoard setup form. Never post them in Discord, support messages or screenshots. If a credential is exposed, rotate it in the Developer Portal and contact RecruitBoard to update the connection safely.
Logo and nickname: Your customer's bot avatar changes everywhere that bot appears, including DMs and any other servers it joins. The server nickname changes only in the selected server; it does not rename the application's global Discord account.
Applications and reviews: Continue configuring forms and panels on their dashboard pages. Application review channels must be private: deny View Channel for @everyone and allow the recruitment staff and your bot to view the channel. Give the bot Send Messages, Embed Links and Read Message History there.
Activation pending or a change missing? Check Premium is active and the correct server is selected. Confirm your bot is invited, then check its permissions, saved settings and connection status. For nickname changes it needs Change Nickname. If activation stalls or fails, contact RecruitBoard support with the server ID and visible error, without credentials; avoid submitting repeated activation requests.

Quick troubleshooting

Find your issue below and follow the recommended checks.

Welcome or goodbye message missing?

Check that the feature is enabled, the correct channel is selected, settings are saved and the bot can send messages there. Wait for sync and test with a new join or leave.

Premium welcome card missing?

Confirm Premium is active, the card and welcome message are enabled, and the bot can attach files. Test with a new member after saving.

Card font or text position looks different?

Check the selected font is installed in the Premium bot container and compare the saved settings with the actual Discord card.

Anti-Spam Trap not working?

Check that the feature is enabled, the chosen channel has synced, and the bot can read and delete messages. Kick mode also requires permission to kick members.

Bot not connected?

Confirm the bot is running and its bridge has been configured by the bot owner.

Channels or roles missing?

Allow the bot to sync, then refresh the Overview page.

Application panel not appearing?

Check the application panel settings and selected channel in the website dashboard, save any changes, wait for sync and verify the bot can view and send messages in that channel.

Support panel not appearing?

Enable and save the ticket panel, select its public channel and wait for a successful sync.

Ticket creation failed (50013)?

Grant the bot Manage Channels and Manage Roles, then check channel and category permission overrides.

Already have an open ticket?

Check whether the previous ticket channel still exists.

Custom ticket welcome not appearing?

Save the Ticket Opened Embed, wait for sync, then open a new ticket to test the change.

Transcript DM failed?

Ask the member to enable Discord DMs before attempting deletion again.