We're happy to have you.

Q: Can the welcome say who invited the member?

Yes, when the Analytics service tracks invites. `{inviter}` and `{inviter.mention}` name who invited the member and `{invite.code}` names the invite, each when the bot is sure of it; otherwise they print Unknown. The bot needs the Manage Server permission to read invites.

Greet every join with a message and a card you design yourself, plus a DM, and hand out roles on join or from a menu. Gate the server behind a button, a captcha or a web page with a deadline, and give newcomers your rules, a quest and a buddy. Everything is set on the web, and the bot refuses to hand out any role that could hurt your server.

Get started

ways to verify

rotating greetings

card templates

slash commands

How it works

STEP 1

Run setup

The wizard creates #welcome and #welcome-logs, posts a sample, and the first time turns on the embed, the card, the first-message celebration and server highlights.

STEP 2

Write the greeting

Text or an embed you design with tags and conditions, up to 25 rotating variants with their own images, plus an optional goodbye, DM and boost thank-you.

STEP 3

Design the card

Start from one of 12 templates in the Card Studio, then move and restyle text, avatar, image and shape layers over a background from the library, your own upload or a link.

STEP 4

Decide what a join unlocks

Roles on join, each now or after its own wait and taken away again later if you like, or only after the member verifies. A buddy, a quest and a log line follow.

STEP 5

Keep them engaged

Quest tasks with rewards, role menus for self-service roles, a celebration for the first message, and milestones for the server.

Everything it does

The complete list, grouped by what you are trying to do. Every item describes what Welcome does today.

The welcome message

One greeting, or twenty-five that take turns.

Text or embed. A plain message or a rich embed with the member's avatar and a colour you choose.

An embed you design. A title, an author line, a small and a big picture, up to 6 fields, a footer and a timestamp. The goodbye and the DM get the same designer and can have a colour of their own.

Link buttons. Up to 3 buttons that open a link, under the welcome message or the DM.

A ping above the embed. An embed greeting carries a line of text above it, the member's mention by default, so the new member gets a notification. Leave it empty to send the embed alone.

Rotating greetings. Up to 25 variants, each up to 1,900 characters with its own image or GIF, shown at random or in order.

Server highlights. Add the member count and the boost level to the embed, and on a custom bot how many people are in voice.

Start here channels. Point newcomers at up to 5 channels as clickable links.

A goodbye. Off by default. A message on leave with the same placeholders and rotation, which can note how long they were a member.

A DM. Off by default. The same placeholders, sent privately.

A thank-you for boosts. Off by default. Text or an embed you design, posted when a member boosts, with a ping above the embed and an optional DM. Thank first boosts only if you like. Discord's own boost notice can be deleted once yours is posted.

Quiet during a raid. While Sentinel's raid mode is on, members who join get no greeting, card, DM, quest or buddy, and are not greeted later. The join log still gets a line that says why. On by default.

Previews as you type. The Messages page draws the welcome, the goodbye, the DM and the boost message with the bot's own renderer, as a returning member, a new account or with a known inviter.

Tags and conditions

One tag language for the greeting, the goodbye, the DM, the boost message, the card and the rules.

24 tags. The member, the server, today's date, account age, time in the server and boosts. The member count and the join number also come as a rank, such as 1,234th, in the server's language.

Conditions. {if user.returning}...{else}...{end} for returning members, new accounts, members without an avatar, boosted servers, first boosts and known inviters, and number checks such as {if member_count >= 1000}, up to three deep.

Who invited them. {inviter}, {inviter.mention}, {invite.code}, {invite.uses} and {invite.url}, from the Analytics service's invite tracking. Anything short of a sure match prints Unknown.

A join number that never goes down. {join_count} starts at your member count on the first join and adds one for every join after it. Set it by hand on the Logs & cleanup page when you move from another bot.

Typos flagged. The Messages page lists tags it does not know and conditions that are never closed, so you can fix them before anyone joins.

The welcome card

An image the bot draws itself.

Designed in the Card Studio. Start from one of 12 templates, then drag, resize and restyle every layer, with undo and redo. The simple view covers the template, background, text and avatar; the advanced view opens every layer.

Up to 20 layers. Text, the avatar as a circle, rounded square, square or hexagon with a ring, pictures (the member's avatar, the server icon, your uploads or an https link) and shapes, with outlines, shadows, glows and a frosted-glass blur.

39 fonts. Sans, display, gaming, script, serif and mono. Text takes a colour or a gradient and wraps over up to 6 lines or shrinks to fit, ending in an ellipsis when it still does not.

Names in any script. A character the chosen font lacks is drawn from the Noto fonts, so Chinese, Japanese, Korean, Arabic, Hindi and Thai names and colour emoji show up instead of empty boxes.

Backgrounds. 54 built-in pictures in 8 sets, a colour, a gradient of up to three colours, the main colour of the member's avatar, your own upload or an https link, with blur and darken.

Animated cards. An animated GIF or WebP background makes an animated GIF card of up to 48 frames, 800 pixels wide and 8 MB. Past a limit, or when there is no time left to animate it, the card is sent as a still image.

Any size. Seven presets from a 1,000 by 300 strip to 1,280 by 720, or any width and height from 300 to 2,000 pixels, with rounded corners if you like.

Your own uploads. Up to 20 per server: PNG, JPEG, GIF or WebP, up to 8 MB, at least 300 by 100 pixels and up to 64 frames. They are stored by YourBot's image service and served from a public link.

A goodbye card. Off by default. It follows the welcome card's look with goodbye wording until you design one of its own.

In the DM too. The welcome DM can carry the same card.

No watermark. Drawn by the bot itself, with no third-party service and no watermark.

Never holds up the greeting. If the card takes too long the message still goes out without it. Backgrounds are cached for 10 minutes.

Preview as you edit. The Card Studio draws the real card with the bot's own renderer as you change it, and /welcome test shows it in Discord.

The verification gate

Hold a join until a person proves they are one. Everything below runs on both the shared bot and a custom bot.

Set up for you. One click makes an Unverified role and a #verify channel, hides your other channels from new members until they verify, turns the gate on and posts the message. Members already in the server keep their access. A confirm step lists every change first, and Undo removes only what setup made and puts your previous settings back.

Three ways to verify. A green Verify button on a panel in a channel you choose. A captcha, an image with a code, three tries per image and a New image button. Or a web page, where the member signs in with Discord and the bot checks they are really in your server before anything is shown.

Until then, nothing. No auto-role and no buddy until the member verifies. Optionally an Unverified role is given on join and taken back on verify, so you can hide channels from people who have not verified yet.

A deadline. Give members a number of minutes, up to seven days, and one DM reminder before it. At the deadline the member is kicked, banned, held with a role you pick or left alone, your choice. Hold keeps them in the server and tells them a moderator has to verify them; verifying takes the role back.

Only the suspicious. Gate everyone, or only accounts younger than a number of days or without an avatar. With Sentinel's ban evasion on, an account that looks like a banned member is held too, and the log line names the banned account. Trusted members are verified the moment they join, and the log line says which path each join took.

Stricter during a raid. While Sentinel's raid mode is on, every member who joins can be made to verify, even when only new-looking accounts normally do.

Captchas that refresh. Set an interval from 30 to 600 seconds and the image is swapped in place while it is open. An answer to an image that has since been replaced fails, so a code cannot be farmed.

Rules above the button. Your rules show numbered under the verification message and on the web page, with a pointer to /rules when they do not all fit.

Your own button label. Up to 80 characters, such as "I agree to the rules", in place of Verify.

The steps by DM. Members who have to verify can get a DM on join saying where to go, what to press and by when, in one DM with the rules when those are DMed too.

Roles

What a join unlocks, and what it never can.

Auto-roles on join. One or more roles, each given at once or after its own wait of up to 365 days, and taken away again a set time later if you like: a newcomer role for a week, a veteran role after 90 days. A member who leaves before a role is due never gets it.

Members already here. Count first, then give the join roles to the members already in the server, each by their own join date, with progress and a stop button. Roles still to come are scheduled.

Bots that join. Bots get roles of their own and a line in the log channel when they join or leave. Greetings, DMs and member roles are for people only.

Discord's own verification level. Discord skips its verification check for anyone who has a role. The Roles page warns when a join role would let new members skip it and can make those roles wait 10 minutes.

Role persist. A returning member gets back the roles they held when they left, never the gate's own Unverified or hold role, never the boost role and never a join role that is taken away after a while.

Roles members give themselves. Pick up to 25 roles members can add with /roles add and drop with /roles remove. Nothing else can be picked, and every pick goes through the same safety check.

A boost role. Given to members who boost and taken away when they stop boosting, through the same safety check.

Safe by construction. Every role grant refuses everyone, managed roles, roles with dangerous permissions such as Administrator or Manage Roles, and any role above the bot's own.

Role menus

Self-service roles that look like part of your server.

Up to 25 roles per panel. Buttons or a dropdown.

Emoji reactions. Up to 20 roles on one message: reacting picks a role and removing the reaction un-picks it.

Six modes. Any combination, one at a time, add only, remove only, reversed (for opt-out roles) or first pick is final.

Limits. Cap how many roles a member can hold from a menu and how many members can hold a role (DPS, 10 max). Choose which roles may or may not use the menu. A refused pick says why. On a reaction menu the reaction comes back off.

Several roles per pick. One button, option or emoji can give up to 5 roles together.

Replies your way. A click answers privately with what changed, stays quiet or uses your own text with tags such as {role} and {user.mention}.

Templates that bring their roles. Name colours, pronouns, notifications, regions and platforms. The bot creates the roles with no permissions and reuses ones that already exist. While the menu is a draft, it can delete them again.

On a message you already posted. Paste its link and the bot adds one reaction per role. Deleting the menu takes the bot's reactions off and leaves your message alone.

Styled. An embed or plain text with a title, a formatted description, a colour, a thumbnail, an author row, a footer and a banner.

Survives restarts. Published panels keep working after the bot restarts.

Dangerous roles are hidden. The picker leaves out roles the bot must not grant and tells you why.

Rules

Written once, shown with /rules, by DM, in a channel and at the verification gate.

A numbered list. A title and up to 25 rules of up to 300 characters each, in your embed colour. Server tags such as {server} fill in.

Read with /rules. Any member reads them privately; with Manage Server, /rules can post them in the channel for everyone.

Posted, then kept up to date. Post them to a channel from the dashboard. Posting again to the same channel edits those messages, so links to them keep working.

DMed on join. Every new member can get the rules by DM.

Quests, buddies and celebrations

The first week, made into a game.

A welcome quest. Tasks such as send a message, join voice, add a reaction and say hello, or your own, each with an emoji and a trigger. Staff can mark a task done by hand.

Rewards per task or on completion. A role, a celebration message, or XP that members check with /quests list.

Buddies. Pair each newcomer with the least-loaded member of a buddy role, announce the pair, and optionally DM the buddy. Members who verify on the web page get a buddy the same way.

The first message. React with 🎉, announce it, or grant a role the first time a member speaks.

Milestones. Announce member counts you choose. The defaults are 100, 250, 500, 1,000, 5,000 and 10,000.

Logs and cleanup

What your moderators see, and what the bot tidies up after itself.

A join and leave log. One line per join with the account age, the member number and the inviter when it is known, and one per leave with how long they stayed.

Auto-delete. Delete the greeting after up to a day or as soon as its member leaves within a window you set. The goodbye can go after up to a day too.

Owner text screening

The shared bot speaks for every server on it, so it checks the text it is asked to send.

Checked when you save. Greetings, goodbyes, DMs, boost messages, card text, the verification message and button label, the rules, role menus and the buddy introduction are checked for invite spam, more than 10 links, known scam and look-alike sites and a scam phrase or @everyone next to a link, also when hidden with look-alike or invisible characters.

Held, not sent. The shared bot does not send held text until you change it, and the dashboard and /welcome test say what was held and why.

Never on a custom bot. A custom bot speaks for its own owner, so its text is never held.

Commands

Every slash command the service registers, and who can run it. Most day-to-day use happens through buttons and the dashboard; commands are the fast path.

Command	What it does	Who
`/welcome test`	Previews the live welcome message and card for you.	Manage Server
`/welcome set message`	Sets the welcome message.	Manage Server
`/welcome set channel`	Sets the welcome channel.	Manage Server
`/welcome set goodbye`	Turns goodbye messages on or off.	Manage Server
`/welcome set autorole`	Adds an auto-role.	Manage Server
`/welcome set dm`	Turns welcome DMs on or off.	Manage Server
`/welcome set card`	Picks the Gradient, Dark, Light or Minimal card look, replacing a Card Studio design.	Manage Server
`/quests list`	Shows your own quest progress and XP.	Everyone
`/quests admin-complete`	Marks a quest task done for a member.	Manage Server
`/roles list`	Lists the roles you can give yourself.	Everyone
`/roles add`	Gives you a role from the server's self-assign list.	Everyone
`/roles remove`	Takes a self-assigned role off you.	Everyone
`/rules`	Shows you the server's rules; with Manage Server it can post them for everyone.	Everyone

In the dashboard

Everything is configured from the web, per server. These are the areas you will find there.

Overview

Joins today and over 7 days with a trend, verifications and departures, what a new member sees step by step with a preview, problems the platform found, the command reference, a warning when the setup would greet nobody, a Send me a test button and a banner while Sentinel's raid mode is on.

Messages

The welcome message, the goodbye, the welcome DM and the boost message: channel, text or embed, the line above the embed, the embed designer and link buttons, rotating messages, server highlights, start-here channels, auto-delete for greetings and goodbyes, the boost options, a tag picker and live previews.

Card Studio

The welcome and goodbye cards: templates, backgrounds, uploads, layers, fonts and size, in a simple or an advanced editor, with a preview the bot draws.

Roles

Roles on join and their timers, sticky roles, roles for bots, giving the roles to members already here, the self-assign list for /roles and your role menus at a glance.

Role menus

Button, dropdown and emoji reaction menus with their status, and an editor for placement, layout, choice, message style and roles, with a live preview and publish.

Verification

A one-click setup of the gate with Undo, the gate (how members verify, who has to, whether accounts that look like a banned member are held, the Unverified role, the deadline and what happens at it, the reminder, the captcha refresh, the button label and the DM steps), what Welcome does during a Sentinel raid, plus a button that posts the panel.

Rules

The rules and their DM, plus a button that posts the rules.

Engagement

Milestones, the first-message celebration and the buddy system, each with a preview.

Quests

Turn the quest on, pick its channel, add, order, pause and remove tasks, add rewards and preview the embed.

Logs & cleanup

The join and leave log channel, the join counter and the last ten events.

Setup

The one-click wizard, then a status view with re-run.

Runs on its own

On join. Count the join, record the event, restore persisted roles, grant auto-roles now, on their timers or after verification, give the Unverified role and start the deadline if the gate applies, queue the verification steps and rules DMs, send the message and card, post the quest, send the DM, assign a buddy, check milestones and log a line, with the inviter when it is known. A bot gets its bot roles and a log line instead.

During a raid. While Sentinel's raid mode is on, a join gets its roles and its log line and nothing else, and with the switch on every member who joins has to verify. Nothing held is sent later.

After rules screening. On a server with Discord's rules screening on, the welcome waits until a member accepts the rules, and the join log line goes out at once and says so. Then the rest of the join runs: the join count, the greeting and card, the DM, the roles and the verification gate.

On leave. Record the roles they held, drop the join roles still to come, delete their greeting if it is set to go when they leave, send the goodbye with its card when that is on and log a line.

On a boost. Give the boost role, then thank the member in the boost channel (and by DM when that is on). Delete Discord's boost notice when you asked for it. When a member stops boosting, the boost role is taken back.

On verify. Grant the verified role, take back the Unverified and hold roles, and run the auto-role and buddy steps that were waiting, whichever way the member verified.

At the deadline. A pass every 15 seconds sends the reminder DM, then kicks, bans, holds or closes the case, on whichever bot serves your server.

On a timer. The same 15-second pass hands out roles whose wait is over, takes back roles whose time is up, deletes greetings and goodbyes whose time is up and picks up the job that gives the join roles to members already here.

On activity. Messages, voice joins and reactions tick quest tasks and trigger the first-message celebration.

On a reaction. Adding or removing a reaction on a reaction menu gives or takes the role, on whichever bot serves your server.

Limits and plans

The service is included with every subscription tier. These are the fixed limits it works within.

Setting	Value	Notes
Rotating greetings	`25`	Per welcome and per goodbye, 1,900 characters each.
Message text	`2,000 characters`	For the welcome, the goodbye, the DM and the boost message.
Embed fields	`6`	Plus up to 3 link buttons on the welcome and the DM.
Card size	`300 to 2,000 px`	Width and height. Seven presets; 1,024 by 400 by default.
Card layers	`20`	300 characters per text layer, 2,000 in all.
Animated cards	`48 frames`	A GIF up to 800 px wide and 8 MB, otherwise a still card.
Card uploads	`20`	Per server. 8 MB and 64 frames each at most.
Card background links	`5 MB`	Fetched within 5 s, from public https addresses only.
Auto-delete	`0 to 1,440 min`	0 = off. Up to one day.
Join role timers	`0 to 365 days`	A wait and a take-away time per role, up to 25 roles.
Roles for bots	`10`
Self-assignable roles	`25`
Verification deadline	`0 to 10,080 min`	0 = no deadline. Up to seven days.
Suspicious account age	`1 to 365 days`	Default 7.
Captcha	`3 tries per image`	Refresh interval 30 to 600 s, 0 = off.
Roles per menu	`25`	20 on an emoji reaction menu.
Rules	`25`	300 characters each, with a title of up to 100.
Start here channels	`5`
Quest tasks	`15`	Rewards have no fixed cap.

Works with

Sentinel

Sentinel's quarantine role makes a good hold role for members who miss the deadline, and account-age gating on join lives in Sentinel's rules.

Analytics

Analytics invite tracking fills the inviter tags and the invited-by note in the join log, and its /invites ranks who brought in members that stayed.

Safety and permissions

Role grants fail closed. Every grant, whether auto-role, persist, quest, first message, verification, the hold role, the boost role or a menu, refuses everyone, managed roles, eight dangerous permissions, and any role at or above the bot's own.

The web page checks membership first. A visitor signs in with Discord, and the bot confirms they are in your server with its own token before the page shows anything about it, and the page is rate limited per member.

Captcha codes are short-lived. A pending code lives for minutes, not days, and is consumed on the first correct answer.

No mass pings. Every message the service sends blocks everyone and here, and member names are defused so a member called @everyone cannot ping the server.

Scam text is held on the shared bot. Owner-written text is checked when it is saved, and the shared bot does not send text that looks like invite spam or a scam until it is changed.

Channels and roles are verified. Every channel and role saved from the dashboard is checked against your server's real channels and roles first, and the hold role may be neither the verified role nor the Unverified role.

Setup can be undone. The one-click verification setup records every role, channel and permission it changes. Undo deletes only what setup made and puts the rest back as it was, and a permission you changed since is left as you set it.

Temporary permissions are returned. To post into a locked verify channel the bot grants itself view and send, posts, then removes the grant.

Safe image fetches. Custom card backgrounds are fetched over https only, from public addresses only, with a size cap.

Uploads are checked. Card uploads are checked for type, size, pixels and frames before the image service stores them, and an upload a saved card still uses cannot be deleted.

Little is stored. Discord IDs and names in join and leave records kept for 180 days, a snapshot of roles on leave for role persist, a pending row per unverified member until they verify or the deadline passes and a row per join role still to come or to be taken back. Greetings set to be deleted are remembered by ID for 7 days at most. The one-click verification setup keeps the IDs of the roles, channel and permissions it changed so it can be undone. No message content.

What it does not do

Worth knowing before you set it up. If one of these matters to you, the marketplace may have a plugin that covers it.

No uploading your own font files. The card uses its 39 built-in fonts.
No animated avatars on the card. An animated avatar is drawn from its first frame.
No Discord membership screening. The gate is Welcome's own panel, captcha or web page.
No VPN or proxy check on the web verification page.
No drip sequence of follow-up messages after the welcome.
No quest leaderboard. Members see their own XP.
No CSV import for role menus or quest tasks.

Questions

Can I use my own image on the card?

Yes. In the Card Studio, upload a PNG, JPEG, GIF or WebP of up to 8 MB, or give an https link to one of up to 5 MB. An image layer can also put a logo anywhere on the card.

Can the card be animated?

Yes. Give it an animated GIF or WebP background and the card is sent as an animated GIF of up to 48 frames, 800 pixels wide and 8 MB. When it would be bigger, or takes too long to draw, a still card is sent instead.

Can the greeting change each time?

Yes. Add up to 25 rotating messages, each with its own image, and choose random or in-order rotation.

Can the welcome say who invited the member?

Yes, when the Analytics service tracks invites. {inviter} and {inviter.mention} name who invited the member and {invite.code} names the invite, each when the bot is sure of it; otherwise they print Unknown. The bot needs the Manage Server permission to read invites.

Does the welcome wait for Discord's rules screening?

Yes. A member still on Discord's rules screen cannot talk in the server yet, so the greeting, the DM and the roles wait until they accept the rules. The join log notes the wait when they join.

Can new members be held until they verify?

Yes. Turn on the verification gate, pick a button, a captcha or the web page, post the panel, and auto-roles and buddies wait for it. Give out an Unverified role to hide channels until then.

What happens if someone never verifies?

Whatever you chose for the deadline: a kick, a ban, a hold role that keeps them in the server until a moderator verifies them, or nothing. They get one DM reminder before it.

Can I gate only suspicious accounts?

Yes. Set who has to verify to suspicious accounts, pick the age limit, and everyone else is verified the moment they join.

Can the bot set up verification for me?

Yes. On the Verification page, Set it up for me makes an Unverified role and a #verify channel, hides your other channels from new members until they verify and posts the message. Members already in the server keep their access, and Undo takes it all back.

Does Welcome keep greeting during a raid?

Not by default. While Sentinel's raid mode is on, members who join get no greeting, card or DM, and the join log says why. You can also make everyone who joins during a raid verify.

What roles can it grant?

Any role below the bot's own that is not managed by an integration and does not carry a dangerous permission such as Administrator, Manage Roles or Ban Members.

Can members pick roles with reactions?

Yes. A role menu can use emoji reactions, on a message the bot posts or one you already posted, with up to 20 roles. Button and dropdown menus take up to 25, and /roles lets members add roles from a list you choose.

Does it welcome people who rejoin?

Yes, and with role persist on they get back the roles they had when they left, except join roles that are taken away after a while.

Can a role come after a member has been here a while?

Yes. Give a join role a wait of 30, 90 or 365 days and it arrives then, as long as the member stays. A role can also go away again, such as a newcomer role after a week.

Can members who joined before I set this up get the roles?

Yes. On the Roles page count the members, then start it. Each member gets what their own join date says, and roles still to come are scheduled.

Where does the quest show up?

It is posted when a member joins, in the quest channel, and any member can see their own progress with /quests list.

Can it thank members who boost?

Yes. Turn on the boost message on the Messages page. It thanks a member when they start boosting and for every boost Discord announces, or only for first boosts. It can also give a boost role that is taken away when they stop boosting. Discord's own boost notice can be deleted once the thank-you is posted.

Why did the shared bot not send my greeting?

When saved text looks like invite spam or a scam, the shared bot holds it until you change it. The Messages page shows what was held and why, and /welcome test says so too. A custom bot never holds your text.