여러 개의 봇에서 YourBot 하나로.

Open the dashboard, pick your server and go to Services. Flip the service's switch to ON. It takes effect without you restarting anything; on a custom bot, YourBot restarts the bot for you. Open then takes you to its settings page. The ten services are free on every server. Marketplace plugins are installed from the Marketplace instead and need Premium and a custom bot on that server.

Premium is YourBot's paid plan, billed per server, monthly or yearly. On top of the Free plan it adds:

• a custom bot with your own name, avatar and presence
• the plugin marketplace (marketplace plugins run on your custom bot)
• the Plugin Builder, for your whole account while you hold a Premium subscription (each build is still paid from AI credits)
• 50 free lifetime Start Your Server designs, counted per server and per account (a second Premium server does not add another 50 for you)
• premium support

The ten services are the same on both plans. Buy it on Buy Subscription; the current price is on Pricing.

On the Account page, click Open billing portal (or Manage on the subscription) and cancel in Stripe's portal. Cancellation takes effect at the end of the current billing period and you keep Premium until then. Meanwhile the subscription shows Canceling with a Resume subscription button if you change your mind. You can also cancel by emailing support@emberstreamstudio.com. There are no refunds for partial billing periods unless the law requires one.

First make sure a Premium subscription is assigned to the server. In the Discord Developer Portal (discord.com/developers/applications), click New Application, give it a name and click Create. On its Bot page, turn on Server Members Intent and Message Content Intent and click Save Changes; setup refuses the token without both. Presence Intent is optional: turn it on if you want Group Finder game pings or Analytics activity tracking, then tick Request the Presence Intent on Bot Settings and restart the bot. Then click Reset Token and copy the token. Paste it under Enable Custom Bot on Bot Settings, then use + Invite to Server to add your bot. Bot Settings has a Setup Guide and a Video Guide that walk through each step.

The Free plan costs nothing. Premium is billed per server, monthly or yearly: choose on Buy Subscription, pick how many additional servers you want, pay through Stripe Checkout, then assign the subscription to your servers on the Account page. The first server is included and each additional server is a small add-on on the same subscription. The current prices are on Pricing. Marketplace plugins are priced separately by their developers.

Analytics counts activity in your server: messages, voice sessions, joins and leaves, reactions and threads. It turns those counts into trends, cohort retention, heatmaps, leaderboards, role rewards, alerts and counter channels on the Analytics pages at /p/analytics/. Members can pull up numbers in Discord with /stats, /me, /leaderboard, /top, /server and /chart. It stores who posted, where and when, never the message text.

Check Status first; a platform problem shows there. Then open the Bot page for your server. On the shared bot the badge reads In this server or Not invited. Not invited means the bot was removed, so use + Invite to Server. On a custom bot the badge reads Running, Stopped or Crashed: a stopped bot comes back with Start Bot, and a crashed one is restarted automatically after a short wait. After 5 crashes in a row, or straight away if Discord rejects the token or the bot's intents are switched off, it is quarantined and the server falls back to the shared bot, so the Bot page shows the shared bot. The Account page marks your bot Quarantined. Fix the cause (for a rejected token, get a new one with Reset Token in the Developer Portal), then paste the token under Enable Custom Bot on the Bot page, which clears the quarantine and restarts the bot.

Stored: the settings you save for each service, a record of who is in each server with their usernames (kept to detect ban evasion), message metadata for Analytics (who posted, in which channel and when, never the text), member join and leave events, voice session times, an audit log of admin actions and billing records from Stripe (never card numbers). Message text is stored only by features that need it: ticket transcripts, the messages attached to a Sentinel case, excerpts of what a Sentinel check of old messages matches and Sentinel's message log of deleted and edited messages (part of Sentinel's recommended protection, kept 30 days by default). While the message log is on, Sentinel also keeps a copy of each new message for 72 hours so it can log what a deleted or edited message said. Online counts and members' game activity are recorded only if you turn on Status tracking or Activity tracking in Analytics settings. Server data is tagged with its server, and the core tables also enforce row-level security per server.

Open the Developer Portal and click + New Plugin. Enter a Display Name and a one-sentence Summary (a description and a GitHub repository URL are optional), then click Create Plugin. The first time, you're asked to accept the Developer Agreement. You don't choose a plugin ID: the platform assigns one and shows it under Identifiers on the plugin's Settings tab. Then add code on the Versions tab with Pull from GitHub or Upload a zip, try it on a server with Test and click Submit to send it to staff review. To have the code written from a description instead, use the Plugin Builder.

When you click Submit on a version, it joins the review queue and shows as in review on your Versions tab, with the time staff aim to decide by. A reviewer reads your source alongside the automated scan findings, which include how your requested capabilities and domains line up with the code, then publishes the version or rejects it with notes. Either way you get a dashboard notification and a Discord DM. Every version you list on the marketplace goes through this queue unless you have trusted developer status, and versions from a private repo always do.

Open Earnings and click Connect Stripe, which takes you through Stripe's own onboarding for a Stripe Express account. You need that account connected with charges enabled before you can create a paid plan or publish a plugin that has one; free plugins don't need Stripe. EmberStream, the company behind YourBot, is the merchant of record: when a buyer pays, your share goes straight to your Stripe account and Stripe pays it out to your bank automatically. The platform fee starts at 30% and drops as your sales over the last 30 days grow, down to 15%. The Earnings page shows your current fee tier.

Each plugin has a per-minute limit on outbound HTTP requests on each server it's installed on, metered as a token bucket. A request over the limit fails and the SDK raises RateLimitError. If your plugin needs more, ask YourBot staff (the /support command in Discord links to the support server). Staff can raise the limit for your plugin, but it can't go below the default.

On Services, click Uninstall on the plugin's card (marked Marketplace). The plugin's marketplace page has an Uninstall button too. You need Manager access on the server. The plugin stops running there and its key-value data is deleted at once. If it keeps SQL tables, YourBot holds them for 7 days and they come back if you reinstall within that time (unless the plugin deletes them itself on uninstall); after that they are deleted. Uninstalling doesn't cancel a paid subscription: cancel it with Manage on Plugin Licenses.

On Bot Settings, paste it into Bot Token under Enable Custom Bot and click Enable Custom Bot. Once your custom bot is running, a new token goes in New Bot Token under Token Management, then Update Token. The token is encrypted with a key tied to your server and is never shown on the page again. Process logs redact it too. Saving a token restarts your bot with it automatically. A Premium subscription has to be assigned to the server before a token can be saved.

While Stripe retries a failed renewal, your Premium subscription is past due and your custom bot keeps running. Premium ends when the subscription is canceled: when a cancellation reaches the end of its billing period, or when Stripe gives up on a failed payment and cancels it. Then your custom bot stops and the server goes back to the shared bot. Marketplace plugins stop too, because they only run on a custom bot, and paid plugin licenses bought on that subscription are canceled. The ten services keep running on the shared bot and your settings and data stay. To come back, subscribe again, assign it to the server and click Turn my custom bot back on on Bot Settings; your saved token is still there. For 7 days after your last billing period ends, the server keeps any unused free Start Your Server designs. That grace does not keep the custom bot or marketplace plugins running.

With your server selected in the dashboard, open Services and switch Analytics on (this needs manager access). Click Open on the card: until setup has run, managers land on /p/analytics/setup, where Run setup creates a private #analytics-alerts channel (or reuses a text channel with analytics in its name), keeps bots out of the counts, adds an activity-drop alert if you have none and starts importing message history. New messages, voice sessions, joins and leaves are counted from the moment the service is on.

The import reaches back up to 365 days, never past the Keep data for limit shown on the Settings page. Setup raises Keep data for to match so the import is kept. Raw detail older than your Keep data for window is removed every night. If you later run Import history under History, set Keep data for at least as long as the import first.

Missing commands usually mean the bot was added without permission to create commands. Authorize it again, which keeps it in your server: the shared bot through the invite link, a custom bot through + Invite to Server on the Bot page. On a custom bot, then press Re-sync commands on the Bot page; the Commands line under Health shows whether the last sync worked. Duplicates usually mean two bots: on a server that runs a custom bot, the shared YourBot bot's commands only reply that the server uses a custom bot, so you can remove the shared bot from the server while your custom bot is running. If the list still looks stale, press Ctrl+R in Discord on desktop to reload it.

• Server data (service settings, tickets, transcripts and moderation cases): kept while the bot is in your server. Owners and managers can delete tickets and cases sooner with Data Management in Tickets settings or Delete old records in Sentinel settings. After the shared bot leaves, a nightly job deletes the server's settings and most of its data 30 days later.
• Analytics raw activity (messages, voice, joins and reactions): 90 days by default. Choose 30, 90, 180 or 365 days under Keep data for in Analytics settings, up to the limit that page shows; Analytics setup raises it to cover the history it imports. Older rows are pruned nightly while Analytics is on. Hourly and per-member daily summaries are kept for twice that window; each member's all-time message and voice totals are kept as long as the server's data.
• Sentinel message text (the message log of deleted and edited messages plus messages saved with a case): 30 days by default, adjustable up to 365. A short excerpt of the message that triggered a case stays with the case.
• Admin audit log: 2 years; it is not removed early when the bot leaves.
• Dashboard sign-in records: 2 years.
• Marketplace plugin crash reports: 90 days.
• Billing records: kept for financial record-keeping.

Your plugin zip needs two files at its root: the entry point __main__.py and manifest.json. The manifest must include:

• id: the plugin ID the platform assigned, shown under Identifiers on your plugin's Settings tab
• name: a human-readable name (the marketplace shows the Plugin Name from the Listing section of your Settings tab)
• version: the platform numbers each version itself and rewrites this field to match when you upload

Optional fields include description, capabilities_required (capabilities_requested is also accepted), slash_commands and proxy_domains_requested. Capabilities and domains your code uses are detected and added on upload. See the developer docs for the full format.

Two layers run on every version you upload or pull.

• At upload, a zip is refused if any .py file contains eval(, exec(, os.system, os.popen, pty.spawn, import subprocess, __import__, pickle.loads or marshal.loads. import socket, import ctypes and importlib are allowed but flag the version for review. So does any other upload warning, such as a manifest version the platform had to correct or capabilities it had to add.
• The full scan then records findings rated info, warn or high, plus a risk score. It looks for hidden or generated code (base64 payloads, names built from strings, reflection lookups, compile), foreign function interfaces, anti-debugging, network access that bypasses the proxy, reads of sensitive environment variables or files, hard-coded secrets (Discord tokens and webhook URLs, GitHub, AWS, Stripe and OpenAI keys, private keys and random-looking strings) and mismatches between manifest.json and what the code uses.

Reviewers see the findings next to your source. Publish privately has no reviewer, so a flagged version or a high risk score blocks it there.

Payouts are automatic, so there's nothing to request. Your share of each sale is transferred to your Stripe account when the buyer is charged, then Stripe holds it for about 30 days before paying it to your bank on a daily schedule. If a sale is refunded or disputed, your share of that charge is reversed. Earnings shows your balance, what is still in the hold window and estimated release dates; Stripe sets the exact bank dates.

Each marketplace plugin runs in its own Docker container with these defaults:

• 64 MB of memory with no swap and a capped share of CPU
• at most 64 processes
• no network access of its own (outbound HTTP goes through the proxy with the proxy:http capability, and WebSockets through the platform broker with proxy:websocket)
• a read-only filesystem apart from a 16 MB /tmp that can't run programs
• a non-root user (UID 65534), all Linux capabilities dropped, no privilege escalation and a seccomp system-call filter

If it crashes or runs out of memory, the runner restarts it after a short delay that doubles each time. Five crashes within 5 minutes stops it and turns it off on the servers that installed it.

Only the server's owner can ask. With that server selected, use Request Refund on the plugin's marketplace page (give a reason and click Submit Request). You can also click Refund next to the license on Plugin Licenses, with that same server selected. The developer reviews it first; if they don't answer within 7 days it goes to YourBot staff. Staff can also review a developer's denial. An approved refund returns the most recent charge for the plugin in full to your original payment method and ends the license. For a subscription, also cancel it with Manage on Plugin Licenses so it doesn't renew. If a request is denied you can ask again after 30 days. Plugins bought in a bundle are refunded as a whole, so contact support for those.

The fastest way is the YourBot support Discord. In the dashboard, the Help tab on every page opens it. In any server with YourBot, you can also run /support for a private reply with a button to it. Email works too: support@emberstreamstudio.com. Tell us your server name and what you were trying to do. For a bug in a marketplace plugin, /pluginbugreport sends it to that plugin's developer.

The invite asks for every permission the ten services need. It never asks for Administrator; Start Your Server offers a separate Grant Administrator link only when a design uses locked channels or Community mode. You can untick permissions on Discord's invite screen or trim the bot's role later, as long as your enabled services keep what they need. For example, Voice Channels and Tickets need Manage Channels and Welcome needs Manage Roles for auto-roles. Every service that posts needs Send Messages and Embed Links. If a service is missing a permission, its dashboard page shows a banner naming it, with a Fix with one click link. To check every service you have on at once, down to each channel and role it uses, run the Setup Check on the Bot page or /yourbot check in Discord. Privileged intents are set on the bot's Discord application, so there is nothing to switch on in your server settings.

The ten services work the same on both. The shared bot comes with the Free plan. There is nothing to set up and it runs under the YourBot name and avatar. A server with an active Premium subscription can give the shared bot its own picture, banner and about me in that server only, under How the Bot Looks in This Server on the Bot page. A custom bot needs Premium. It runs as its own bot with your name, avatar and presence. It is also the only way to run marketplace plugins. Choose the shared bot if the bot's identity does not matter to you. Choose a custom bot if you want your community's branding or marketplace plugins.

Most servers keep the defaults. The settings that matter are on the Analytics Settings page:

• Leave bots out: on by default (recommended); switch it off to count bot activity.
• Channels to leave out and Roles to leave out: activity in those channels, or from members with those roles, is not recorded.
• Keep data for: 30, 90, 180 or 365 days, 90 to start. Older detail is removed every night.
• Time zone: follows the server time zone unless you pick another zone.
• Status tracking and Activity tracking: off by default, and they only switch on when the bot has the Presence Intent.

Role rewards have their own Role rewards page at /p/analytics/rewards, where a reward grants a role to members who match its conditions (up to 8, matched all together or any one).

When a switch flips back, the page shows a short message. For the ten built-in services it is usually one of two things: switching too fast (the page accepts 15 switches a minute, so wait a moment) or an expired session (reload the page and try again). Built-in services don't need a subscription. Marketplace plugins have extra requirements, and the message names the missing one: a subscription on the server, a custom bot token or a license for a paid plugin. Still stuck? Ask in the support server with the service name and your server ID.

There is no delete button in the dashboard; our team handles deletion. Email legal@emberstreamstudio.com (the privacy contact in the Privacy Policy) or ask in the support server. We may ask for your Discord user ID to verify the request, and we respond within 30 days. The erase deletes your analytics activity, dashboard sign-in history, notifications, appeals and saved payment details. It also removes your name from membership records. We keep what abuse prevention and the law need: any platform sanction (with its notes scrubbed), a bare record of the servers the account joined, plus billing and credit records. Data a server keeps about its members, such as tickets and moderation cases, is controlled by that server's administrators.

When you upload a zip or pull from GitHub, the platform scans your code for SDK calls and adds any capability they need that your manifest left out. For example, ctx.http.get() adds proxy:http and ctx.kv.set() adds storage:kv. Some manifest fields imply a capability too: listing proxy domains adds proxy:http and declaring slash commands adds interaction:respond. Web addresses written as strings in your code are added to your proxy domains the same way. On the Versions tab, hover the capability count on a version (or open where?) to see which file and line each detected capability came from. Detection matches calls written out in the source, so declare anything your code reaches another way.

Look at the version's row on the Versions tab. There are three different stops:

• The upload was refused. The zip failed a check, for example a blocked call such as eval( or import subprocess, no __main__.py in the zip or an unsafe path or symlink. The error names the file. Fix it and upload or pull again.
• The row shows errors. The validator found problems that stop Submit, such as a manifest.json id that doesn't match your plugin ID, a capability your code uses that isn't requested or a slash command with no matching handler. Each error names the file and a fix. Warnings don't block you.
• It says rejected. A reviewer turned it down. Their notes are in your notifications (and on the row when it has no validator warnings). Upload or pull the fix and submit it again.

Buyers ask for refunds from the plugin's marketplace page or their Plugin Licenses page. Each request appears on Refund Requests and your plugin's Refunds tab, and you get a notification and a Discord DM. You have 7 days to approve or deny it before it goes to YourBot staff to decide. If you approve, YourBot staff give it a final review and issue the refund. Staff can also review a request you denied. When a charge is refunded, your share of it is reversed from your Stripe account. Refund requests aren't limited to a set number of days after purchase.

KV (ctx.kv, capability storage:kv) stores key-value pairs for fast lookups such as settings, flags, counters and dedup tokens. Each value can be up to 64 KB, with up to 50,000 keys per server. SQL (ctx.sql, capability storage:sql) gives your plugin its own Postgres schema on each server, where you can create tables and indexes and run SELECT, INSERT, UPDATE and DELETE. It allows up to 100 tables, returns at most 1,000 rows per query and limits schema changes to 20 an hour. Both are kept separate per plugin and per server, so a plugin can never read another server's data or another plugin's.

Your Premium subscription is marked past due and your custom bot keeps running while Stripe retries the charge. You also get a Payment failed alert in your YourBot messages. On the Account page the subscription shows Past due: click Update payment method on it to change your card in Stripe's billing portal. If Stripe cannot collect the payment and cancels the subscription, it ends: your custom bot stops, the server moves to the shared bot and marketplace plugins stop with it. The ten services, your settings and your data stay.

It depends on what happened:

• Delisted: the plugin leaves the marketplace and takes no new installs, but servers that already have it keep running it. Its developer can delist it too, with the same effect.
• Suspended (disabled for safety): staff switch it off on every server at once, and whoever installed it gets a notification with the reason. It can't be switched back on while suspended. When staff lift the suspension, it stays off until you turn it back on.
• Banned: it's switched off on every server and can't be turned back on.

A plugin that keeps crashing is also turned off automatically, and its page says why. If you paid for a plugin that can no longer run, request a refund from its marketplace page or Plugin Licenses.

Click Login with Discord in the dashboard or Sign in on the website. You can also go straight to /login. Discord asks you to authorize YourBot the first time and then sends you back signed in. YourBot never sees your Discord password. The login shares your Discord profile (user ID, username and avatar) and the list of servers you are in. The dashboard shows the ones you own or can manage, plus any you were given access to.

To switch to custom, assign a Premium subscription to the server, then paste your bot token under Enable Custom Bot on Bot Settings. If you set one up before, click Turn my custom bot back on instead. To switch back, click Switch to Shared Bot in the Danger Zone on the same page. That stops your custom bot and the marketplace plugins that need it, keeps your token saved and hands the server to the shared bot. If the shared bot is not in the server, Bot Settings shows + Invite to Server. Service settings and data stay as they are.

The bot needs View Channel, Send Messages, Embed Links and Manage Roles. Manage Roles is for role rewards, and the bot's own role has to sit above any reward role; the Role rewards page warns you when it doesn't. If the bot's role is missing one of these, the Analytics pages show a banner that lists them with a Fix with one click link. Joins and leaves rely on Discord's Server Members Intent: YourBot requests it, and on a custom bot you switch it on in the Discord Developer Portal. Status tracking and Activity tracking also need the Presence Intent.

Check three things. Join-to-Create Voice Channels must be switched on in Services; a lobby does nothing while it is off, and every service is switched off when the shared bot is removed from the server. The channel people join must be one of the service's lobbies. The bot needs Manage Channels to create the room and Move Members to move the person into it, and Manage Channels must not be taken away by an override on the room category. The service page shows a banner with Fix with one click when a server-wide permission is missing, but a category or channel override has to be fixed in Discord. To find one, run the Setup Check on the Bot page or /yourbot check in Discord: it checks the bot's permissions in each lobby and room category. A full category (Discord allows 50 channels in one) does not block rooms: they go to your Fallback category or the lobby's own category, and managers get a notice.

The dashboard gives people one of three roles on a server: Owner, Manager or Viewer. The Change history page (Change history in the sidebar) lists the changes made on the server's dashboard: who made each one, when and what they changed. Owners see every change. Managers see changes on the pages their manager permissions let them read: Services and Marketplace by default, plus Bot Settings if you give them that page. Changes to dashboard access and Start Your Server builds are for owners only, and Viewers can't open the page. Recent Access Activity on the Access page (people added, removed or given a new role) is shown to owners, and Recent Activity on the Bot page to whoever can open that page, owners by default. Service histories, such as Sentinel cases and the Group Finder audit log, are open to anyone with a dashboard role on the server, Viewer included. The Privacy Policy limits YourBot staff access to running and supporting the service and says that access is logged.

Yes. Put the repo in Repository URL in the Listing section of your plugin's Settings tab, and set Repo visibility under Source & auto-deploy (a private repo also needs a GitHub token). Then you have two ways to ship from it:

• In the Pull from GitHub card on the Versions tab, enter a branch, tag or commit (main by default) and click Pull. You then confirm the capabilities it detected, and the version shows the commit it came from.
• CI/CD Auto-Deploy on the Settings tab: tick Enabled, pick the branch (main by default) and click Save. Add the webhook URL and secret it shows in GitHub under Settings → Webhooks, with content type application/json and just the push event. Every push to that branch then creates a new version and submits it for review. For trusted developers with a public repo, that version can publish without waiting for review.

Each install has an auto-update setting, on by default. When a new version is published, enabled installs with it on move to that version straight away. A release never moves an install to an older version. If the new version asks for capabilities or proxy domains a server hasn't approved, that server is skipped: its owners and managers get a notification, and nothing changes until they review and approve the new permissions on the plugin's marketplace page. With auto-update off, the plugin page shows Update available with a button to update, and choosing a different version there with Switch turns auto-update off.

Open your plugin's Pricing tab and use Add Plan. A plan is either a Subscription (Monthly or Yearly, with an optional free trial of up to 14 days) or a One-Time Purchase. You set the price in US dollars and how many servers one license covers (1 to 10). A plugin can have up to 5 plans. Paid plans need your Stripe account connected first (Earnings, Connect Stripe). A plugin with no plans is free to install. Subscribers can later move to another subscription plan under Change plan on the plugin's page, and Stripe prorates the difference; one-time purchases can't be switched.

Open your plugin in the Developer Portal. The Crashes tab lists your plugin's Python tracebacks (newest first) and Logs holds everything else, including your ctx.log output and calls the platform refused (you can filter by the capability that was denied). Common causes:

• a capability the server didn't grant, which makes the SDK raise CapabilityError (since SDK 0.10.1 refused calls also leave a warning in Logs, up to three per method an hour)
• running out of the 64 MB memory limit
• an unhandled exception in a handler

After a crash the runner restarts the plugin after a delay that doubles each time. Five crashes within 5 minutes stops it and turns it off on the servers that installed it. Their owners and managers get a notification saying so.

On the Account page, click Open billing portal in the Billing panel. It opens Stripe's billing portal, where your invoices, payment methods and cancellation live. The Billing panel itself also lists your recent payments.

Open the Marketplace. You can search, browse by category and filter by free or paid, billing type (one-time, monthly or yearly), minimum rating, free trial or on sale, then sort by popularity, rating, newest or price. Each plugin's page shows the developer, reviews, plans and prices, the commands it adds and the capabilities it asks for. Pick your server under Installing to, then install it (paid plugins need a plan bought first). Installing needs Premium and a custom bot on that server, and the page walks you through any missing step.

Open your server list (Overview in the sidebar) and click the server you want. From then on every dashboard page, such as Services, Access and Bot Settings, works on that server until you pick another one. The choice is saved in your login session, so it applies to every tab in the same browser.

Bot Settings shows your custom bot's live state (Running, Stopped or Crashed) along with uptime, gateway latency and whether its commands synced. If the process crashes, the orchestrator restarts it with increasing delays between tries. After repeated crashes it is quarantined: the server falls back to the shared bot and the Account page marks the bot Quarantined. If Discord rejects the token, for example after you reset it in the Developer Portal, the bot is quarantined straight away. To bring it back, fix the cause, then paste the bot's token (a new one if you reset it) under Enable Custom Bot on that server's Bot Settings, which clears the quarantine and restarts the bot. The Status page shows platform-wide health.

The usual causes, all on the Analytics Settings page:

• Channels to leave out or Roles to leave out cover more than you meant. Threads and forum posts inside a channel left out are skipped too.
• Leave bots out is on by default, so bot messages are not counted. Switch it off if you want them.
• Only regular messages and replies count. Join, boost and pin notices do not.
• Messages from before Analytics was switched on only appear after an import: use Import history under History.
• Raw detail older than your Keep data for window is deleted every night (chart rollups are kept for twice that window), so a long range can show less than you expect.

Discord only lets a bot give or remove roles that sit below its own highest role, and it can't kick, ban or time out a member whose highest role is at or above the bot's. In Discord, go to Server Settings > Roles and drag the bot's role above every role it hands out, such as Welcome auto-roles, Analytics role rewards, Giveaways winner roles and Sentinel's quarantine role. Then retry the action. The bot also needs the Manage Roles permission. Most service pages show a banner with Fix with one click when it is missing; for Giveaways winner roles, check the bot's role in Server Settings > Roles yourself. The Setup Check on the Bot page, or /yourbot check in Discord, names each role your services hand out that sits above the bot's.

Not as one file. These services export their own data from their dashboard pages:

• Analytics: Download CSV in the chart menus on its pages, plus Messages and Voice CSV downloads on its Sharing page.
• Sentinel Moderation: Export CSV on the Cases and Messages tabs of History.
• Beacon Events: Export CSV on each event and a CSV of each poll's votes.
• Giveaways: Participants CSV on each giveaway.
• Tickets: download any transcript as HTML or TXT, export ticket analytics as CSV or JSON and download the Tickets configuration as JSON.

For a copy of the personal data we hold about your own account, email legal@emberstreamstudio.com, the contact in the Privacy Policy; staff can produce a JSON export of it.

On your plugin's Settings tab, under Source & auto-deploy, set Repo visibility to Private and click Save visibility. In GitHub, create a fine-grained personal access token limited to that one repository with Contents: read. Paste it under GitHub Personal Access Token and click Save PAT. It's stored encrypted and never shown back to you. Then click Pull in the Pull from GitHub card on the Versions tab: if a new draft version appears, the link works. Until a PAT is saved, you can't submit versions from a private repo (and pulls fail too unless the GitHub App is linked). Versions from a private repo always go through staff review.

Trusted developer is a status that YourBot staff grant by hand and can take away. For a trusted developer, submitting a version (including an auto-deploy push) publishes it immediately instead of queueing it, but only when the plugin's Repo visibility is Public. A zip upload or Versions-tab pull that raised any upload warning (for example a risky import such as socket, a manifest version the platform had to correct or capabilities it had to add) still goes to the queue, as does any version whose dashboard changed since the last published one. Plugins with a private repo are reviewed every time. The upload checks and the pre-submit validator apply to everyone.

On your plugin's Overview tab, pick a version and a server and click Dev Install (the Test button on the Versions tab does the same). Dev installs are free and skip both review and the subscription check. They get every capability the plugin asks for automatically. The rules:

• only you (the plugin's owner) can create one, on a server where you have the Manager role
• the server must have the YourBot Dev bot in it (the Overview tab offers an invite if it's missing)
• each dev install lasts 24 hours and you can have 3 at a time
• a server that already has the plugin from the marketplace can't take a dev install

Uploading a new zip moves your active dev installs to it automatically and restarts their 24 hours. After a GitHub pull, or once a dev install has expired, dev-install the new version.

The Free plan works on every server you add YourBot to. Premium is per server: a subscription includes one server, and each additional server is an add-on on the same subscription, priced on Pricing. Choose additional servers when you buy, or later with Add a server on the Account page, then assign each seat to a server. Each seat runs its own custom bot: after assigning a server, open that server's Bot Settings and add its token, and use a different bot application for each seat. Adding a server part-way through a period is charged for the rest of that period, right away for larger amounts and on the next invoice for small ones. Removing a seat takes effect at the end of the billing period: the seat stays yours until then and nothing is refunded for the rest of the period. You can also buy a separate subscription with Buy more. Marketplace plugins are priced by their developers; some plugin plans cover more than one server.

Developers can attach up to 5 plans to one plugin. Each plan is either a subscription (monthly or yearly, sometimes with a free trial) or a one-time purchase. A plan can also cover more than one server per license. If you're on a subscription, use Change plan on the plugin's page to move to another subscription plan; Stripe prorates the switch. One-time purchases can't be switched, so a different plan is a separate purchase.

Each service has its own settings page at /p/ followed by the service id, for example Tickets, Sentinel moderation and Voice Channels. The Services page is where you switch services on and off. Once a service is on, its Open button takes you to its page and the sidebar lists it under your server name. A service's page only opens while that service is switched on.

Yes. On Bot Settings, click Restart under Process Control. The running process is asked to shut down cleanly and is only forced if it does not exit, then a fresh one starts. Your settings and data are stored by YourBot, not inside the bot process, so a restart is safe at any time. If the bot is stopped, the same panel shows Start Bot instead.

Scheduled Announcements posts a message to a channel at a time you pick: once, every day, on chosen weekdays or on a day of the month. Each announcement fires in its own time zone, which starts as your server timezone. If the bot was offline when a post was due, it goes out once as soon as the bot is back and the schedule carries on. Manage everything from the calendar at /p/announcements/, or use /announce now, /announce list and /announce cancel in Discord (staff only, unless you allow more roles on the Commands page).

Only for a custom bot. The shared YourBot bot already has the Server Members and Message Content intents. A custom bot needs both switched on in the Discord Developer Portal: open your application's Bot section and find Privileged Gateway Intents. YourBot won't save a token whose application is missing either one. A custom bot that loses them stops and is quarantined: the server falls back to the shared bot and the Account page marks your bot Quarantined. Switch them back on, then paste the bot's token (or a new one from Reset Token) under Enable Custom Bot on the Bot page, which clears the quarantine and restarts it. Presence is optional. Message text is read for Sentinel's filters, ticket transcripts and command handling. It is stored only by the features that keep it.

Every zip upload or GitHub pull creates a version and the platform assigns its number. If your newest version is still a draft or was rejected, the upload replaces it instead of adding another.

• draft: the validator has run and any errors or warnings are on the version row. Try it on a server with Test.
• in review: you clicked Submit. The row shows when staff aim to decide, and Retract takes it back to draft.
• published: it's live. Installs with auto-update on move to it, except on servers that must first approve new permissions.
• rejected: staff sent it back with notes. Upload or pull the fix (it replaces the rejected version) and submit it again.

For trusted developers with a public repo, Submit publishes straight away unless the version was flagged or changes the dashboard.

Yes. Marketplace plugins run on your server's own custom bot, never on the shared YourBot bot. To install one, the server needs an active Premium subscription assigned to it and a custom bot set up on Bot settings, with its token saved and the bot turned on. If either is missing, the plugin's page shows Finish setup to install with a link for that step. You also need the Manager role on the server. Paid plugins are priced by their developers and billed separately from Premium; see Pricing for Premium itself.

The current SDK is yourbot-sdk 0.10.1. Install it with pip install yourbot-sdk (Python 3.10 or newer). It includes the yourbot command line tool: yourbot new or yourbot init scaffolds a plugin, yourbot dev runs it locally against a mock host, yourbot validate runs the same pre-submit checks the platform runs and yourbot doctor checks your setup. You don't ship the SDK with your plugin: the sandbox installs the version the platform pins and ignores any SDK line in your requirements.txt. The developer docs show the SDK version the platform runs.

Yes. On your plugin's Overview tab, click Switch to private, which takes it off the marketplace and turns off any installs made by other people (you can't switch while it has active paid subscriptions). Then use Publish privately on a version in the Versions tab. A private version skips staff review, never appears in the marketplace and only you can install it, on a small number of servers (3 by default). Because no reviewer sees it, a version with any upload warning or a high scanner risk score can't be published this way. The servers still need Premium and a custom bot. Switching back to public returns self-published versions to draft, so listing the plugin goes through normal review.

Yes. The chart menu on each Analytics page has Download CSV, which downloads what you are looking at with its current filters: Home, Growth (with Download week by week (CSV) for the weekly cohorts), the Chat, Voice, Online and Playing tabs of Activity, Best times, Channels, Members, Counters, Alerts and the Markers card in Settings, plus the member and channel side panels. The Sharing page also has Messages CSV and Voice CSV for the last 7 to 365 days. For a live feed into your own tools, a manager can create a key under Developers on the Sharing page and send it as a Bearer token to the endpoints under /api/v1/analytics/<server id>/ (series, tops, sums, counts and resources). Up to 5 keys can be active per server. Each key is shown only once and is limited to 60 requests a minute.

The bot joins with every service switched off, so nothing posts, moderates or greets members until you turn it on. Whoever added it gets a welcome message by DM (the server owner gets it instead if that fails, and it is posted in a channel if both have DMs closed). Pick services from its Pick the services you want menu, then choose Set them up for me to run their setup from Discord or Set up in the dashboard to just switch them on. Its Open the dashboard button opens the dashboard on that server. Members with Administrator in Discord get manager access to the dashboard automatically; you can change that under Discord Permission Sync on the Access page. You can switch services on at any time on the Services page.

Yes. Open the Account page and find the subscription's card. Its server list shows servers you own, and a server that already has a subscription has to be unassigned first.

• Subscription for one server: pick the new server and click Assign. The subscription moves. Marketplace plugin subscriptions you bought for the old server while it had this subscription move with it, ready to install on the new server from the Marketplace. One-time plugin purchases stay with the old server.
• Subscription for several servers: click Release next to the server you are leaving, then pick the new server and click Assign. Plugin licenses stay with the server you released.

The server you leave goes back to the shared bot and keeps its settings and data. Moving does not change your billing. On the new server, open Bot Settings, paste your bot token under Enable Custom Bot and invite the bot. If it says the bot is already the custom bot of your old server, wait a few minutes and try again.

With your server selected, open Services, switch Scheduled Announcements on (manager access needed) and click Open to reach /p/announcements/. Click + New Announcement, or a day on the calendar, then pick a channel, write the message (Discord markdown, optional embeds), choose when it fires and click Schedule. The optional Setup page at /p/announcements/setup finds an #announcements, #announcement or #news channel, or creates #announcements that members can read but not post in. For a quick one-off from Discord, run /announce now with a channel and a message (it needs Manage Server or a role allowed on the Commands page); it posts within about 30 seconds.

It depends where you see it. In Discord, YourBot queues the bot's actions. When Discord answers with a rate limit, the action waits as long as Discord asks (up to 30 seconds) and is retried, so a short burst is delayed rather than lost. In the dashboard, That was tried too many times just now (or Toggling too fast on the Services page) means you hit the page's own limit for that action; wait a minute and try again. A command reply saying This command is on cooldown comes from the cooldown set for that command on the service's Commands page, which an owner or manager can change.

There is one paid plan, Premium, so downgrading means canceling it and going back to the Free plan. Cancel from Open billing portal on the Account page. Premium stays active until the end of the period you paid for. Then your custom bot stops, the server moves to the shared bot and marketplace plugins stop, while the ten services keep running with your settings and data.

Remove the shared bot from your server. Its services switch off at once, and a nightly job permanently deletes the server's settings and most of its data 30 days later (re-inviting it before then keeps everything). On a server that runs a custom bot, removing the bot does not start this. You can also clear some data yourself: Data Management in Tickets settings and Delete old records in Sentinel settings delete old tickets, transcripts and moderation cases, and Analytics settings sets how many days of raw activity to keep (30, 90, 180 or 365). Some records outlast the purge, including the bare record of which accounts were members (names removed), financial records and the admin audit log (2-year window). To have your server's data deleted sooner or in full, email legal@emberstreamstudio.com, the contact in the Privacy Policy.

The Plugin Builder writes a marketplace plugin from a description. It can first draft a plan of the commands, storage, events, scheduled jobs and any dashboard pages for you to approve (or you can skip straight to the build), then it writes the code and checks it with the same validator as a normal upload. The Plugin Builder is part of Premium: your account needs an active Premium subscription to build. Each run is paid from prepaid AI credits from AI Credits. Each plan costs a small amount. Each build holds its worst-case cost up front, charges only the tokens it actually uses and returns the rest. The result is an ordinary plugin in your Developer Portal. You can test it with a Dev Install; to run it for real, publish it and install it on a server that has Premium and a custom bot, like any marketplace plugin.

Not directly. Each plugin's container has no network access at all. The only ways out are YourBot's HTTP proxy and its WebSocket relay, and only if you granted the plugin the proxy:http or proxy:websocket capability. Even then it can reach only the domains you approved when installing it (and their subdomains), plus any exact address a server admin or a YourBot manager on your server added through the plugin's own setup. The proxy blocks private and internal addresses and rate-limits each plugin on each server.

Everything is set per announcement on the New Announcement form:

• Recurrence: Once (specific date/time), Every day, Weekly (pick weekdays) or Monthly (pick day of month). Monthly takes a day from 1 to 31 or Last day of month, and a day past the end of a short month moves to its last day.
• Timezone: any IANA zone name, filled in with your server timezone (UTC until you set one on the Bot page).
• End date (optional) and Max occurrences (optional) stop a repeating post on their own.
• Mentions: Allow role mentions is on by default, Allow @everyone / @here is off.
• Embeds (advanced, optional): raw Discord embed JSON, up to 10.

A message can be up to 2,000 characters, and a server can hold up to 100 pending announcements.

Re-invite it within 30 days and your data is still there. On Servers the server now shows Not installed; use Invite bot there or + Invite to Server on the Bot page. When the shared bot leaves, YourBot switches every service and marketplace plugin off but keeps their settings and history, so after the re-invite switch the services you use back on in Services. If a custom bot was kicked, its settings and services stay as they were: Servers shows Bot missing, so use Re-invite there or + Invite to Server on the Bot page. If the shared bot is not back within 30 days, a nightly job permanently deletes the server's settings and most of its data. Discord also takes away the bot's access to private channels when it is kicked, so check its log and ticket channels after re-inviting.

AI credits are a prepaid balance on your YourBot account. They pay for Start Your Server designs beyond any free ones and for Plugin Builder runs. Buy a credit pack on the AI Credits page, which checks out through Stripe and shows your balance and what each build spent. Your balance also shows in the Billing panel on the Account page. Credits are separate from Premium: a subscription includes no credits. It adds 50 free Start Your Server designs, and the Plugin Builder needs it, with each build still paid from credits.

The bot needs View Channel, Send Messages and Embed Links in each channel it posts to, plus Pin Messages so the setup wizard can pin its guide. Before every post the bot checks that the channel still exists and that it can reach it. If not, the announcement is flagged on the Announcements page and the server's owner and managers get a dashboard notification, at most once a month for the same channel and problem. A one-time announcement moves to Failed; a repeating one skips that slot and keeps its schedule. Edit it, pick a working channel and save to fix it.

Start Your Server designs your Discord server's channels, roles and service setup from a short description of your community, and it applies the plan only after you review it. Each message you send to the designer is one design turn. A Premium server gets 50 free lifetime design turns, counted per server and per account. Other turns are paid from your AI credit balance: the page shows the usual cost before you send, holds the most a turn could cost while it runs and refunds the rest. Server owners open it from Start Your Server in the dashboard sidebar or at /start.

The shared bot's slash commands are registered with Discord for every server at once, so a command can show up while its service is switched off in yours. Switch the service on in Services (the Owner and Manager roles can) and the command works straight away; a custom bot restarts itself to pick it up. If the reply is This command is disabled on this server, the service is on but that command was switched off: open Commands on the service's card and switch it back on. After the shared bot is kicked and re-added, every service starts switched off.

Check the announcement's Timezone first. Each announcement fires in the zone it was saved with, and the form fills that field from your server timezone, which is UTC until you set one on the Bot page. A post saved for late evening in the wrong zone can land on the next or previous day for your members. Changing the server timezone later doesn't move announcements you already saved; open each one, correct the zone and save. Also check the Weekdays boxes: a weekly announcement saved with none ticked runs on Monday. The calendar on /p/announcements/ shows each post in its own zone, so it can look right even when the zone is wrong.

You don't need to kick it first: authorizing the bot again for a server it is already in updates its permissions in place. If a service page shows The bot is missing permissions this service needs, press Fix with one click, which opens Discord's authorize screen for your server. Otherwise use the invite link and pick your server; for a custom bot use + Invite to Server on the Bot page. The link asks for every permission the services use except Administrator. It includes Pin Messages, which Discord split out of Manage Messages, so a bot added before that change needs this once. Keep the boxes ticked; a channel override that denies the bot still applies. Discord only lets someone with Manage Server authorize a bot.

Beacon Events posts an event card with Sign Up, Leave and Options buttons to your announcement channel. Members pick a role, and a class or spec when the event has them; when a role or the event is full, new sign-ups go on a waitlist and the longest-waiting member moves in when a spot opens. Reminders go out in the channel or by DM, and an optional voice channel opens before the start. Attendance feeds each member's reputation, and /poll create adds button polls. Manage it at /p/beacon/ or with /beacon create, /beacon list, /beacon cancel and the other /beacon commands.

Set your server's timezone: on the Bot page, pick one under Server Timezone (it starts at UTC). Schedules, charts, ticket business hours and the times the bot shows follow it, unless a service has its own timezone set in its settings (Analytics, Beacon Events, Giveaways and Tickets business hours each have one), which it keeps. Each scheduled announcement keeps the timezone it was saved with, so open older ones and change it there. The Bot page is open to owners by default.

Only if you tick Allow @everyone / @here on that announcement; it's off by default. Allow role mentions is on by default, so a role written in the message as <@&ROLE_ID> pings its members (if the role is mentionable or the bot has the Mention Everyone permission) unless you untick it, and user mentions always notify. /announce now never pings @everyone or @here.

With your server selected, open Services, switch Beacon Events on (manager access needed) and click Open. Until an announcement channel is set, that opens the setup wizard at /p/beacon/setup: Run Auto-Setup creates and saves #beacon-events (everyone reads, only the bot posts) and a private #event-logs. Then create an event with + New Event on /p/beacon/, or run /beacon create in Discord, which opens a form for the name, description, start time, a participant cap and roles written like Tank:2, Healer:4, DPS:14, Flex.

Discord removes a bot's access to private channels when it is kicked or leaves, and re-adding it doesn't bring that access back. So the private channels YourBot's setup made for it, such as log channels and ticket categories, are hidden from the bot until you fix them. Either give the bot View Channel (and Send Messages where it posts) on those channels again in Discord, or delete them and run the service's setup again; setup notices a channel it can no longer see and creates a new one.

Server-wide settings are in the Settings card on /p/beacon/:

• Announcement Channel ID: where event cards and reminders post.
• Log Channel ID (optional).
• Reminder (minutes before event): the default reminder for new events, 5 to 1,440 minutes, 30 by default.
• Timezone: follows the server timezone unless you pick one; it decides how a time typed without a zone is read.
• Auto Voice Channel: VC Category ID, Pre-create (minutes before event) from 1 to 120 (15 by default) and Restrict to signed-up members only.

Roles and caps, extra reminders (channel or DM), a sign-up deadline and the auto voice switch are set per event in the event editor. There is no switch for the waitlist or reputation: a full role or event always waitlists new sign-ups, and attendance is credited when an event completes.

The bot needs Manage Channels, View Channel, Send Messages, Embed Links, Read Message History and Connect. Manage Channels and Connect are for the voice channel Beacon creates before an event that has auto voice on; without them that channel is never made. The setup wizard also uses Manage Channels to create its channels. If the bot's role is missing any of these, the Beacon Events pages show a banner listing them with a Fix with one click link.

Members sign up with the Sign Up button on the event card, and the bot's private reply says why when it refuses:

• "This event is no longer open" (or "no longer accepting sign-ups"): the event was closed with /beacon close, cancelled or has already completed. Reopen it with /beacon open, or with Recover Event on its dashboard page if it was cancelled or completed.
• "Signups for this event closed N minutes before the start": the event has a sign-up deadline.
• "This event is full! You've been added to the waitlist": the event or the chosen role is full, and the member moves in when a spot opens.

If the card is missing or has no buttons, open the event on the Beacon Events dashboard and click Post to Discord (or Repost to Discord). Also check that the bot can still post in the announcement channel.

Giveaways runs giveaways that members enter with a button, a reaction or both, or as a drop where the first clicks win. Each giveaway can have prize tiers, entry requirements (account age, days in the server, required and excluded roles, a minimum message count from Analytics), extra entries for roles and boosters, entry tasks and referral invites. The draw runs on its own at the end time and rerolls are allowed for 30 minutes afterwards. A public spectator page at /g/<id> shows the live count and an animated draw. Manage it at /p/giveaway/.

Yes. In the dashboard event editor's Finish step, pick Daily, Weekly, Biweekly or Monthly under Recurrence, with an optional End Date. Weekly and biweekly repeats land on the same weekday as the event's own date, and monthly ones on the same day of the month (days after the 28th move to the 28th). Shortly after each event's start time, Beacon marks it completed, creates the next one with the same roles, caps and reminders and posts it to your announcement channel. For a one-off repeat, clone the event instead: /beacon clone takes the event number and a new date and posts the copy right away, while Clone on the event's dashboard page opens the copy in the editor so you can set the date, then click Post to Discord on its page.

With your server selected, open Services, switch Giveaways on (manager access needed) and click Open to reach /p/giveaway/. The Setup page at /p/giveaway/setup has a one-click Run Setup that creates #giveaways if you don't have one, picks a host role by name (falling back to Manage Server) and pins a short how-it-works post. Then click + New Giveaway for the full editor, or run /giveaway create in the channel you want with a title, a duration and a prize for a quick reaction giveaway.

Each giveaway is set up on the New Giveaway form:

• Prize tiers: a rank, a winner count and a prize per tier. Rank 1 is drawn first.
• Entry method: Reaction only (classic), Button only, Both reaction and button or Drop (first to click wins).
• Requirements & weighting: Min account age (days), Min member days, Required roles, Excluded roles and Min messages (counted by Analytics), plus Booster weight (extra entries) and Role weights (extra entries per role), which stack.
• Dedup window (days): anyone who won a giveaway in this server within that many days is left out.
• Allow rerolls, Require winner confirmation and Public spectator page enabled.

Server-wide, the Setup page holds the Timezone, Winner cooldown (days), Bypass roles, Default messages and the Blocked from giveaways list.

The bot needs Add Reactions, View Channel, Send Messages, Embed Links, Read Message History and Pin Messages. Pin Messages is for the how-it-works post the setup wizard pins. Two options need more: referral entries need Create Invite in the giveaway channel and Manage Server to read invite counts, and Auto-grant role to winners needs Manage Roles with the bot's role above that role. If a required permission is missing, the Giveaways pages show a banner listing it with a Fix with one click link.

Almost always because there were fewer eligible entries than winner slots. When the eligible entries can't cover every winner slot across all tiers, the draw doesn't run: the giveaway is cancelled and a "Not enough entries" notice is posted in its channel. (A Drop giveaway instead ends with whoever claimed a slot.) An entry doesn't count if it was disqualified or if the member is below the giveaway's invite-to-win minimum. Members who won a giveaway in this server inside the dedup window or the winner cooldown are left out too. A cancelled giveaway can't be drawn again, so click Duplicate on its dashboard page, lower the winner count or the requirements and publish the copy.

Group Finder is LFG (looking for group) for your server. Members post a listing with a game, party size, optional role slots and a start time, and others join with the Join button or a role picker; a full group takes a waitlist. A listing can stay in your server, be shared with allied servers through networks or go on the public LFG board at /lfg. It also has alert subscriptions, repeating runs, ready checks and a dashboard hub at /p/group_finder/. Members use /group create, /group quick, /group browse and /group join.

Run /giveaway reroll with the giveaway number, or click Reroll on the giveaway's dashboard page. You can choose how many new winners to draw (1 to 50) and which prize tier by rank. A reroll only works on a completed giveaway with Allow rerolls on and only within 30 minutes of the draw. It leaves out everyone who has already won that giveaway. If you use Require winner confirmation and a winner doesn't claim in time, that slot gets its own Reroll slot button, which works even after the 30 minutes.

With your server selected, open Services, switch Group Finder on (manager access needed) and click Open. Until a listing channel is set, that opens the setup page at /p/group_finder/setup; click Set Up Group Finder there, or run /group setup in Discord (needs Manage Server). The wizard creates a Group Finder category with #lfg-listings and #lfg-forum, saves them and creates starter templates. It needs the bot to have Manage Channels and changes nothing without it. Members can then post with /group create, /group quick or the web form at /p/group_finder/create.

Server settings are on the Group Finder Settings page:

• Channels: Listing Channel, plus an optional Log Channel and Alert Channel.
• Forum threads: a Forum Channel and Auto-create forum threads, which gives each listing its own thread.
• Limits: Max Active / User (3 by default), Default Expiry (h) (4), Max Expiry (h) (48), Cooldown Between Listings (s) (60), Min Account Age (days) (0, off) and LFG Ping Role ID, pinged at most once every 10 minutes.
• Behaviour: Require Listing Approval (makes every listing approval-only, so leaders approve each applicant), Allow Cross-Post (needed for Public listings to reach the public board), Game Pings and Experience Levels.
• Anti-spam: a Keyword Blocklist of up to 50 keywords.

Listing templates with role slots are on /p/group_finder/templates and per-game activity presets on /p/group_finder/presets.

The bot needs Manage Channels, View Channel, Send Messages, Embed Links, Read Message History, Manage Roles, Manage Threads and Create Public Threads. The setup wizard checks for Manage Channels first and changes nothing without it. The thread permissions cover forum threads: with Auto-create forum threads on, each listing gets its own thread, which is locked when the group closes. If the bot's role is missing any of these, the Group Finder pages show a banner listing them with a Fix with one click link.

Listings stay in the server they were posted in unless the leader picks Network or Public visibility; Local is the default. Then check how you want to share:

• Networks: join a network with Inbound on, from the Networks page at /p/group_finder/networks or with /group-admin network join. Network and Public listings from peer servers that have Outbound on are then posted in your listing channel or forum and show up in /group browse.
• The public board: Public listings appear on /lfg only when the posting server has Allow Cross-Post on in Group Finder Settings; without it they post as Network. To ask for a spot from the board, a visitor signs in with one of their servers selected in the dashboard and clicks Request to Join. The leader accepts or denies it on the Requests page at /p/group_finder/cross-requests, which needs a dashboard role on that server.

Sentinel is YourBot's moderation service. Its filters combine 22 kinds of check (word filters, spam rate, mention floods, caps, links, known phishing links, new accounts, staff impersonation and more) with 13 actions, from deleting a message or warning to timeouts, kicks, bans, quarantine and voice actions. Around the filters it adds anti-nuke protection against a hijacked staff account, raid mode and lockdowns, server change logs, management of Discord's own AutoMod rules, warning points and a numbered case log with appeals and member reports. Manage it at /p/sentinel/.

Click Join on the listing in Discord. If the listing has role slots, pick one from the Choose a role to join… menu instead, and if it's approval-only, click Apply and the leader approves or denies. From a command, /group join and /group apply let you pick the listing by name. When the group is full, joining puts you on the waitlist, and the first person waiting moves in when someone leaves. Leave frees your seat, but a member the leader removed can't rejoin that group.

Go to Services, switch the Sentinel Moderation card to ON and click Open. Then open Setup (/p/sentinel/setup), pick Relaxed, Standard or Strict under Choose how strict and click Run setup. The wizard creates #sentinel-logs, #message-log, #server-log and a Quarantined role (reusing any that already exist) and detects your moderator roles. It then adds the filters for your level and turns on the recommended protection: anti-nuke with quarantine, restore and the hold, the bot-add rule, escalating timeouts and the message log. Leave Act right away off so the filters start in Testing, then adjust or add filters on the Spam & scams page.

Each filter on the Spam & scams page (/p/sentinel/spam) opens a panel with:

• Runs on: every message, a member join or a nickname change.
• Catches: any of 22 kinds of check. With several checks, it acts when any of them match or only when all of them do.
• What happens: any of 13 actions. Each action can be set to run only once the member has a given number of warnings.
• Where: run only in chosen channels, exclude channels and exempt roles.
• Pause between punishments: how long before the filter can punish the same member again, 10 seconds by default, from 0 to an hour.
• Priority (lower runs first) and Test this filter on its own.

Warning expiry and point decay, the DMs under What members are told and the log channel are on the Settings page and raid protection is on the Raids page.

The Sentinel pages check the bot for View Channel, Send Messages, Embed Links, Manage Messages, Timeout Members (listed as Moderate Members in the dashboard banner), Kick Members, Ban Members, Manage Roles, Manage Nicknames and Manage Server. If any are missing server-wide, a banner at the top of the page names them with a Fix with one click button that re-invites the bot with its full permission set. Anti-nuke also needs View Audit Log and the setup wizard needs Manage Channels; both are in the bot's standard invite. Discord refuses a timeout, kick or ban when the member's highest role is not below the bot's, so keep the bot's role above the members it moderates.

If the filter warned, timed out, kicked, banned or quarantined the member, open the case it created on History > Cases (/p/sentinel/cases); its Why this fired panel shows the check that matched, the matched term or pattern and the measured value against the threshold. A filter that only deletes messages makes no case. Then open that filter on the Spam & scams page and fix the cause: raise the threshold, add roles under Never for (members with your Moderator roles in Settings are already skipped) or narrow it with Only in these channels and Never in these channels. While you tune, use Try it in its panel to test sample text; with Test this filter on its own it acts on nobody and posts a note in the mod log for each match instead, and a filter that would warn, time out, kick, ban or quarantine also records a case marked Testing. To undo a wrong action, set the case to Overturned, which reverses a timeout, ban or quarantine.

Social & Patches posts new content from outside Discord into a channel, thread or forum you pick. Sources include Twitch live streams, YouTube uploads, Bluesky posts, any RSS or Atom feed, Reddit, GitHub releases, Steam news, Statuspage status pages and patch notes for games such as League of Legends, Valorant, Fortnite, Minecraft, Guild Wars 2 and FFXIV. A catalog of 98 games and tools adds a feed in one click, and every feed can have role pings, keyword filters, a digest and its own message text. Manage it at /p/social/.

Yes. Anti-nuke reads the audit log and watches for 12 kinds of damage: mass channel or role deletion and creation, mass bans and kicks, webhook spam, webhooks deleted or changed, a bot being added, a role given dangerous permissions, a member given a dangerous role and a change to the server name, vanity link or owner. Each watch has its own count and time window, for example 3 channel deletions in 10 seconds. It is on from the first time a server turns Sentinel on. Mass damage gets quarantine, which takes every role Sentinel can take until the account is released, and a single risky change by an admin, such as adding a bot, handing out a dangerous role or renaming the server, is undone and reported while the admin keeps their roles. On the Anti-nuke page (/p/sentinel/antinuke) an owner or an extra owner can switch the response to removing the account's roles, kicking, banning or an alert. Dangerous permission grants and server name or vanity changes are put back by default, whatever the response. A server that used Sentinel before this became the default switches it all on with Turn on recommended protection on Sentinel's Home page.

Yes, free. Every hour, unless raid mode or a lockdown is on, Sentinel backs up each server where it is on: server settings and images, roles, every channel and category with its permissions, emojis and stickers. Every six hours it also saves the ban list and, on servers of up to 25,000 members, who holds which role. A backup is stored only when something changed. Sentinel keeps the newest 24 and one a day for a week, and Back up now on the Backups page (/p/sentinel/backups) keeps up to 10 of your own. An owner can download a backup or restore it: the restore page shows what would change and lets you choose what comes back, and a safety backup is taken first. Messages, threads and webhooks are not backed up. With restore on, anti-nuke brings deleted channels and roles back by itself from the newest backup taken before an attack.

Sentinel has two answers on its Owners & recovery page (/p/sentinel/owners). An owner can add up to 10 extra owners: they can change every Sentinel setting, anti-nuke included, and anti-nuke never acts on them, but they get nothing else on YourBot. The Discord server owner can also make 10 one-time recovery codes; keep them somewhere safe away from Discord. If an owner account is taken over, sign in to YourBot with a different Discord account that is in the server, open Recover a server (/recover) and enter a code. That account becomes an owner, every other owner account is frozen until an owner unfreezes it and a frozen account loses its anti-nuke exemption. While any account is frozen, owning the Discord server gives nobody dashboard access or a pass on command rules. YourBot cannot give you the Discord server itself back; Discord's own support handles a stolen Discord account.

Yes, with /mass ban, /mass kick and /mass timeout. Name members by mention or user ID, pick everyone who joined in the last few minutes with joined_within (up to 1,440 minutes) or do both. Sentinel first shows the count, up to 10 names and who it skipped and why, and nothing happens until the moderator who ran it clicks Confirm. /mass ban takes up to 200 members in one go and can delete their recent messages; kick and timeout take up to 100. The owner, YourBot, you, moderators and anyone whose top role is not below both yours and the bot's are always skipped, and so are bots unless you name them. Each member gets a case and the mod log gets one summary. While anti-nuke is on, only the server owner, an extra owner or an anti-nuke exempt account or role can run /mass, because the bot does the work and anti-nuke does not watch the bot. For one member, right-click them, choose Apps and pick Timeout, Quarantine, Ban or View cases.

Go to Services, switch the Social & Patches card to ON and click Open. If you want ready-made channels, the Setup page (/p/social/setup) has Create / repair channels for a Social Alerts category with #patches, #streams and #creator-posts, plus starter packs of popular feeds. To add a feed, click New Subscription, pick a source such as Twitch, YouTube or an RSS feed (or a game from the catalog), enter the streamer, channel or feed URL, choose where to post and click Create Subscription. The first check only records what is already there, so only items published after that are posted.

Run /lockdown and pick a scope: this channel (the default), every text channel, one role, new joins or invites (paused for up to 24 hours). Add a reason and, if you like, a timer from 1 to 1,440 minutes after which it lifts itself; /unlockdown puts back exactly what the lock changed. An administrator can also set /raidmode to soft (10-second slowmode in every text channel, stepping up to hard if joins keep coming), hard (30-second slowmode, every new join quarantined by default and a DM to admins) or lockdown (maximum verification, no posting and every new join kicked). Raid mode switches itself to hard at 10 joins a minute by default or when a group of look-alike accounts joins. It turns off after 30 minutes by default. Lock down on Sentinel's Home page (/p/sentinel/) lists active locks with an Unlock button and has the raid mode controls, which are also on the Raids page.

Every feed (open it with Edit on the Social overview) has:

• the source key, such as a Twitch username, a YouTube channel ID, @handle or URL, a feed URL, a Steam app ID or a GitHub repo;
• Destination: a channel, thread or forum, with forum tags and Publish to followers for announcement channels;
• Ping roles and Allow @everyone and @here;
• Post as the bot or a webhook with its own name and avatar;
• Digest: off, or one message every 15 minutes, hour, 6 hours or 24 hours with up to 25 items;
• Poll interval (seconds): each source has its own default and minimum, for example 120 seconds for Twitch (minimum 60) and 900 seconds for YouTube and RSS;
• keyword filters (Only post if it mentions and Never post if it mentions) plus the message text and embed.

Twitch feeds also have stream options such as Only alert for these games and a live role.

Social needs View Channel, Send Messages and Embed Links where it posts (plus Send Messages in Threads for a thread). If the bot is missing one of those three server-wide, the Social pages show a banner with a Fix with one click button. Create / repair channels on the Setup page also needs Manage Channels and Manage Roles. A few feed options need more: Manage Webhooks in the channel to post as a webhook, Mention Everyone if you turn on Allow @everyone and @here for a feed and Manage Roles (with the bot's role above that role) for a stream's live role. Role pings only mention the roles you pick for that feed.

Check these in order:

• The feed was added while they were live. The first check only marks the current stream as seen, so alerts start with their next stream.
• The username is wrong. Twitch returns nothing for a login it does not know, which looks exactly like an offline channel, so no error appears. Use the streamer's login name as it appears in their twitch.tv link.
• A filter skipped it. A stream in a game outside Only alert for these games, or one that fails your keyword filters, is skipped.
• The feed is paused. After 5 failed checks in a row a feed turns itself off and server managers get a notification. Its tile on /p/social/ shows the error; fix it and click Reset.

Twitch feeds are checked every 120 seconds by default, so an alert can take a couple of minutes to arrive.

Tickets is a private support desk inside Discord. Members open a ticket from a panel button, or by right-clicking a message and choosing Start ticket if you turn that on, and staff can open one for a member with /ticket open. After an optional intake form the member gets a private channel or thread with your staff team. Staff claim, reply, add internal notes, set priority, escalate to another panel and close tickets from Discord with the /ticket commands or from the dashboard queue, backed by SLA targets, support hours, canned responses, a knowledge base, automations that step in when nobody replies and a star rating when a ticket closes. Each panel has its own pages for who can open it, claiming, roles for the ticket's owner, channel names, a private staff thread, the look of its messages, hours, escalation and logging. Each closed ticket channel or thread gets a transcript. Manage it at /p/tickets/.

Open the Social overview (/p/social/) and look at the feed's tile. A feed that fails 5 checks in a row switches itself off and shows its last error across the top of its tile. Server managers also get a dashboard notification. Fix the cause (for example a deleted channel, a changed feed URL or missing permissions in the channel), then click Reset to clear the failures and turn it back on. If the feed is on but quiet, check its keyword filters and digest setting. If it posts a burst of old items after a change, Skip to current marks the newest item as seen so only new items post.

Go to Services, switch the Tickets card to ON and click Open. The quickest start is Run auto-setup on the Setup page (/p/tickets/setup): it creates Support Tickets and Closed Tickets categories, an #open-a-ticket channel with a General Support panel posted in it, a #ticket-logs channel and a Support Staff team built from your moderator roles. To build it yourself, click + New Panel on /p/tickets/panels, choose the channel mode, categories, staff team and intake form, save it, then post it from Post Panel to Discord or run /tickets panel in Discord.

Each panel on /p/tickets/panels sets its Channel Mode (a private channel, a private thread or a form that goes to a staff review queue with no channel), a Name Template (default ticket-{number}, also {panel}, {username}, {button}, {category}, {panel_number} for the panel's own count and zero padding such as {number:4}), the Open Tickets Category, Closed Tickets Category and Awaiting Reply Category, a Welcome Message, the Staff Team, Intake Form and SLA Policy, an open ticket limit and a cooldown between tickets. Up to 25 buttons and a nested category menu can route tickets to a different form, team or category. Each panel also has its own Access, Claiming, Roles, Channel, Staff thread, Look, Hours, Escalation and Logging pages.

Server-wide options are on the Settings page: the Log channel, Max open tickets per user (1 by default), a daily cap, an inactivity close request (off by default) with a countdown of 24 hours by default, member DM notifications, the rating survey, which events the log channel posts and support hours. The same page decides when a closed ticket's channel is deleted: after a number of days (0 keeps it; the 7-day default starts once you run auto-setup or save the Settings page), a set time after closing or right away. It also sets whether staff must claim a ticket before closing it. The Messages page rewrites what the bot says in tickets and in its DMs, and Automations adds rules that step in when nobody replies.

The Tickets pages check the bot for View Channel, Send Messages, Embed Links, Read Message History, Manage Channels, Manage Roles, Manage Threads, Create Private Threads and Send Messages in Threads. Manage Channels and Manage Roles let it create a private channel for each ticket with its own permission overrides (a channel's own settings call Manage Roles Manage Permissions). Read Message History lets it capture transcripts. The thread permissions cover panels that use private threads and the private staff thread a panel can add inside each ticket channel, which needs Create Private Threads and Send Messages in Threads. A panel set to pin each ticket's welcome message also needs Pin Messages. If any are missing server-wide, a banner on the Tickets pages lists them with a Fix with one click button.

Ask the member what the bot replied, or click the button yourself:

• It says Tickets is not enabled. Switch Tickets on in Services.
• A limit message, such as "You already have 1 open ticket". Each member can have 1 open ticket by default. Raise Max open tickets per user or the daily cap in Settings and check the panel's own limit and cooldown; roles listed under Roles the limits do not apply to skip them.
• "You are not able to open tickets in this server." The member or one of their roles is on the blocklist.
• "You can't open a ticket here.", "Only staff can open tickets here." or a list of roles they need. The panel's Access page limits who can open tickets from the panel or one of its buttons. Members with Manage Server always can.
• "Failed to create your ticket channel." Discord refused the channel. The bot needs Manage Channels and Manage Roles, and the ticket category's own permissions must not deny them. When someone with Manage Server clicks, the reply names any permission missing at server level, and server managers also get a dashboard notification that links to the Panels page.

Outside support hours, members get your closed-hours message instead of a ticket, unless the hours are set to open the ticket anyway with a notice saying when the team is back. Check Support hours in Settings (up to 6 time ranges a day, closed dates and a timezone) and the panel's own Hours page, which can follow the server's hours, stay open around the clock or use hours of its own.

Join-to-Create Voice Channels gives each member a voice room of their own. When someone joins your lobby channel, the bot creates a room named from your template, moves them into it and sends them a control panel by DM. The owner can lock, hide, rename, limit and permit or reject people from that panel or with /voice commands. By default the room is deleted when the last person leaves. You can run several lobbies, each with its own size and naming rules. Configure it at /p/voice_jtc/.

Each closed ticket channel or thread gets a transcript, however it was closed: the Close button, /ticket close, the dashboard or an automatic close. Find them on the Transcripts page, which lists all of them, newest first, 50 a page; each one opens in the browser or downloads as HTML or TXT. On a closed ticket, staff can also press 📜 Transcript to save it and get a link to it on the dashboard. A transcript keeps the last 1,000 messages of a ticket, so in a longer ticket the earliest messages are left out. If a Log channel is set in Tickets settings, a summary of each closed ticket is posted there, along with up to 10 of its files (8 MB in total) so they outlast the channel; if you also pick a Transcript channel in Settings, the transcript and files go there instead. With DM the transcript to the member when their ticket closes turned on, the member who opened the ticket also gets a copy by DM, without staff notes or the activity log. Closed ticket channels are deleted after the number of days set in Settings (0 keeps them; a new setup starts at 7 once you run auto-setup or save Settings) or sooner if you choose that under Closing and deleting tickets, and a transcript is captured before a channel is removed.

Go to Services, switch the Join-to-Create Voice Channels card to ON and click Open. Until a lobby is saved, the service sends you to its Setup page (/p/voice_jtc/setup); click Run Auto-Setup to create a "Click to Join" lobby in a Voice Channels category (a category with that name is reused if you already have one). To use a lobby you already have, run Auto-Setup once, then change the Lobby Channel ID and Category ID under Configuration on /p/voice_jtc/ and click Save Settings. Then join the lobby: the bot creates your room and moves you into it.

Under Configuration on /p/voice_jtc/:

• Lobby Channel ID, Category ID and a Fallback category for when the room category holds 50 channels.
• Channel Name Template: default 🎧 {display_name}, also {username}, {count} and {activity}.
• Default User Limit (0 to 99, 0 for no limit) and Bitrate (bps).
• Delete when empty (on by default) and Pass the room on when the owner leaves (on by default).
• Control panel for room owners, New rooms start locked, New rooms start hidden, Creator owns their channel and Room owners can edit permissions.
• Channel access: inherit from the category or use a custom role allowlist.

The Lobbies card adds extra lobbies, each with its own label, category, name template, user limit and bitrate.

The service checks the bot for View Channel, Connect, Manage Channels, Manage Roles, Move Members, Mute Members, Deafen Members and Priority Speaker. Manage Channels creates and deletes rooms and Move Members moves the member in from the lobby. Manage Roles writes each room's permission overrides for lock, hide, permit, reject and the owner's access. What a room owner is given (manage the room, move, mute, deafen and priority speaker) is trimmed to what the bot itself holds. A banner on the service page lists anything missing server-wide, with a Fix with one click button.

Check these:

• The service is off or the lobby changed. The service must be on in Services, and members must join one of your lobby channels. If the lobby was deleted, click Re-create Lobby + Category on /p/voice_jtc/ or run Setup again.
• Missing permissions. The bot needs Manage Channels to create the room and Move Members to move the member in. The service page lists missing server-level permissions with a Fix with one click button, but it cannot see a deny set on the room category itself, so check that category's permissions too.
• They already own a room. Joining the lobby again moves them back into their existing room instead of making a second one.
• They left too quickly. If a member leaves the lobby before the bot moves them, the new room is deleted straight away.

A full room category is not the cause: at 50 channels, rooms go to the Fallback category, then the lobby's own category, then outside any category.

Welcome greets new members with a message or embed, an image welcome card you design in the Card Studio and an optional DM. It can also post a goodbye, with a card of its own, when they leave. It hands out auto-roles (straight away, after a delay or after the member verifies) and can hold new members behind a verification gate: a button, a captcha or a web page. It also has server rules with /rules, /roles for roles members give themselves, a welcome quest, buddy pairing, a first-message celebration, member-count milestones and self-assign role menus with buttons, a dropdown or emoji reactions. Manage it at /p/welcome/.

The room's owner gets a control panel by DM and the /voice commands: lock, unlock, hide, show, limit (0 to 99), rename (up to 90 characters), permit, reject, unpermit, unreject, kick, transfer, claim, info and prefs. Permits and rejects are remembered for the owner's next rooms, and /voice prefs saves a preferred name, limit and whether rooms start locked or hidden. If the owner leaves, the room passes to the next person inside by default, or anyone inside can take it with /voice claim. /voice info shows the panel privately for members with closed DMs, and anyone with Manage Channels can use every owner control in a room they are in.

Go to Services, switch the Welcome card to ON and click Open. On the Setup page (/p/welcome/setup) click Run setup: it creates #welcome and #welcome-logs, posts a sample welcome and, on a first run, turns on the rich embed, the welcome card, the first-message celebration and server highlights. Then write the greeting on the Messages page (/p/welcome/messages), design the card in the Card Studio and set roles, verification and the rest on the other Welcome pages, clicking Save changes on each. Run /welcome test in Discord (Manage Server needed) to preview what a new member sees.

Each part has its own page in the Welcome service (/p/welcome/), and each page saves only its own settings:

• Messages: the welcome message, the goodbye and the welcome DM, each as plain text or an embed, with tags such as {user}, {user.mention}, {server} and {member_count}, plus up to 25 rotating greetings, server highlights, start-here channels and deleting greetings after a while.
• Card Studio: the image card sent with the welcome, and with the goodbye if you want one.
• Roles: roles given on join, an optional wait of up to 600 seconds, roles given back to members who come back and the roles members can give themselves with /roles.
• Verification: a button, captcha or web page, with an optional deadline.
• Rules: your server rules.
• Engagement: member-count milestones (100, 250, 500, 1,000, 5,000 and 10,000 by default), the first-message celebration and the buddy system.
• Logs & cleanup: the join and leave log and the join counter.

Quests and self-assign role menus have their own pages too.

The Welcome pages check the bot for View Channel, Send Messages, Embed Links, Attach Files (the welcome card is sent as an image file) and Manage Roles (for auto-roles, verification and role menus). Discord only lets the bot give roles that sit below its own highest role, so drag the bot's role above every role Welcome hands out. For safety it never grants @everyone, roles managed by an integration or roles with Administrator, Manage Roles, Manage Server, Manage Channels, Ban Members, Kick Members, Manage Webhooks or Mention Everyone. If the bot is missing a permission server-wide, the Welcome pages show a banner with a Fix with one click button. A role menu that uses emoji reactions also needs Add Reactions and Read Message History in its channel.

Work through these:

• Role order. Discord only lets the bot give roles below its own highest role. Open Server Settings, Roles and drag the bot's role above the auto-role. The Roles page greys out roles above the bot's own, and /welcome set autorole in Discord tells you; a role that was picked before it ended up above the bot stays ticked but is skipped when members join.
• A refused role. Welcome never grants @everyone, integration-managed roles or roles with a dangerous permission such as Administrator, Manage Roles or Ban Members. The Roles page greys those out and refuses them when you save.
• Roles on join is off. On the Roles page, turn on Give roles on join, tick the roles under Roles to give and click Save changes.
• A wait or the verification gate. With Wait before giving them set, a member who leaves before it ends gets nothing, and with verification on, the roles wait until the member verifies.

Yes. On the Verification page (/p/welcome/verification), switch on Turn on verification, pick a Verification channel and a Verified role and choose How members verify: a one-click button, a captcha where they type an image code or a web page where they sign in with Discord. Who has to verify can be everyone or only suspicious accounts (younger than 7 days by default or with no avatar). Optionally give an Unverified role until they pass and set a Deadline after joining, up to 7 days, with a Reminder DM and a choice of kick, ban, hold with a role or nothing At the deadline. Click Save changes, then Post the message to publish the panel; auto-roles and buddy pairing wait until the member verifies.

No. Most services suit any community: Sentinel moderation, Tickets, Analytics, Welcome, Scheduled Announcements, Beacon events, Giveaways, Join-to-Create Voice Channels and Social Feeds alerts for Twitch, YouTube, Bluesky, Reddit or any RSS feed. Group Finder (looking for group) and the game patch-note feeds in Social Feeds are the parts built with gaming in mind. Every service starts switched off, so your server only runs the ones you turn on.

Yes, in most cases. Switching a service on or off and saving its settings reach the bot without you restarting anything, so test with a fresh action, such as a new message or a new voice join. The exception is a custom bot: switching a service on makes YourBot restart your bot so it loads that service. The Services page tells you the custom bot restarted, and the bot is offline for a moment while it reconnects. Switching a service off never needs a restart. If a change doesn't seem to apply, reload the page to check it was saved.

YourBot is one bot with ten services built in: moderation, tickets, analytics, scheduled events, giveaways, a group finder, join-to-create voice channels, welcome flows, announcements and social feed alerts. You manage all of them from one web dashboard, and the shared bot runs them for free. How many of your current bots it can replace depends on which of those jobs they do today. Every service starts switched off, so you can run YourBot next to your current bots and move one feature at a time. Premium adds your own custom bot and plugins from the marketplace. For side-by-side comparisons, see Compare.

Services are the ten tools YourBot builds and runs itself, such as Sentinel, Tickets and Analytics. They are free on every server, work on the shared bot or a custom bot and are switched on from Services. Marketplace plugins are made by independent developers and installed from the Marketplace. A plugin:

• runs only on a custom bot, so the server needs Premium
• runs in its own sandboxed container, with only the permissions you approve when you install it
• is priced by its developer: free, a one-time purchase or a subscription

Installed plugins also appear on the Services page, marked Marketplace.

No. Day-to-day use happens in Discord, and you can switch services on and run their setup there, but managing YourBot needs the web dashboard.

In Discord:

• members use slash commands and buttons, such as ticket panels, event sign-ups and giveaway entries
• the welcome message YourBot sends when it joins lets someone with Manage Server pick services and run their setup
• commands such as /announce now, /giveaway create and /group setup cover common jobs without the dashboard
• /yourbot check privately shows server admins whether the bot has what your services need, like the Setup Check on the dashboard's Bot page

On the dashboard you:

• switch services on and off
• change most service settings
• set command permissions with Commands on each service card
• choose who can open the dashboard on the Access page
• set the server timezone and your custom bot on Bot Settings
• install marketplace plugins and manage Premium

Unless you restrict them on a service's Commands page, members can use:

• Analytics: /stats, /me, /leaderboard, /top and /chart
• Group Finder: /group create, /group quick, /group browse, /group join and /group-alerts add
• Join-to-Create Voice Channels: /voice lock, /voice rename, /voice limit and the other /voice controls for their own room
• Beacon Events: /beacon list and /poll create, plus the Sign Up button on event cards
• Giveaways: /giveaway list and /giveaway info, plus the entry button or reaction
• Tickets: the button on a ticket panel, /kb search and /kb browse
• Sentinel: /report and /appeal
• In any server: /help, /support and /yourbot

Sentinel's moderation commands and /group-admin only show for members with the matching Discord permission. Every service's full command list is in the docs.

Pick one, or mix them:

• Start Your Server designs your channels, roles and service setup from a short description of your community, such as the game you play and how your group runs. It also has ready-made templates, such as Gaming clan and Esports team, plus community templates other server owners shared, and a template opens as a plan at no cost. You see the plan and approve it before anything changes. Server owners open it from Start Your Server in the dashboard sidebar or at /start. On the Free plan each design it writes for you is paid from AI credits; Premium includes 50 free designs.
• The welcome message YourBot sends when it joins has a Pick the services you want menu. Choose your services, then Set them up for me to run each one's automatic setup or Set up in the dashboard to just switch them on.
• Every service also has its own setup page on the dashboard.

No. When the bot joins, every service starts switched off and YourBot creates, renames and deletes nothing (Discord itself adds a role for the bot holding the permissions you approved). It only sends a welcome message by DM to whoever added it or the server owner; if both have DMs closed, it posts that message in a channel instead.

Changes happen only when you ask for them:

• Running a service's setup from its setup page or with Set them up for me in the welcome message adds the channels, roles, permission settings and starter posts that service needs. It never deletes or renames yours, and some setups reuse ones you already have: Sentinel's reuses an existing log channel and quarantine role, while a Quarantined role it creates is blocked from posting in your text channels.
• Start Your Server changes only what you approve in its plan.

You can run YourBot next to the bots you already use and move one feature at a time.

Yes. Each server is set up on its own: its service switches, settings, dashboard access and Bot Settings belong to that server alone, so two servers can run completely different setups. Pick the server you are working on from your server list. Some features also connect servers:

• Sentinel's Banned somewhere else setting acts on accounts banned on your other servers (same Discord owner, with the setting on there too), and Ban networks share bans with servers that other people own. Both are on Sentinel's Ban evasion page.
• Group Finder networks share listings between allied servers, and Public listings can appear on the LFG board.
• Premium is billed per server: a subscription includes one server, and more servers are add-on seats on it, each with its own custom bot.

No. YourBot runs everything on its own servers: the shared bot, the dashboard and the ten services. A custom bot runs there too. You create the application in the Discord Developer Portal and paste its token on Bot Settings, and YourBot starts it, restarts it after a crash and shows its state, with Start Bot, Restart and Process Logs on the same page. Marketplace plugins also run on YourBot, each in its own sandboxed container. There is nothing to install on your computer.

On the Changelog. It lists every release, newest first, with the changes grouped under headings such as Added, Changed and Fixed. Each release also has its own page, and you can follow new releases in a feed reader with the Atom feed.

The invite asks for 32 permissions that together cover all ten services. It never asks for Administrator.

• Moderation: Kick Members, Ban Members, Timeout Members, Manage Nicknames and View Audit Log
• Server setup: Manage Server, Manage Channels, Manage Roles and Manage Webhooks
• Messages: View Channels, Send Messages, Send Text-to-Speech Messages, Manage Messages, Pin Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Use External Emojis, Mention Everyone and Use Application Commands
• Threads: Manage Threads, Create Public Threads, Create Private Threads and Send Messages in Threads
• Voice: Connect, Speak, Video, Mute Members, Deafen Members, Move Members and Priority Speaker

You can untick any of them on Discord's screen. If a service you use then lacks one, its dashboard page shows a banner with Fix with one click. To check the channels and roles your services use as well, run the Setup Check on the Bot page or /yourbot check in Discord.

Access is set per server on the Access page, by role:

• Owner: everything, including who has access, Bot Settings and Start Your Server. The Discord server owner is always one.
• Manager: switches services on and off, changes their settings and command permissions, installs marketplace plugins and can see who has access. No Bot Settings by default.
• Viewer: read only. Sees Overview, Services, Marketplace and service pages such as the ticket queue and transcripts, but can't change anything or open Access or Bot Settings.

Under Manager Permissions you can change what managers get on pages such as Marketplace, Access and Bot Settings: set each to No Access, Read Only or Full Access and click Save Permissions. This applies to every manager on the server. You can't limit someone to certain services.

Not by itself. The Discord server owner is always an Owner on the dashboard; everyone else needs a dashboard role. Discord Permission Sync on the Access page hands one out automatically: set Administrator and Manage Server each to No Access, viewer or manager and click Save Permission Sync. A server YourBot joins for the first time starts with Administrator at manager and Manage Server at No Access. So a member with only Manage Server sees the server in their server list but can't open its pages until you change that or grant them access yourself. Sync never gives the Owner role. When a member gains or loses a role in Discord, their synced access updates within seconds.

Yes. On Services, click Commands on the service's card. To set many commands at once, pick a preset and click Apply Preset: Open clears every rule, while Balanced and Locked down limit staff commands to the Moderator roles you choose. A preset replaces the rules already set for that service's commands. For one command, click EDIT on its row:

• Who can use it: only these roles
• Where it works: only these channels
• Cooldown: seconds between uses, up to 3600, per user, per channel or server-wide
• the advanced section: blocked roles and channels, plus members who are always allowed or always blocked

Click Save Changes. The switch on each row turns a command off. The server owner and dashboard Owners are never blocked, and members with Administrator skip the role, channel and cooldown rules unless you untick Administrators bypass these restrictions. The command still shows in Discord; a blocked member gets a private reply saying why.

Describe your community: what it is for, the game or topic, roughly how many people and anything you want in it, such as an LFG area, a private staff section, events or a verify step. Servers built around one game, or around a purpose like study, support, creators or esports, all work. If your description is short, the designer may ask a question or two first, and Just build me something good tells it to go ahead with its best guess. On a server that already has channels, it reads them and can plan around what you want to keep. Each message can be up to 4,000 characters. Start at Start Your Server.

Yes. The builder page has a gallery of ready-made templates, including a gaming clan, esports team, study group, creator hub, support server and community hangout. Opening one is instant and free: no AI runs until you ask for changes in chat. Your templates lists designs you saved with Save this design as a template, and the globe button (Share to Community templates) puts one of yours under Community templates for other server owners to use. Saved templates carry no IDs from your server, so they fit any server. Nothing is built until you review the design and start the build.

A design can include:

• Categories and channels: text, voice, forum (with post tags), announcement and stage channels. Announcement and stage channels need Discord's Community mode; without it they are built as text channels and the build report says so.
• Roles with a moderator, helper or member permission preset. Presets never grant Administrator, Manage Server, Manage Roles or Manage Channels.
• Access rules per category or channel, such as a staff area only staff can see or an announcements channel members can read but not post in.
• Channel topics, slowmode and formatted starter posts, like a welcome or rules message, that the bot posts after the build.
• Discord's own AutoMod filters and, if you want, Community onboarding with a welcome screen, questions and a server guide.

You can review and change all of it before anything is built.

Yes. A design can switch on any of the ten services and point them at the channels and roles it creates, for example Tickets at a support category or Giveaways at a giveaways channel. The Services tab on the design lists each service it touches with its settings, which you can edit field by field; your changes are saved into the design. When you build, Features this build sets up lets you untick any service you'd rather leave off, and its channels are still built. A design can also propose switching off services that don't fit, which you confirm the same way. After the build, YourBot checks that every configured service points at a channel or role that exists and that the bot can post there. It may also suggest marketplace plugins, but those are suggestions only and are not installed.

Two ways, and you can mix them:

• Chat: tell the designer what to change, like fewer channels or a private staff area. Buttons such as Fewer channels, Add giveaways, Add events, Private staff area and Add a verify gate send common requests. Each chat message is a design turn, so it uses a free design or AI credits.
• By hand, at no cost: the small buttons next to each category, channel and role in the preview let you Rename, Move to another category, edit who can see and use it or Remove from design. Roles have Pick this role's permissions yourself, and the Services tab edits service settings.

The designer is told about your hand edits with every later chat message and asked to keep them. Not what you wanted? Discard, shown until you build, tells the designer you don't want this design, and it asks what you'd like instead.

No. Designing, chatting, editing and saving templates only change the design stored in YourBot. Your Discord server is untouched until you start the build yourself. Before that you can:

• click a channel in the preview to see it the way members will, with its intro message, topic and permissions;
• use See it as to switch between New member (no roles yet) and each role in the design, showing which channels that member could see and where they could only read;
• open Review and build to see every change listed under Adding, Renaming, Moving and Updating, and untick anything you want left out.

The Safety check flags problems it can spot in the design before you build.

Yes. The designer reads your current channels and roles, and the build reuses anything that already exists by name, adding only what is missing. Nothing existing is deleted unless you choose it. In Review and build:

• channels and roles the design would remove, and anything in your server that isn't in the design, are listed with every box unticked; Start fresh ticks them all, so check the list before you build;
• to delete anything you must also tick I understand the items I checked are deleted permanently, and their messages cannot be recovered.;
• anything listed under Kept for your enabled features is never deleted;
• renames and moves of existing items are listed too, and you can untick them.

The bot can't delete a role that sits above its own; the build names any such role before it starts.

Before every build, YourBot takes a snapshot of your channels, categories and roles, with their permissions and topics, and of your server settings. If the snapshot can't be taken, the build stops before changing anything. After the build, Download backup saves it as a JSON file and Undo build puts back what the build removed or changed:

• deleted channels are recreated with their access rules, topic, slowmode and age-restricted setting;
• deleted roles are recreated with the permissions the bot is able to grant, which never include Administrator, Manage Server or Manage Roles;
• deleted categories are recreated with their access rules;
• service settings and role permissions the build changed are set back;
• channels and categories the build kept get back the name, category, topic, slowmode, age-restricted setting and access rules it changed, except Manage Permissions and Manage Webhooks, which the builder never sets;
• roles the build renamed get their old names back;
• server settings changed by onboarding, like the verification level, are restored, and Community mode is switched off again if it was off before.

Undo does not remove what the build added or give members back a recreated role. Deleted messages can't be restored because Discord can't bring them back, so recreated channels come back empty.

Only people with the Owner role on that server in the dashboard. The server's owner has it, and an owner can give it to someone else on the Access page. Managers and Viewers can't open the builder. AI credits for a design turn come from the balance of the owner who sends it. The build itself is carried out by the bot that runs your server, your custom bot if you have one, shown as building as @name on the design page. That bot needs Manage Channels, plus Manage Roles when the design adds or changes roles, and its role must sit above any role the build changes.

Whatever was already created stays in your server, and building again is safe: the build reuses what exists by name and only adds what is missing.

• If some items fail, for example because Discord refused them, Build report: what didn't land and why lists them and Retry the failed items tries exactly those again.
• If YourBot restarts mid-build, the design page says This build was cut short by a restart; review it and build again to finish.
• A build that stops making progress is ended after about 30 minutes, and the page asks you to reload and try again.

Only one build runs on a server at a time. Undo build is offered once a build finishes, including one that finished with errors.

Yes, at any time. On Bot Settings, while your server runs its custom bot, find Bot Identity. Enter a new Username, an Avatar Image URL (PNG, JPG or GIF) or both, then click Update Identity. YourBot downloads the image and sends the change to Discord, so it applies everywhere your bot appears. Discord limits how often a bot can change its name and avatar, so make changes sparingly. The online status and activity are set separately under Bot Presence. Bot Settings is open to owners by default.

On the shared bot, a server with an active Premium subscription can give the bot its own picture, banner and about me in that server only, under How the Bot Looks in This Server on the same page. Every other server keeps seeing the normal YourBot bot.

You pay the price shown on Buy Subscription, which matches Pricing. Choose Monthly or Yearly there. That price covers your first server. Each server you add with Additional servers adds the add-on price, and the page shows the new total before you continue. Stripe Checkout then charges that total for the first billing period.

There is no free trial, so Checkout asks for a payment method and takes the first payment straight away. If you arrived with a valid referral code, the Buy Subscription page says so and you get a discount off your first month on a monthly plan. After that, the subscription renews at the end of each period until you cancel.

Yes. Before a Start Your Server design or a Plugin Builder build runs, YourBot holds enough of your AI credits to cover the most it can cost. When the run finishes you are charged only for the tokens it used, and the rest of the hold goes straight back to your balance.

• A Start Your Server design that fails is refunded in full.
• A Plugin Builder build that fails before it writes anything is refunded in full. If it stops part-way, you pay only for the tokens it used before it stopped.
• If a run is cut off by a restart on our side, a daily cleanup returns the whole hold.

Designs covered by Premium's free allowance use no credits. Every hold, charge and refund is listed on the AI Credits page.

Every message you send to the designer is one design turn, whether it is your first description, a change or an answer to a question it asked. Starting from a template, editing by hand and the build itself use no turns.

• A server with Premium gets 50 free design turns for its lifetime. They are counted per server and per account, and a turn is free only while both have some left, so a second Premium server does not give you another 50.
• Every other turn is paid from the AI credit balance of the person who sends it. The line above the message box shows what the next turn usually costs; while it runs, YourBot holds the most it could cost and refunds the rest when it finishes.
• By default a server can run up to 40 turns a day.

Buy credits on the AI Credits page.

No. If a design turn fails, because the AI service is busy, returns an error or takes too long, the hold on your credits is released in full and no free design is used. A paid turn that fails says Nothing was charged. in the chat. A design that runs past 6 minutes is stopped, with a tip to use a shorter description or ask in two steps. Your message stays in the conversation, so you can send it again. If the design task itself crashes, the hold is refunded automatically, usually within a day. You only pay for turns that come back with a reply: if the layout arrives but the starter posts couldn't be written, you pay for what was used and can ask for the posts in your next message.

Yes. YourBot doesn't guarantee a Premium price for the life of your subscription. If the price of your subscription changes, you get notice by email or a dashboard notification before it takes effect. The new price applies from your next renewal after that notice, and you can cancel before that renewal so you are never charged it. If you cancel and subscribe again later, you pay the price in effect then. Current prices are on Pricing, and the terms are in section 13.6 of the Terms of Service.

Email legal@emberstreamstudio.com with "Security" in the subject line and the steps to reproduce the issue. The team aims to acknowledge reports within 3 business days. Leave real user data and credentials out of the report.

While you test, use only servers and accounts you own, don't run denial-of-service or destructive tests against the live platform and give the team reasonable time to fix the issue before you disclose it. YourBot will not take legal action over good-faith research that follows these rules, leaves other people's data alone and goes no further than needed to show the issue. The full policy is on the Security page, and the same contact is published in security.txt.

Your server list shows the servers you own or where you have Administrator or Manage Server in Discord, plus any where you were given dashboard access and are still a member. Servers without the bot are listed too, marked Not installed with an Invite bot button. If one is missing:

• Check that you signed in with the Discord account that is in that server.
• The list can be up to 15 minutes behind Discord. If you just joined the server or just got the permission, sign out and back in to reload it now.
• If you need dashboard access without those Discord permissions, ask the server's owner to add you on their Access page.

Look at what the member sees:

• It isn't in their command list. Sentinel's moderation commands and /group-admin only show for members with the matching Discord permission, such as Ban Members or Manage Server. If a command is missing for everyone, press Re-sync commands under Health on Bot Settings. If that doesn't help, authorize the bot again with the invite link (for a custom bot, + Invite to Server on Bot Settings); it stays in your server.
• A private reply refuses it, such as "You need one of these roles to use this command" or "This command is on cooldown". A rule on the service's Commands page blocks it, so change it there.
• The reply says the service isn't enabled. Switch it on in Services.
• It shows twice. Both the shared bot and your custom bot are in the server. The shared bot's copy only replies that the server uses a custom bot, so use your own bot's.

YourBot reads messages as they arrive so features such as Sentinel's filters can check them. Analytics records who posted, in which channel and when, never the text. Message text from your server is stored only in these cases:

• Tickets: a transcript of each closed ticket.
• Sentinel message log, when it is switched on: deleted and edited messages, kept 30 days by default. To show what a deleted or edited message said, Sentinel holds a copy of each new message for 72 hours, then drops it.
• Sentinel cases and reports: a few messages from around the flagged message, kept 30 days by default, plus a short excerpt that stays with the case.
• Sentinel checks of old messages: when you run one, a short excerpt of each message your filters match, kept with the check's results.

Marketplace plugins see message text, and can keep it, only if you allow it when you install them.

Your server's data lives in YourBot's database, which runs on Google Cloud in the us-central1 region in the United States, alongside YourBot's bot services and marketplace plugin sandboxes. Payments go through Stripe and the AI features send their requests to Anthropic, both based in the United States. There is no setting to keep your data in another region. If you need it kept in a specific country, email legal@emberstreamstudio.com, the contact in the Privacy Policy.

The AI features are Start Your Server, the Plugin Builder and Sentinel's AI setup. When you use one, YourBot sends only what that feature needs to Anthropic, its AI provider:

• Start Your Server: your description and follow-up messages, plus the layout of the server you are designing for (such as category, channel and role names and IDs, which services are on and which other bots it has). If you click Scan my server, it also sends what those other bots posted there (such as welcome messages and panels) and a count of their recent actions.
• Plugin Builder: your plugin description and instructions and, when you edit a plugin, its current code and dashboard.
• Sentinel AI setup: your description of the community and its moderation goals, plus the strictness you pick.

Messages your members write, member lists, moderation cases and billing details are never sent. YourBot saves the results so you can review and apply them. The Privacy Policy says Anthropic's terms do not let it train on this data and that YourBot does not train models on it either.

Essential cookies keep you signed in and protect accounts, such as your session cookie and a random device ID used to catch accounts made to dodge bans. Others remember your language and a referral code you arrived with. These are always on.

Optional tracking runs only on public pages such as the home page and Pricing. It starts only after you click Accept on the cookie banner: Google Analytics, plus X and Reddit advertising pixels that measure whether our ads bring visitors. If you click Decline, none of them load. The signed-in dashboard never loads them.

To change your choice, click Cookie settings in the website footer or Manage Cookie Settings in the Cookies section, which lists every cookie. Declining there removes the optional cookies.

Staff can see it, but they can't edit your service settings. They have no role on your server, so saving changes on your dashboard stays limited to the people you gave the Owner or Manager role.

• Read-only view: to troubleshoot a problem, staff can open a read-only view of your server's dashboard. It blocks every change, can't open Bot Settings or the Access page and closes after 30 minutes by default. Opening it is logged.
• Admin tools: staff tools show a server's settings, services, marketplace plugins and bot setup and allow support actions such as restarting or pausing a custom bot, removing a marketplace plugin or changing a subscription.

Both require staff to pass two-factor authentication. The Security page has the details.

You decide when you install it. Under Permissions & Install on the plugin's marketplace page, What this plugin can do lists every capability the plugin asks for. Anything you leave unchecked stays off, and the plugin's calls that need it are refused.

Message text stays private by default. A plugin sees what members write only if you tick its Read message content capability (marked SENSITIVE) or pick Let this plugin read message text under Message privacy. Otherwise it sees that messages were sent but not what they said.

To review or take back access later, click Details on the plugin's card on Services, change the boxes and click Update permissions. The card shows the capabilities you approved and shows content access when the plugin can read message text. Installing a plugin or changing its permissions needs the Owner or Manager role on the server.

YourBot's Terms of Service cover every marketplace install and purchase. Under them:

• The plugin is made by an independent developer, not by YourBot. A developer may also have terms of their own, which apply alongside YourBot's.
• You pay through Stripe, separately from your Premium subscription.
• A refund request goes to the developer first and moves to YourBot staff if the developer does not answer in time. Staff can review any request, and their decision is final.

The developer is bound by the Marketplace Developer Agreement, which covers their side of the sale, such as revenue sharing and payouts.

Open the Marketplace. The tiles at the top browse by category (Community, Games, Organization and Tools, each shown once it has plugins), and Most Popular sorts by installs. The game chips and #tag chips below them narrow the list to one game or tag, and the search box finds plugins by keyword. Sort orders results by featured, name, popularity, rating, newest, recently updated or price. Signed in, the toolbar adds more filters:

• price (Free or Paid) and rating (4+ stars or 3+ stars)
• billing type (One-time, Subscription or Annual)
• game and genre lists and By developer…
• Free trial, On sale, Saved and Following

Sign in and open the plugin's marketplace page:

• Developer: the name under the title opens the developer's profile, and the More from section lists their other plugins.
• Reviews: star ratings and written reviews, tagged Owned or Verified purchase where that applies, plus any Response from the developer.
• Release history: What's New shows the latest changelog and Release history lists every published version with its date and notes.

Click Follow to get a notification when a new version comes out. What's shipping lists recent releases across the whole marketplace.

It means YourBot staff reviewed that listing by hand and gave it the badge. Staff add and remove the chip themselves, using the bar described on Quality Standards, and plugins with the chip come first in the marketplace's default Featured order.

A plugin without the chip has still been checked. The chip is separate from the safety review every version goes through: each version is scanned automatically when it is uploaded, and staff review it before it goes live unless the developer has trusted status. Every marketplace plugin also runs sandboxed, chip or not.

Yes, a license covers the server it was bought for: the one selected under Installing to when you paid. Some plans cover more than one server, and the plan card says how many.

A license can't be moved to another server on its own, with one exception: when you move a one-server Premium subscription to another server with Assign on the Account page, plugin subscriptions you bought for the old server move with it. One-time purchases stay with the server they were bought for.

Open Permissions & Install on the plugin's marketplace page (for a paid plugin, after you buy a plan). It lists:

• What this plugin can do: each capability it requests, such as sending messages, managing roles or calling websites, tagged SAFE, STANDARD or SENSITIVE.
• Proxy domains: the websites it wants to reach.
• Message privacy: whether it may read message text.

Everything starts ticked except reading message text, and anything you untick stays off. The plugin still installs, but features that need a refused permission don't work because YourBot blocks those calls. To change your choices later, reopen the section, adjust the boxes and click Update permissions (Manager role needed); saving also moves the plugin to its newest version. If a new version asks for more, auto-update pauses on your server until you approve it there.

Yes, and that is the default. On the plugin's marketplace page, open Permissions & Install and under Message privacy keep Keep message text private (recommended). If the plugin requests Read message content, leave that box unticked too. The plugin is then told a message was posted (which message, where and when) but never gets its text, including when it fetches past messages.

Choosing Let this plugin read message text or ticking Read message content gives it the text. You can switch either way later with Update permissions. A feature that reacts to what people write won't work while the text stays private.

Yes. Once the plugin is installed and has more than one published version, its marketplace page shows a Version card with a version list. Pick a version and click Switch. Switching turns auto-update off, so the plugin stays on that version when new ones come out. You can only switch to a version whose permissions you have already approved.

To go back, pick the version marked latest, click Switch, then click Enable auto-update. Saving Update permissions also moves the plugin to its newest version. You need the Manager role and Premium on the server.

Send it to the plugin's developer:

• In Discord, run /pluginbugreport, pick the plugin and describe the problem.
• On the plugin's marketplace page, select the server it happened on, open Report a problem in the Support card, say what went wrong and click Send report.

Your reports and the developer's replies show under My reports on the plugin's page. The same card has Ask the developer a question and, if the developer set one, a Developer support link. You can have up to 10 open reports per plugin.

Yes. Plugin UI is switched on by default in the Plugin Builder. Choose how it's built:

• Quick dashboard: pages of platform widgets such as stats, tables, charts and settings forms. Change it later with Open editor under Custom dashboard on the plugin's Settings tab.
• Design your site: up to 6 custom pages in the look you describe, with up to 4 images you upload. Change it later by editing its page files in the plugin's zip and uploading a new version.

Add notes on what each page shows and who it's for. The plan lists the pages before the build, and the draft review previews them with sample data. After install, people with a dashboard role on the server open it with Open Dashboard on the plugin's marketplace page, and each page can be limited to a higher role.

Click Plan it before building. A fast model turns your description into a plan you review before the build is charged:

• the slash commands and their options
• the storage it will use, the Discord events it listens to and any scheduled jobs
• the dashboard or site pages, when Plugin UI is on
• a few optional questions; anything you leave blank, the builder decides

It also lists anything it adjusted to fit the platform, such as renaming a command that clashes with a YourBot command. To change the plan, type the change and click Replan, or rewrite the description with Edit the description. Approving the plan starts the build. Each plan or replan costs a small amount of AI credit.

You pay for the tokens a build actually uses, at the per-token price of the model you pick. Each model in the list shows what a typical plugin has cost on it when there is enough history, and otherwise the hold a build on it takes.

The budget you pick (Standard, Large or Max) is a length limit, not a quality setting. It caps how much the build can write in one pass and sets the hold taken from your AI credits before it starts, so a bigger budget means a bigger hold, not a bigger bill for the same plugin. When the build ends you're charged for what it used and the rest of the hold comes back. A build that runs out of room stops partway and continuing it costs another pass, so pick a bigger budget for a large request.

Yes. On the draft review, Download files gives you a zip with __main__.py, manifest.json, the README and requirements. After Create plugin from this draft it's an ordinary plugin in your Developer Portal: on its Versions tab, Source shows the files and Zip downloads them. Edit them locally, then add the result as a new version with Upload a zip, or push it to a linked GitHub repo and use Pull from GitHub.

To make changes by describing them instead, use Edit with AI on the plugin's Overview tab, which is paid from AI credits like a build. Builds you haven't committed are kept under Saved builds for 30 days, where you can review, resume or download them.

If you sell paid plans, the Developer Agreement asks you to give your customers reasonable support, keep a working support contact in your listing and answer refund requests and platform questions within a reasonable time. Persistently failing paying customers can lead to enforcement. Requests reach you here:

• Support URL on your plugin's Settings tab shows as a Developer support button on its marketplace page.
• Bug reports from the plugin's page and /pluginbugreport land on the Reports tab, where you can reply.
• Questions from buyers land on the Questions tab.
• Refund requests land on Refunds; one you don't answer within 7 days goes to YourBot staff.

Your plugin's page can show buyers how quickly you usually reply.

Yes. Plugins are written in Python with the yourbot-sdk package: install it with pip install yourbot-sdk (Python 3.10 or newer). Its command line tool scaffolds a plugin with yourbot new, runs it on your machine against a mock host with yourbot dev and runs the platform's pre-submit checks with yourbot validate.

A plugin ships as a .zip with __main__.py (the entry point) and manifest.json at its root. It can add a requirements.txt of plain PyPI packages, which the sandbox installs as prebuilt wheels; the platform supplies the SDK itself. Create the plugin with + New Plugin in the Developer Portal, then add your code on its Versions tab with Upload a zip or Pull from GitHub.

Yes:

• Slash commands: list each one under slash_commands in manifest.json with its description and options, handle it with @plugin.on_slash_command("name") and reply with ctx.interaction.respond(). Names used by YourBot's own commands are refused.
• Buttons and menus: attach components to a message sent with ctx.discord.send_message(), then handle clicks with @plugin.on_component("custom_id") (or prefix=) and pop-up forms with @plugin.on_modal_submit("custom_id").
• Scheduled jobs: decorate a function with @plugin.cron("0 9 * * *") and add a matching {"spec": "0 9 * * *", "name": "<function name>"} entry to cron in manifest.json. You can have up to 5, they run in UTC and no more often than every 5 minutes. @plugin.schedule does not run on the marketplace.

Yes, through YourBot's HTTP proxy, since the plugin has no network of its own. Call ctx.http.get(), ctx.http.post() or ctx.http.request(), which need the proxy:http capability. List every domain you call in proxy_domains_requested in manifest.json; web addresses written as strings in your code are added on upload too. A listed domain also covers its subdomains.

Each server approves your domains when it installs the plugin and can refuse any of them. For an address only that server knows, such as its own game server, call ctx.http.allow_host() from a slash command run by someone with Manage Server (or a dashboard action by a manager): that exact host is then allowed on that server only. The proxy blocks private and internal addresses and limits requests per minute on each server.

List the ones your code needs in capabilities_required in manifest.json. There are 18:

• Storage: storage:kv, storage:sql and storage:secrets
• Discord: discord:send_message, discord:edit_message, discord:delete_message, discord:add_reaction, discord:read, discord:manage_webhooks, discord:manage_channels, discord:manage_roles, discord:moderate_members (timeouts), discord:kick_members and discord:ban_members
• Other: interaction:respond (replying to commands, buttons and forms), proxy:http, proxy:websocket and events:message_content

Ask only for what you use. On upload, the platform adds any capability your SDK calls need that you left out. Each server can refuse any capability at install, and a refused call raises CapabilityError. Receiving events such as member joins needs no capability, but message text needs events:message_content or the server's consent.

A version is flagged when uploading its zip or pulling it with Pull from GitHub on the Versions tab raised a warning, for example a risky import (import socket, import ctypes or importlib) or capabilities the platform had to add to your manifest. A flag doesn't reject the version. When you click Submit it joins the staff review queue like any listed version, and the reviewer sees what was flagged.

It does close two shortcuts: a trusted developer's version is queued for review instead of publishing straight away, and Publish privately refuses it because no reviewer would see it. To clear the flag, remove the cause and upload or pull a new version.

As soon as Sentinel Moderation is switched on, these run without any setup:

• Join screening: every new member gets a risk score from account age, a missing avatar and how many people joined in the last minute. The riskiest accounts are kicked, high-risk ones are quarantined and lower-risk ones get a Suspicious Join note in the log channel.
• Raid detection: raid mode switches to hard when 10 people join within a minute or when a group of look-alike accounts joins together (both on by default). Hard mode quarantines every new join by default. The look-alike accounts are quarantined too.
• Moderation done in Discord: bans, kicks, timeouts, server mutes and deafens placed in Discord itself are recorded as Sentinel cases.
• Platform bans: accounts banned from YourBot are flagged in the log channel.

Quarantining needs a quarantine role and the notes need a log channel. The wizard on Setup creates both. It also sets up filters, anti-nuke, the message log and server logs, which wait until you set them up. The server owner is never kicked or quarantined by these checks.

On Setup, pick a level under Choose how strict, leave Act right away off and click Run setup. The filters install in Testing: nobody is warned, timed out, kicked, banned or quarantined and no message is deleted. Instead, each match posts a note in the mod log saying what the filter would have done, and a filter that would have punished someone also records a case marked Testing on History > Cases.

The wizard also turns on the recommended protection: anti-nuke with quarantine, restore and the hold, the bot-add rule, escalating timeouts and the message log. Anti-nuke is not part of Testing: mass damage quarantines the account straight away, and a single risky change by an admin is undone and reported. Its settings are on the Anti-nuke page.

Testing covers neither automatic raid mode nor join screening, which quarantines or kicks very high-risk new accounts. Filter packs you add later from the Filter packs page enforce straight away. When you are happy with what the notes show, switch Spam & scams from Testing to On. To keep one filter testing, open it and turn on Test this filter on its own.

They are the three levels on Sentinel's Setup page. Each adds built-in filter packs and includes everything in the level below it:

• Relaxed: Anti-Spam Starter (message spam, repeated copypasta, all caps and emoji floods) and Phishing Defender (deletes known phishing links and warns, quarantine on repeats).
• Standard, the default: adds Invite Control (deletes Discord invite links and warns), Mass Mention Guard (5 or more mentions in one message) and Executable Attachment Block (.exe, .bat, .msi and similar files).
• Strict: adds Anti-Raid Basic (quarantines accounts under 3 days old when they join and times out anyone sending 3 messages in 10 seconds), New Account Guard (quarantines accounts under 7 days old when they join), Hate Speech Filter (starter) (a short word list to extend) and High-Risk User Containment (removes links from members in the caution risk band or higher).

Every filter can be edited or deleted afterwards on the Spam & scams page.

Yes, three ways:

• Try it in a filter's panel tests sample text against the checks you are editing, before you save. Message spam and Copy-paste spam need several messages. Checks about the author, such as account age, roles or risk, only use a placeholder there.
• Turn on Test this filter on its own in a filter's panel (Test it on its own first when you add it) and no action is taken: each match posts a note in the mod log saying what the filter would have done, and a filter that would warn, time out, kick, ban or quarantine also records a case marked Testing. Setting Spam & scams to Testing does the same for every filter.
• The Check old messages page runs your filters over up to 2,000 past messages in each of up to 25 channels. Report only lists what they would catch and changes nothing. Filters using Message spam, Copy-paste spam, File floods or Spam score are left out.

To be told about matches without touching the member, give a live filter only the Tell the mods action. It posts a note to the channel you pick or to the log channel.

Yes. On the Spam & scams page, add a filter with one of these checks and a Delete the message action:

• Words and phrases: your word list. How they match can be contains, exact or regex. Contains and exact also catch look-alike letters, leetspeak and spaced-out or stretched words unless you untick that box.
• Links and invites: Invites to other Discord servers, Every link or a list of Sites to block.
• Scam links: links on public phishing lists, plus your own Block these too list under Your own scam sites on Spam & scams.
• Brand-new websites: links to domains registered in the last 30 days by default.

Edited messages are checked again. The Invite Control and Hate Speech Filter (starter) filter packs are ready-made versions. To stop a message before it is posted at all, add Discord's own keyword or word preset rules on the Discord AutoMod page.

Yes, with these checks on the Spam & scams page (default limits in brackets):

• Message spam: one member sending too many messages too fast (5 within 10 seconds).
• Copy-paste spam: the same message repeated (3 times within 60 seconds).
• Mass mentions: user and role mentions in one message (5).
• ALL CAPS, Emoji spam, Walls of text and Sticker spam for shouting, emoji walls, blank lines and stickers.
• File floods: many messages with files or images in a short time (4 within 30 seconds).
• Spam score: one score per member that every message adds to, with more for mentions, links, files, emojis, repeats, extra lines and capitals. It halves every 10 seconds and the filter acts at 100, so mixed spam that stays under each single limit still adds up.

The Anti-Spam Starter, Mass Mention Guard, Sticker & Wall-of-Text and Heat Spam Filter filter packs set these up for you. Reaction spam is handled by Reaction spam on Spam & scams, which stays off until you set a limit. Discord's own mention limit and spam filter can be managed on the Discord AutoMod page.

Every join is screened automatically: account age, a missing avatar and join bursts add up to a risk score. High scores are flagged in the log channel, quarantined or kicked. For your own filters, set Runs on to When someone joins or When someone changes their name and use:

• New accounts: accounts younger than a number of days (7 by default). It only works on filters that run When someone joins.
• Avatar: members still on the default avatar.
• Names: words or patterns in the display name, the username or both.
• Link in their name: an invite or a link in the name, a common advertising trick.
• Fake staff: a name or avatar copied from a moderator or the owner.

Then add an action such as Quarantine, Kick or Fix their name. The Filter packs page has ready-made packs: New Account Guard, No avatar on join (installed switched off), Advertising Accounts, Staff Impersonation and Nickname Sanity.

Yes, at two levels:

• Server-wide: members holding any of the Moderator roles in Sentinel Settings skip every filter, the honeypot and reaction spam checks. The setup wizard fills that list with the moderator roles it finds. Bots are never checked. The server owner is never timed out, kicked, banned or quarantined.
• Per filter: open the filter and go to Where. Only in these channels limits it to the channels you pick, Never in these channels skips others and Never for lets members with any of those roles through.

Channel scoping has no effect on filters that run on a member join or a nickname change, because those events happen outside any channel.

A filter can run any of 13 actions, several at once:

• Delete the message
• Warn, a warning on the member's record that is also sent to them by DM by default
• Time out, from 1 minute to 7 days
• Kick
• Ban, permanent or for 1 hour, 1 day, 7 days or 30 days
• Quarantine, which gives the member your quarantine role
• Tell the mods, a note in a channel you pick or the log channel
• DM them, your own message to the member
• Fix their name, which strips words from a nickname or replaces it
• Server mute, Server deafen, Disconnect from voice and Move to a voice channel for members in voice

Actions can also wait in a warning step, such as Once they have 2 warnings: they run only once the member has that many warnings, so one filter can warn first and time out repeat offenders. Warnings, timeouts, kicks, bans, quarantines and voice actions each create a case.

Nearly. A numbered case is created when:

• a moderator uses /warn, /timeout, /kick, /ban, /softban or /quarantine
• a moderator acts on a member report from the Reports tab of the Inbox
• a filter warns, times out, kicks, bans, quarantines or uses a voice action (while it is testing, the case is marked Testing)
• join screening or raid mode quarantines, kicks or bans a new member
• someone bans, kicks, times out, server mutes or server deafens a member in Discord itself. This reads the audit log and can be turned off with Record bans, kicks and timeouts done in Discord itself in Sentinel Settings.

A filter that only deletes a message, posts an alert, sends a DM or renames someone makes no case. Neither does an action Discord refuses, for example when the member's highest role is above the bot's. Cases are listed on History > Cases and moderators can see a member's recent ones with /history.

Yes. Open the case from History > Cases:

• Why this fired shows the filter and its evidence, such as the matched term or pattern with an excerpt, a count against its threshold, a domain, an invite code or a join's risk signals.
• Channel transcript holds up to 11 messages from that channel around the moment the filter fired. It is kept for the days set under Records in Sentinel Settings, 30 by default. Cases marked Testing have no transcript.
• Staff notes, the case's activity, related reports and the member's warn count and risk score are on the same page.

Yes, three ways once Sentinel is on:

• /report with a member and a reason. It also saves the last 30 messages in that channel by default.
• Right-click a message and pick Report Message under Apps, then give a reason. The report is tied to that exact message.
• React with the report emoji, if you set one under Members can report with a reaction in Sentinel Settings. The reaction is removed straight away and each member can report this way once every 5 minutes by default.

Reports arrive in the Inbox. On its Reports tab, staff can Mark reviewed, Dismiss or take action with a warn, timeout, kick or ban, which creates a case. Settings can also DM reporters when their report is resolved and ping your mod roles about high-risk reports. Members cannot report themselves or a bot.

Yes. The web appeal page is yourbot.gg/appeal/ followed by the server ID. The DM Sentinel sends with a warning, timeout, kick or ban includes the link. The member signs in with Discord and sees only their own warnings, timeouts, kicks, bans and quarantines on that server, each with a form to explain why it should be reversed (at least 20 characters, one appeal per case). Members still in the server can also use /appeal with the case number.

Appeals arrive in the Inbox. On its Appeals tab, staff click Approve or Deny. Approving overturns the case and lifts a timeout, ban or quarantine. The member gets a DM with the decision either way. The appeal page only works while Sentinel is switched on for that server.

Yes. Every lock records what it changed and lifting it puts back exactly that:

• /unlockdown and the Unlock button under Lock down on Sentinel's Home page set each channel's Send Messages permission for @everyone (or for the locked role) back to what it was, so a channel that was already closed stays closed. A lock with a timer does the same when its minutes run out.
• Turning raid mode off, with Stop raid mode on Home, /raidmode off or the automatic switch-off (30 minutes by default), resets every text channel's slowmode to its value from before raid mode came on. When raid mode is switched off from lockdown, it also restores @everyone's posting permission and your server's verification level.
• Paused invites are only resumed if Sentinel paused them.

Server-wide locks never touch Sentinel's own log channels.

Yes. History > Members is a risk roster: members ranked by risk band with their score, warnings, cases and last action. Click a member for their history page: their recent cases, an action breakdown, Why this score (active cases, watchlist, quarantine, pending reports, denied appeals and recent automod hits) and buttons to release a quarantine or change the watchlist. In Discord, moderators can run /history on a member.

Warnings stop counting after the days set under Warnings in Sentinel Settings, 30 by default. Filters read the live count through their warning steps. Each warning is also worth one point; points can fade by a set number a day (off by default). With Repeat timeouts get longer on, each automod timeout can last longer than the last. Risk bands (track, caution, high, critical) can watchlist a member, post a notice, ping your mod roles or quarantine automatically.

Yes. On Panels, open a saved panel and click + Add Button. A panel holds up to 25 buttons, each with its own label, emoji and colour. Open a button's Advanced routing to send its tickets somewhere else:

• Override team: tickets from this button go to that team, which gets access to them and the ping.
• Override form: a different intake form.
• Extra role access: one more role that gets access to these tickets when the panel uses Private Channel mode.
• Link to category, Channel name template, Open Tickets Category and Closed Tickets Category.

Empty fields use the panel's own settings. A button linked to a category takes its team and form from that category. To have members pick from a menu after clicking a button that has no routing of its own, add entries on the panel's Category menu tab; each entry has its own Route team and Route role. Button changes on a posted panel are pushed to Discord automatically.

Yes. Right-click the message, open Apps and choose Start ticket. The ticket opens for the person who used the menu, and the bot posts a quote of the message in it with the author, the channel and a link. Set it up under Start a ticket from a message in Tickets settings:

• Who can use it: Staff teams and Manage Server by default. Choose Everyone to let any member use it, or Manage Server only.
• Panel to use: the panel whose form, team and limits apply. It starts at First enabled panel; panels in Form mode are skipped.
• Add the message author to the ticket: on by default. Turn it off for reports the author should not know about.

To make the message's author the owner instead, set Who owns a ticket started from a message under Closing and deleting tickets to The message author, with the staff member added. That only applies when staff use the menu and the author is another member, not a bot; the ticket then skips the author's limits, cooldown, support hours and the panel's form. The panel's Access rules apply to whoever uses the menu. Staff can also open a ticket for any member with /ticket open.

Yes. Each panel picks one under Channel Mode on its Ticket setup tab:

• Private Channel: a new channel in the Open Tickets Category that only the member, your staff, the bot and any observer roles from the panel's Access page can see (observers can read but not write). On close the member loses access, or keeps read-only access if the Access page says so, and the channel moves to the Closed Tickets Category if you set one.
• Private Thread: a private thread in the Thread Parent Channel you choose. The member and the team's members are added. On close it is archived and locked.
• Form: no channel. The intake form answers post to your Review Channel with Accept and Reject buttons. Accept can give the Role granted on Accept, and the member gets your Accept DM or Reject DM. Staff can't chat with the member, so attach an intake form.

A close request (from staff, the inactivity rule or an automation) has Close now and Keep it open buttons. A closed channel or thread shows 🔓 Reopen, 🗑️ Delete and 📜 Transcript buttons for staff; Delete asks first. To have closed channels removed for you, set When a ticket closes under Closing and deleting tickets in Tickets settings to delete the channel a set time after closing or right away. The transcript is saved before any delete.

Build forms on Forms with + New Form, add fields, then choose the form as a panel's Intake Form (or a single button's Override form). A field can be:

• short or paragraph text, a number (with optional Min value and Max value) or a date typed as YYYY-MM-DD
• a dropdown or multi-select with up to 25 choices, or a yes or no toggle
• a section header that shows text and asks nothing

Discord shows at most 5 text fields at once, so only the first 5 visible text fields appear. Dropdowns, multi-selects and toggles are asked one at a time before those and don't count. Pre-fill from Discord can fill a field with details such as the member's username, roles or server join date; set it to Hidden (silent) to record it without asking. Answers show in the ticket's first message and on its dashboard page.

Yes. On Forms, add the field, click Edit on it and fill in Show only when: an earlier Field, an Operator (= equals, contains or any answer) and a Value, then click Save changes. The field is skipped unless the answer matches. Matching ignores capital letters, and equals matches any one pick of a multi-select. For a yes or no toggle the value is Yes or No; for a dropdown or multi-select, use the choice's value (the part before |).

Dropdowns, multi-selects and toggles are asked first, one at a time, so later pickers and the text fields can depend on them. Text fields are shown together in one Discord form, so a text field that depends on another text field is never shown.

Server-wide limits are in Tickets settings:

• Max open tickets per user: 1 by default.
• Max tickets per user per day: how many one member may open in any 24 hours. 0, the default, means no daily limit.

Each panel adds its own on its Ticket setup tab:

• Open ticket limit for this panel: how many tickets the panel can have open at once across all members, up to 500. 0 means no limit.
• Cooldown between tickets (seconds): how long a member waits after opening a ticket on that panel before opening another there, up to 604,800 (7 days). 0 turns it off.

Members holding a role in Roles the limits do not apply to skip all four. The Blocked from opening tickets list and support hours still apply to them. A member who hits a limit gets a private reply saying which one.

To decide who may open tickets at all, use the panel's Access page: Only these roles, Never these roles and Staff only, for the whole panel or for one of its buttons. A blocked role wins over an allowed one, members with Manage Server always get through and the check runs when the button is clicked, before any form.

Yes.

• Claim: click 🙋 Claim on the ticket's first message, run /ticket claim or click Claim in the dashboard Queue. Once it is claimed the button reads 🔓 Unclaim: the claimer, a member with Administrator or the server owner can unclaim it, and other staff are refused. If the panel's Claiming page lets staff take over a claim, a click from anyone but the claimer takes the ticket over instead. Whether staff must claim a ticket before closing it is up to you: Staff must claim a ticket before closing it, under Closing and deleting tickets in Tickets settings. Servers that used Tickets before the setting existed have it on, auto-setup on a new server leaves it off and the switch shows where yours stands. It never applies to the member who opened the ticket.
• Assign: /ticket assign hands the ticket to a staff member as its claimer. On Teams, set a team's Auto-assign to Round-robin or Least loaded to assign each new ticket automatically; Manual leaves it to staff.
• Transfer: on the ticket's dashboard page, pick a team under Team and click Assign. The new team gets the channel, the old team loses it and the claim is released.

Staff here includes anyone with Manage Server and the members of the ticket's team.

Yes. In Discord, click 📝 Note on the ticket's first message or run /ticket note; the note is saved without being posted in the ticket. On the dashboard, open the ticket and use Add note under Staff Notes (Owner or Manager role needed). Notes are listed on the ticket's dashboard page and are never posted in the ticket itself. Members never see them: the transcript DMed to the member leaves them out.

Yes. Every ticket has a priority: Low, Normal (the default), High or Urgent. Staff change it with /ticket priority in the ticket or the Priority buttons on its dashboard page, and the Queue filters by it.

Response-time targets are SLA policies. In Tickets settings, click + New SLA Policy, set a First Response Target (minutes), a Resolution Target (minutes) and an optional Breach Ping Role, then choose it as the SLA Policy on a panel's Routing & form tab. New tickets from that panel show when a first response is due. When a target is less than 30 minutes away, the bot posts an ⏳ SLA Approaching warning in the ticket, which pings nobody. If a target passes, the bot posts an SLA breach warning in the ticket and pings that role. The first message from anyone other than the member, typed in the ticket or sent from the dashboard, counts as the first response. Priority does not change the targets.

To act before a target passes, a rule on Automations can ping the ticket's team, post a message or post a canned response when a ticket has waited a set time for staff. When another team should take over, staff can escalate the ticket to another panel with /ticket escalate or Escalate to another panel on its dashboard page, once the panel's Escalation page lists where its tickets can go. The ticket then moves to that panel, its SLA policy and, by default, its team; under a different policy the targets it has not met yet start again.

Yes. Open the ticket from the Queue. Its Channel Chat shows the conversation live, and anyone with the Owner or Manager role can type a reply and click Send. The bot posts it in the ticket with your name in bold at the start. A reply can be up to 1,900 characters and can carry one file of up to 8 MB. Replies sent from the dashboard can be edited or deleted there. The same page has claim, close, priority, team and staff note controls.

A closed ticket has to be reopened before you can reply, and a ticket in Form mode has no chat because it has no channel.

No. Members reply inside their ticket channel or thread, and messages sent to the bot by DM do not reach the ticket. The bot can DM members updates with a link back to their ticket. Switch them on under Member notifications in Tickets settings; all are off by default:

• When their ticket opens
• When a staff member claims it
• When staff reply and the ticket is waiting on them

When a ticket closes, the bot also DMs a rating prompt while Ask members to rate their support is on (the default), plus the transcript if DM the transcript to the member when their ticket closes is on. You can rewrite the opened, claimed, staff reply and transcript DMs on the Messages page, and a canned response can be set to go to the member by DM. A member can stop all ticket DMs from your server with /ticket dms off.

Both.

• On Canned Responses, click + New response and fill in Title, Category and Response body; Edit changes a saved one. In a ticket, staff run /ticket respond and pick one by name; the bot fills in placeholders such as {member}, {staff.name} and {ticket.number} and posts it signed with their name. Tick Send to the ticket owner's DMs instead of the ticket to have /ticket respond send it to the member by DM, unless they turned ticket DMs off. On the dashboard, click Copy and paste it into the ticket's chat.
• On Knowledge base, click + New article and write a title, keywords and up to 4,000 characters of text. Members find published articles with /kb search and /kb browse. With Suggest articles when a ticket opens on (the default), the bot posts up to three articles that match the ticket right after its welcome message, so some tickets answer themselves.

Yes, and it is off by default. In Tickets settings, under Inactivity, set Ask to close after this many hours without a message (up to 720) and Countdown before the automatic close (hours) (1 to 168, 24 by default). When a ticket goes quiet that long, the bot posts a close request with the countdown. If the member who opened it replies, the request is cancelled; otherwise the ticket closes and its transcript is saved.

Every close request has two buttons: Close now runs the normal close, and Keep it open lets the member who opened the ticket cancel the request, as a reply does. Staff can start the same countdown by hand with /ticket closerequest (1 to 168 hours, 24 by default). Separately, Auto-close when creator leaves closes a member's open tickets when they leave the server.

For more control, add rules on Automations, up to 10 per server. When the member has not answered staff for a set time, or a set time after they leave the server, a rule can post a message, start the close countdown, close the ticket or delete it. Each rule covers every panel or only the ones you pick, and the page lists what the rules did recently.

Closed ticket channels are deleted after the number of days in Delete closed ticket channels after (days) in Tickets settings, from 0 to 365. 0 keeps them, and a new setup starts at 7 once you run auto-setup or save Settings. If a channel has no transcript yet, the bot saves one before deleting it.

To remove channels sooner, set When a ticket closes under Closing and deleting tickets to delete the channel a set time after closing (1 minute to 7 days) or right after closing. Staff can also delete a closed ticket's channel with its 🗑️ Delete button or Delete channel on its dashboard page, and /ticket delete closes an open ticket first. These save the transcript first and keep the channel if it can't be saved. Reopening a ticket before a timed delete keeps its channel.

Transcripts have no expiry. They are kept until you delete them under Data Management in the same settings: set Older than (days), tick the confirmation box and click Delete tickets. That removes closed tickets older than that, with their transcripts, notes, ratings and activity log. The Transcripts page lists all of them, newest first, 50 a page. If you remove the bot that runs your server, a nightly job deletes the server's ticket data 30 days later, unless the bot is added back before then.

Yes, and it is on by default. When a ticket closes, the bot DMs the member who opened it and asks for a 1 to 5 star rating; they can also rate with /ticket survey in the closed ticket. Each ticket can be rated once, and only by that member. To stop both, turn off Ask members to rate their support under Rating survey in Tickets settings; ratings already given stay in your analytics. The prompt is also skipped when the member has closed DMs or turned ticket DMs off with /ticket dms off.

Results are on the Tickets Analytics page: Avg CSAT, Feedback rate (how many closed tickets were rated) and, for managers, each staff member's Avg rating on the tickets they claimed. Export CSV and Export JSON include these figures.

You can search them and download transcripts one at a time. There is no export of every ticket record in one file.

• Search: the Queue search box finds tickets by title or ticket number, closed ones included. Or filter the list by status (including Closed), priority, assignee, team, category and date opened. In Discord, /tickets search does the same for members with Manage Server.
• Each ticket: its dashboard page has an Activity log of claims, transfers, priority changes and closes.
• Transcripts: the Transcripts page lists all of them, newest first, 50 a page, each with Open and HTML or TXT downloads.
• Analytics: Export CSV and Export JSON give totals, not individual tickets.

Once the Analytics service is on, it records:

• Messages: who posted, in which channel and when, whether it was a reply and how many attachments, embeds, stickers and mentions it had. Only regular messages and replies count. The text is never stored.
• Voice: each session with its channel, length and state (muted, deafened or in the AFK channel), plus screen shares.
• Members: joins and leaves, plus which invite brought each new member while Track invites is on (the default; the bot needs Manage Server for it).
• Reactions given and received plus threads created.
• Status and game activity, only if you turn on Status tracking or Activity tracking in Analytics Settings.

Bots are left out by default (Leave bots out), as is anything in Channels to leave out or from members with Roles to leave out.

Yes, for messages, up to a year back. Run setup on the Analytics Setup page starts importing up to 365 days of message history, never more than the Keep data for limit shown on the Settings page. Setup also raises Keep data for to match so the nightly cleanup keeps what was imported.

You can import again under History in Settings: in Import Discord history, choose How far back (7, 30, 90, 180 or 365 days) and click Import history. This does not change Keep data for, so set that at least as long first.

The import reads the text channels the bot can see, along with their active threads and forum posts and up to 100 recently archived public ones per channel. It skips excluded channels, counts only regular messages and replies and never counts a message twice. It also records the join date of everyone still in the server. Voice time, reactions and leaves cannot be imported; they count from the moment the service is on.

Two Analytics pages cover it, and Home sums it up:

• Growth: Members over time, the member count at the end of each day with joins above the line and leaves below it. Do new members stay? shows what new members did after joining (got a role, said hello, joined voice, came back after a week, still here today), how many were Active within a day and how many Left within a day. Its Week by week table has one row per weekly group of new joiners with the share that came back the Next day, A week on and A month on, for the last 4, 8, 12 or 24 weeks. Growth also shows Where they came from and Who left lately.
• Members: Going quiet names the regulars who chatted or joined voice in the last 14 days, then nothing for 5 days or more, and Active members per day charts daily activity.
• Home: the member count and its change, active members and, once three or more regulars have gone quiet, a finding that names them.

Week by week is recalculated once a day.

Yes, on the Best times page. Every hour of the week shows how busy each hour was over the range you pick (7 days to a year), for Chat, Voice or Online (Online needs status tracking). Your busiest hours names the busiest hour, the next two and the quietest, with the peak hour, the total, the weekend share and the active slots, and Plan around it suggests when to run an event, post announcements and have a moderator around. Weekdays and weekends says whether your server leans to weekends or weekdays. Click any hour to see which channels and members were around then. You can also narrow Chat to one channel or Compare with before.

Times follow the Analytics time zone: your server time zone unless you pick another under Time zone in Analytics Settings.

Use the Channels page:

• The channel list shows each channel's messages, or hours for a voice channel, over the range you pick against the same stretch before it, with the change, a Growing, Fading, Steady, New or Quiet badge, how many people took part and when it was last active. Against the period before shows both numbers side by side.
• Ready to archive? lists channels that had messages before but none in the last 7, 14, 30, 90 or 180 days (14 by default), with when each was last active.

Click a channel to open it in a side panel: its messages against the window before, how many people posted, top contributors, an hour-by-day heatmap and the threads started there.

To be told when a channel goes silent, add a Dead channel rule on the Alerts page. Dead channel only looks back as far as Analytics keeps hourly totals, which is twice your Keep data for window.

Yes. The Voice tab of the Activity page shows time in voice and sessions, the typical session (the median) and how long 1 in 20 sessions last (the 95th percentile), voice per day with Most people at once, the Busiest voice channels, Most time in voice and Screen share. It also has Voice duos (pairs of members who spend the most time in voice together) and Coming back each week (members who return week after week).

Elsewhere:

• Best times in Voice mode shows when members are in voice.
• The leaderboard on the Members page ranks by Voice hours, Voice sessions, Days in voice, Screen share hours and Screen shares.
• A Voice peak alert posts when the number of members in voice reaches your threshold.
• An In voice counter channel shows how many are connected right now.

Under Read filters in Analytics Settings, Voice states to leave out can drop AFK, muted or deafened sessions from voice hours.

Yes. While the Analytics service is on, members can run:

• /me for their own stats card
• /stats or /user to look up another member
• /leaderboard, ranked by messages, voice hours or voice sessions
• /top for the top members and channels
• /server for a server overview card
• /chart for messages, voice, members, one channel or one member per day

Cards are posted in the channel. On their own card a member gets a Hide my card button, which stops others looking it up and turns off its public link. Server managers can change the cards' colours and sections in the card designer.

The leaderboard on the Members page ranks members by Messages, Voice hours, Days active, Reactions given, Reactions received, Voice sessions, Days in voice, Screen share hours, Screen shares, Threads started, Channels posted in or Time in the server, over 7 days to a year, with an All-time top 10 under it. In Discord, /leaderboard ranks by messages, voice hours or voice sessions.

Role rewards can use the same kinds of activity as conditions, plus the longest message streak, members invited and a top rank or top percent. That lets you give a role to, say, your ten most active voice members of the month.

Yes, on the Role rewards page. A reward pairs a Discord role with up to 8 conditions, matched all together or any one. A condition sets a minimum, an optional maximum and a window on a metric (messages, voice hours, days active, reactions, threads, tenure, invites and more). It can also be a top rank or top percent. Each reward runs on its own schedule, from every 10 minutes to once a day. It can DM the member or post each run to a channel.

To take the role away when activity falls, tick Revoke when a member no longer qualifies; it comes off on the next run. A reward whose conditions are all All stored data minimums never revokes, because those totals only grow. Permanent keeps the role for good. Inverted: grant to members who do not match makes an inactivity role.

The bot needs Manage Roles with its role above the reward role. Roles with powers such as Administrator or Ban cannot be rewards.

On the Alerts page every rule posts to a Delivery channel you pick. There are five kinds under Rule type:

• Activity drop: messages or active members fell by at least the percentage you set (5 to 99) over the last 1 to 30 days, compared with the same number of days before. It posts again when activity recovers.
• Spam spike: the message rate goes over a number of messages per minute, measured over up to 60 minutes.
• Activation drop: too few recent joiners sent a message or joined voice.
• Voice peak: the number of members in voice reaches your threshold.
• Dead channel: a channel has had no activity for 1 to 365 days. It posts again when every channel is active.

Cooldown (hours), from 1 to 168, stops repeats. Spam spikes and voice peaks are checked every 5 minutes, the other three once an hour. Run setup adds an Activity Drop Warning for a 30% drop over 7 days. Home and the Chat tab of Activity also flag an unusual spike or drop in today's messages, on the dashboard only.

Yes, with counter channels on the Counters page. Under New counter channel, let the bot create a voice channel nobody can join or use one of yours, then write the Channel name with up to 4 counters: {value} for a single counter or {1} to {4} for several, as in Members: {value}. Counters include:

• Members (people, bots or everyone, with an optional goal) and Members with a role
• In voice right now
• Channels and Roles
• Clock and Countdown
• Activity count, Activity change and Top member or channel over 1, 7 or 30 days
• Members by status, which needs the Presence Intent

The bot renames the channel only when the value changes, at most once every 6 minutes. Names stop at 100 characters. It needs Manage Channels on that channel. The Counters page shows how many counter channels your server can have.

Yes to both:

• Sharing: on the Analytics Sharing page, Who can open the dashboard has a read-only dashboard at yourbot.gg/a/ followed by your server ID. It shows server totals only (messages, voice hours, joins and leaves, member count and top channels), never individual members. Pick Private (the default, link off), Members only, Role restricted or Public, then click Save sharing.
• Stats cards: each member's card has its own public link. Reset share links on the Sharing page stops every link handed out so far.
• Exports: the menu on a chart has Download CSV for what you are looking at. Export data on the Sharing page also has Messages CSV and Voice CSV for the last 7 to 365 days. For a live feed, create a key under Developers on the Sharing page and use the Analytics API.

Yes. Both start off. In Analytics Settings, under Status and activity tracking, switch off Status tracking (online, idle, busy and offline counts every five minutes) and Activity tracking (what members play, stream and listen to), then click Save. Nothing new is recorded after that. What was already recorded is deleted by the nightly cleanup once it is older than your Keep data for window.

To keep activity tracking but narrow it, open Which activities to record and set Activity filter to Only the names listed or Everything except the names listed. Custom statuses are never recorded. Members who hid their stats card are skipped.

From Discord, run /beacon create. A form asks for the Event Name, a Description, the start time as YYYY-MM-DD HH:MM (read in Beacon's timezone, or add a zone such as 2026-03-10 20:00 PST), Max Participants (blank = unlimited) and Roles (comma-separated, blank = none), written like Tank:2, Healer:4, DPS:14, Flex. The event card posts in your announcement channel with one reminder at your default reminder time.

From the dashboard, click + New Event on Beacon Events. The five-step editor has a live preview and adds what the Discord form can't: classes and specs, several reminders, a sign-up deadline, repeats and an automatic voice channel. Create Event saves the event and posts the card. To change an event later, open it and click Edit, or use Quick Edit for the title, time and cap; Save Changes also updates the card in Discord. The dashboard editor needs the Manager role.

Yes. The Templates page at /p/beacon/templates has built-in templates such as WoW Mythic Raid (20), WoW Mythic+ (5), FFXIV Full Party (8), PvP Night, Social Event and Meeting, plus any your server saves. Click Use on one to open the event editor with its title, description, participant cap, category and embed look filled in, then set the date and the roles. In the editor's Roles step, WoW Raid, FFXIV Party and Generic each load a role set in one click, or type roles into Quick Add. To make your own template, click + Create Template and pick a starting point such as Raid Night, Dungeon Run, Movie Night or Game Night, or click Save as Template on an event. To repeat an event with its roles and caps exactly as they were, click Clone on its page instead.

Yes. When an event has roles, Sign Up asks each member to pick one, and the card lists members under their role. In /beacon create, type roles in Roles (comma-separated, blank = none) as Label:cap, for example Tank:2, Healer:4, DPS:14, Flex; a role without a number has no cap. In the dashboard editor's Roles step, add roles with + Add Option and put each role's cap in its Max box. Click + Child to nest classes or specs under a role: members then pick the role first and the class or spec in a second menu, and the spec shows next to their name on the card. Max Participants caps the whole event on top of the role caps. When a role or the event is full, new sign-ups go to the waitlist.

New sign-ups go on the waitlist. The member gets a private reply with their place in line, and the card shows the waitlist. Only Attending sign-ups take a place, so members marked Tentative, Late, Bench or Absent never fill a slot. When someone clicks Leave, the member who has waited longest for that role moves in automatically. If nobody is waiting for that role, the longest-waiting member overall moves in. The promoted member gets a DM and a notice is posted in the event's channel. Removing a sign-up on the event's dashboard page also moves the next person in, without the DM or the notice. Raising a cap does not pull anyone off the waitlist.

Yes. The Options button on the event card opens a private menu with Tentative, Late, Bench and Absent. Members can pick one whether or not they have signed up, and it keeps any role they already chose. Tentative and Late appear next to the member's name, while Bench and Absent are listed under Other on the card. The status counts later too. Attending, Tentative and Late members get reminders. Late earns half attendance credit, while Tentative, Bench and Absent don't affect reputation. None of these statuses takes a capped slot. Clicking Sign Up again sets the member back to attending.

Yes, in two ways.

• Signup Deadline: in the dashboard editor's Finish step, under Advanced, enter how many minutes before the start sign-ups close. After that, Sign Up tells members sign-ups have closed and to contact the organizer, while Leave still works. Reminders, the voice channel and attendance carry on as normal.
• /beacon close with the event number stops sign-ups at once and removes the card's buttons. The organizer or anyone with Manage Server can use it. A closed event gets no reminders or voice channel and is never marked complete, so there is no recap and no attendance credit. Reopen it with /beacon open, then click Repost to Discord on its dashboard page if the card has no buttons.

Use the deadline if you still want reminders and attendance.

Yes. Beacon reads times in its own Timezone setting, in the Settings card on Beacon Events. It follows your server timezone from the Bot page unless you pick another zone in that setting, and the choice applies to every Beacon time. For a single event, add a zone after the time in /beacon create or /beacon clone: an abbreviation (2026-03-10 20:00 PST), a zone name (2026-03-10 20:00 America/New_York) or an offset (2026-03-10 20:00 -0700). The dashboard editor has no per-event zone. Its Date & Time is read in Beacon's timezone, which the hint under the field names. Members always see the time in their own zone on the card.

Yes. Open the event on Beacon Events and click Recover Event, which shows on cancelled and completed events. If the date has already passed, the editor opens so you can set a new one. In Discord, /beacon open with the event number reopens a cancelled or closed event without changing its date, for the organizer or anyone with Manage Server, so use the dashboard when the date has passed. Sign-ups from before the cancellation are kept. If the card in Discord still shows the cancellation or has no sign-up buttons, click Repost to Discord on the event's page to post a new card with sign-up buttons.

Yes. In the dashboard event editor's Finish step, click + Add Reminder for each reminder, set how many minutes before the start it goes out and choose Channel or DM. Add one of each to get both. A channel reminder posts in the event's channel and mentions everyone signed up as Attending, Tentative or Late. A DM reminder messages each of those members and skips anyone whose DMs are closed. Waitlisted, Bench and Absent members get neither. If nobody has signed up, nothing is sent. Events made with /beacon create start with one channel reminder at your Reminder (minutes before event) setting, so edit the event on the dashboard to add a DM one.

Yes. Tick Auto-create voice channel in the event editor's Finish step. Before the start, the bot creates a voice channel named after the event and posts a link to it in the event's channel. Under Auto Voice Channel in the Beacon settings you set how early (Pre-create (minutes before event), 1 to 120, 15 by default), an optional VC Category ID and Restrict to signed-up members only. With that last option everyone can see the channel, but only members signed up when it was created can connect. The channel is deleted once the event has started and the channel is empty, and 30 minutes after the start time at the latest. With auto voice on, Attending or Late members who haven't joined the channel by the start are logged as no-shows. The bot needs Manage Channels and Connect.

Automatically. Shortly after an event's start time, Beacon marks it completed, posts a recap in the announcement channel and credits each sign-up: Attending counts as attended and Late as half, while Tentative, Bench, Absent and waitlisted sign-ups are left out. If the event had auto voice on, Attending or Late members who never joined its voice channel are logged as no-shows instead. These results build each member's reputation, a score out of 100 with streaks and badges. /beacon rep (optionally with a member) shows their score, events, attended, no-shows, current and best streak and badges in a private reply. The Reputation page at /p/beacon/reputation ranks members by score, listed by Discord user ID. Both show totals, not an event-by-event history. For one event's sign-ups, use Export CSV on its page.

Yes, as a separate button poll; polls aren't attached to an event card. In Discord, /poll create posts a poll in the current channel with a question and 2 to 25 comma-separated options. It can allow several votes per member or hide the counts until the poll closes. On the Polls page at /p/beacon/polls, managers can build a poll from ready-made option sets, set an optional Auto-close at time and Post it to a channel you pick. Close a poll with /poll close or Close (in Discord, the creator or anyone with Manage Server), show the tally with /poll results and download every vote with CSV. An anonymous poll's CSV leaves out who voted.

Yes, for sign-ups. On an event's dashboard page, Export CSV downloads one row per sign-up with the member's user ID, role, spec, status, whether they are waitlisted, their sign-up order and when they signed up. In Discord, /beacon export with the event number sends you a similar file privately. For polls, CSV on the Polls page downloads every vote. The attended or no-show result Beacon records after an event isn't in these files; each member's totals are on the Reputation page and in /beacon rep.

On the dashboard, open Giveaways and click + New Giveaway. Pick the channel, add your prize tiers and set the timing under Schedule:

• Duration starts it right away and runs for the time you type, such as 30m, 2h or 3d (at least 30 seconds).
• Pick dates takes an Ends at and an optional Starts at. A start time in the future saves the giveaway as scheduled, and the bot posts it at that time. The form shows which timezone the times are in.

Then click Publish now, or Save draft to finish it later. Drafts and scheduled giveaways can still be edited, or published early with Publish now on their page. In Discord, /giveaway create with a title, a duration and a prize (or tiers) posts a quick reaction giveaway in the channel where you run it. By default a server can have 25 running or scheduled giveaways and create 50 a day.

A drop has no draw: the first members to click Enter on the giveaway message win on the spot. Choose Drop (first to click wins) as the Entry method on the New Giveaway form, or set drop to true in /giveaway create. There is one slot per winner across your prize tiers, filled in rank order, so the first clickers get the rank 1 prizes, and each member can hold one slot. Entry requirements, the winner cooldown, the blocked list and required tasks still apply to every click. The drop ends as soon as the last slot is taken, or at its end time with whoever claimed. Members who click after the slots are full are still entered, so a reroll can replace a winner who doesn't claim their prize.

Yes, three ways:

• Save as template on a giveaway's dashboard page stores its setup under a name you choose. Start from it with Start from template: on the New Giveaway form, or Use on the Templates page. A template keeps the prizes, entry method, requirements, messages and options, but not the channel, the dates or the entry tasks.
• Duplicate on a giveaway's page makes a draft copy, entry tasks included, and opens it so you can set new dates.
• Recurring (optional): on the New Giveaway form (Daily, Weekly or Monthly) starts the next giveaway with the same settings as soon as one completes. Each new one runs until one day, 7 days or 30 days after the previous one ended. A giveaway in the chain that ends cancelled, including one cancelled for too few entries, stops the chain.

Yes. On the New Giveaway form each tier has a Rank, a number of Winners and a Prize; click + Add tier to add another. Ranks run from 1 to 20 and each tier can have 1 to 100 winners. Rank 1 is drawn first and a member can win only one tier, so nobody takes two prizes from the same giveaway. In Discord, /giveaway create takes winners for a single prize, or tiers written as rank:count:prize separated by |, for example 1:1:Grand prize|2:3:Runner-up prize. Unless the giveaway is a drop, every winner slot has to be filled: if there are fewer eligible entries than winners in total, the giveaway is cancelled instead of drawn.

Open Requirements & weighting on the New Giveaway form:

• Min account age (days): how old the member's Discord account must be.
• Min member days: how long they have been in your server.
• Required roles (they need every one) and Excluded roles (any one keeps them out).
• Min messages over Counted over (days), 30 days by default and up to 365.

Requirements are checked when someone enters, and a member who is turned away is told why. The message count comes from the Analytics service and only counts messages Analytics has recorded. If Analytics is switched off on your server, the Min messages requirement is skipped and everyone passes it, so switch Analytics on first. Members with one of the Bypass roles on the Setup page skip all of these requirements.

Yes, both are set per giveaway on the New Giveaway form.

• Entry tasks: add link or custom tasks, each either required or worth bonus entries. Members mark them done on the giveaway's public page, signed in with Discord and in your server, so keep Public spectator page enabled on for a giveaway with tasks. Tasks run on the honour system, so marking a task is what counts. A required task blocks Enter until it is marked, and a bonus counts whether it is marked before or after entering.
• Referrals (under Messages): set Referral bonus (entries per referred member), Invite to win (min referrals) or both. The giveaway message then gets a My invite link button (/giveaway invite works too) that makes a personal invite. Each new member who joins through it counts once if their account is at least Referred account age (days) old, 7 by default. Invite to win keeps entrants below the minimum out of the draw. The bot needs Create Invite in the giveaway channel and Manage Server to read invite counts.

Use the Prize vault on the giveaway's dashboard page. For each tier, paste keys, codes or links under Add items, one per line and click + Add to vault; write Label | value to give an item a name. Items are stored encrypted and the page only ever shows their labels and whether each one was delivered. Each winner receives the next unused item of their tier inside the winner DM, or in a DM right after they press Confirm prize when Require winner confirmation is on. When a tier runs out, the winner is told the host will deliver the prize. Items arrive only by DM, so check the draw history: a winner marked DMs closed needs you to follow up. You can remove an item until it has been delivered.

Yes. Tick Require winner confirmation on the New Giveaway form and set the Window in hours (1 to 168, 24 by default). Each winner gets a DM with a Confirm prize button. If their DMs are closed, the button is posted in the giveaway channel with a mention instead, and only that winner can press it. When a winner confirms, the host gets a DM, the winner receives their prize vault item if the tier has one and the Auto-grant role to winners role is given then rather than at the draw. A winner who doesn't confirm in time is marked expired under Winner confirmations on the giveaway's page, where Reroll slot picks a replacement for that slot, even after the normal 30-minute reroll window.

The draw runs by itself at the end time, or when a host ends it early. Winners are picked at random with the operating system's secure random source, so the result can't be predicted or replayed. Each entry counts as one ticket, plus one more per bonus entry from boosting, roles, tasks or referrals, so bonuses raise a member's odds without guaranteeing a win. Tiers are drawn from rank 1 down and each member can win only once per giveaway. Disqualified entries, members inside the dedup window or winner cooldown and, for invite-to-win giveaways, entrants below the referral minimum are left out, and every pick is checked against the server's current members. If there are fewer eligible entries than winner slots, the giveaway is cancelled rather than partly drawn. Participants CSV on the giveaway's page exports every entry and its weight.

Yes. Each giveaway with Public spectator page enabled (on by default) has a public page at /g/<id> that anyone can open without signing in. It shows the prizes, a countdown, the live entry count and the most recent entrants, then plays the draw as an animation and lists the winners; Replay animation runs it again. The link is behind Watch live on the giveaway message, the Spectator page button on its dashboard page and in the replies to /giveaway info and /giveaway list. By default the page stays up for 3 days after the giveaway ends or is cancelled. Untick the option when you create a giveaway to keep it off the public web.

Yes.

• Recent winners: each giveaway has a Dedup window (days), and the Setup page has a server-wide Winner cooldown (days). The longer of the two applies, up to 365 days, so one giveaway can't switch the server cooldown off. Anyone who won a giveaway in your server inside that window can't enter and is skipped at the draw. New giveaways made on the dashboard start with a 7-day dedup window by default.
• Blocked members and roles: add them under Blocked from giveaways on the Setup page, or with /giveaway blacklist add, remove and list (these need Manage Server). Blocked members can't enter any giveaway in the server, and Bypass roles don't override the block.

At the draw, every picked winner is checked against the server's current members. Anyone who has left is disqualified, with a note that they left before the draw, and another entrant is drawn in their place. If Discord can't be reached for the check, the pick stands. Once winners are announced, nothing changes on its own if a winner leaves later. Within 30 minutes of the draw a host can pick a replacement with /giveaway reroll or Reroll on the giveaway's page, as long as Allow rerolls is on. With Require winner confirmation, the slot of a winner who doesn't confirm in time gets a Reroll slot button on the giveaway's page, which works after those 30 minutes.

In Discord, /giveaway create, end, reroll and cancel work for members with Manage Server or Administrator, or with the host role that Run Setup detects from role names such as giveaway host, moderator or staff. A host can act on any giveaway in the server, not only their own. Everyone can use /giveaway list and /giveaway info, and the /giveaway blacklist commands need Manage Server. On the dashboard, people with the Owner or Manager role can create, edit, end, cancel and reroll giveaways. A giveaway can be cancelled while it is a draft, scheduled or running, but not once the draw has started. These actions are recorded in the Activity log on the giveaway's page.

Only the title is required, and there is no setting that makes another field mandatory. Depending on whether they use /group create or the web form, posters can add a game, activity, description, party size (2 to 40), expiry, start time, region, platform, language, experience level, a voice requirement, a join mode, visibility and role slots. To control who can post and what, set Min Account Age (days) and a Keyword Blocklist in Group Finder Settings. To check players before they join, make listings approval-only: players who click Apply can add a note for the leader, who approves or denies them.

Yes. A listing can have named role slots, each with its own size, such as Tank 1, Healer 1 and DPS 3. Members then pick a role from Choose a role to join… instead of clicking Join. A full role drops out of that menu and shows a lock on the card, and once every role is full the card shows All Roles Full. To add slots:

• /group quick with mythic+ (or m+), dungeon or raid creates Tank, Healer and DPS slots.
• /group create with a template that has slots, such as the built-in Dungeon Finder or Raid Finder.
• Role Slots on the web form at /p/group_finder/create, with + Add Slot or the 5-man Dungeon, 20-man Raid and 3v3 Arena presets.

The party size still caps the whole group, so keep it equal to the slot total. Approval-only listings show Apply instead, and applicants don't pick a role.

Yes. Make the listing approval-only by choosing Approval: leader reviews applications for join_mode in /group create, or turn on Require Listing Approval in Group Finder Settings to make every listing on your server approval-only. The card then shows Apply instead of Join. Players click it and can add a note, or run /group apply, and the leader gets a DM for each application. The leader answers with /group approve or /group deny, and the player gets a DM either way. Managers can also Approve or Deny applicants on the listing's page under Listings in the dashboard. An application can't be approved while the group is full.

When the last seat fills, the listing turns full and a Waitlist button appears. Anyone who clicks Join after that goes on the waitlist too. When a member leaves a full group, the first person on the waitlist moves in automatically and gets a DM. If the listing requires voice, the bot also opens a voice channel for the group.

To follow a listing without joining, click Watch on it or run /group watch. You get a DM when someone joins, leaves or joins the waitlist, when a seat opens in a full group, when the group is closed or completed and shortly before a scheduled start. Click Watch again to stop, and /group watching lists what you follow.

Yes. In Discord, /group browse lists open groups eight to a page, with filters for game, activity, region and platform and sorting by newest, expiring soon or closest to full. Groups shared from partner servers in your networks are included. With Auto-create forum threads on in Group Finder Settings, every listing also gets its own thread in your forum channel, tagged when a forum tag matches its game, activity or difficulty. On the web, your server's Public LFG Page (the link under Share & Embed in Settings) shows anyone the open Public groups from your server and partner servers in your networks, and Public listings from every server are on the LFG board. Members can also have new groups sent to them with /group-alerts add.

Yes. Set start in /group create, or Starts In (optional) on the web form, as a time from now such as 30m, 2h, 1h30m or 1d, up to 14 days ahead. The card shows the start time in each member's own time zone with an Add to calendar link. About 15 minutes before the start, every member of the group and everyone watching it gets a DM reminder. Not sure when to run? The leader can post /group poll with two to five start times; members vote with buttons, and closing the poll sets the start and DMs the group. The listing still expires on its own clock, counted from when it was posted and capped by Max Expiry (h) (48 hours by default), so give it an expiry that reaches past the start.

Yes. Create the group with voice set to True in /group create, and the card shows Voice Required. When the last seat fills, the bot creates a voice channel named after the group in the listing channel's category, limited to the party size, and links it on the card. The bot deletes the channel when the leader clicks Done, runs /group close or leaves the group, when a moderator uses /group-admin close-listing and when the listing expires. The bot needs Manage Channels. The web form and /group quick don't have a voice option.

Yes. The leader clicks Ready Check on the listing card. The bot posts a ready check that mentions everyone in the group, with Ready and Not Ready buttons and a live count of how many are ready. Only the leader can start one, and only group members can answer. Network and Public listings also have a leader-only ready check in their web event chat.

Yes, both.

• Repeat: set repeat (every day, week, two weeks or month) and optionally repeat_count (total runs, 0 until you stop it, up to 52) in /group create, or Repeats (optional, needs a start time) and Total runs (0 = until stopped) on the web form. A repeating group needs a start time. For a group that's already posted, the leader or anyone with Manage Server runs /group repeat, where Off: stop repeating ends it. Each new run is posted after the previous one ends (closed, marked done or expired) and no earlier than three days before it starts, with the same details and roles. Members don't carry over, and people watching get a DM when it posts.
• Relist: /group relist picks one of your closed or expired listings and posts it again as a new listing, with an optional number of hours until it expires.

Every listing expires after a set number of hours, never more than Max Expiry (h) (48 by default). In /group create that is the hours you give, else the template's default, else Default Expiry (h) (4 by default); the web form has its own Expires In (hours) field. When it expires, the card shows it as expired and loses its buttons, its forum thread is locked and archived, any auto-created voice channel is deleted and the web event chat turns read-only before being deleted 24 hours later. If the leader leaves, the listing closes straight away with the same cleanup. Leaders can end a listing early with /group close or the Done button, and managers can force-close any listing with /group-admin close-listing. An expired or closed listing can be posted again with /group relist.

Both.

• Ratings: when the leader clicks Done, each member gets a DM asking how the run went, with a thumbs up (Good) or thumbs down (Not great). Each member rates once per group. After a leader has 3 ratings, their listings show the share of thumbs up and how many ratings they have. Who voted is never shown.
• Reports: /group report with the listing and a reason sends it to your moderators. It is posted in the Log Channel if one is set, and managers review it on the Reports page at /p/group_finder/reports or with /group-admin reports. They can Dismiss it, Remove Listing or choose User Suspended, which stops the leader posting listings for 7 days.

Leaders can also record a player who didn't turn up with /group noshow.

Yes. /group-admin suspend with a member, a number of hours (1 to 720, 24 by default) and a reason stops them posting listings in your server until it runs out: /group create, /group quick, /group relist and the web form all refuse them. It doesn't stop them joining other people's groups. Lift it early with /group-admin unsuspend, and see active ones with /group-admin suspensions or on the Posting Suspensions page at /p/group_finder/suspensions, which has an Unsuspend button. Resolving a report as User Suspended suspends the listing's leader for 7 days. To take someone out of one group, a manager clicks Remove next to them on the listing's dashboard page, and they can't rejoin that group. The /group-admin commands need Manage Server by default.

Yes, through networks. A manager creates one on the Networks page at /p/group_finder/networks with Create Network (or /group-admin network create) and shares its Network ID with the partner servers' admins. They paste it under Join an Existing Network and click Join Network, or run /group-admin network join. Each server then sets two switches: Outbound sends its Network and Public listings to partners, and Inbound brings partners' listings into its listing channel or forum and into /group browse. A listing only travels when it is posted as Network or Public, the posting server has Outbound on and the receiving server has Inbound on with Group Finder switched on. Players on partner servers join from their own copy, and every copy stays in sync. When you post a Network listing, you can limit it to some of your networks.

Each listing has its own visibility, so one can stay in your server while another goes public:

• Local (the default): posted only in your server. /group quick always posts Local.
• Network: also posted in partner servers in your networks, when your server has Outbound on and theirs has Inbound on.
• Public: Network plus the public LFG board. It needs Allow Cross-Post in Group Finder Settings; without it the listing posts as Network.

Partner servers see the same card you do: title, description, game and other details, the leader's display name (with their rating once they have 3), display names of up to 15 members (members from another server are marked) and the waitlist and pending counts. The public board shows the title, game details, how full the group is, your server's name and the leader's name. Network and Public listings also get a web event chat where members see each other's names and avatars. Your server's Public LFG Page link (under Share & Embed in Settings) shows open Public listings from your server and partner servers in your networks, without member names. Local and Network listings never appear there.

Yes. /group quick builds a listing from a preset in one step:

• mythic+ (or m+) and dungeon: 5 players with Tank, Healer and DPS slots.
• raid: 20 players with Tank, Healer and DPS slots.
• arena: 3 players, or 2 if you put 2v2 in details.
• pvp: 5 players.

/group create also offers built-in templates (Generic LFG, Dungeon Finder, Raid Finder, PvP Squad and Event Signup), and the setup wizard adds game templates such as WoW Mythic+ (5-man), WoW Raid (20-man) and FFXIV Full Party (8) based on the games it finds in your channel and role names (WoW and FFXIV if it finds none). The web form has 5-man Dungeon, 20-man Raid and 3v3 Arena slot presets, and managers can build their own templates with role slots on Templates.

Yes. On the Join-to-Create page, go to the Lobbies card and fill in Add a lobby: pick an Existing voice channel or type Or new channel name, then set a Label, a category under Rooms go in, a Name template and a User limit. Tick Start locked or Start hidden if you want, then click Add lobby. Once added, each lobby also has its own Bitrate and Control panel setting. Blank fields use the server settings.

For example, run a Duo lobby with a limit of 2 next to a Squad lobby with a limit of 4. Tick Recreate if deleted to have the bot make a lobby again if its channel is deleted. Remove stops a channel being a lobby and keeps the channel.

New rooms are named from the Channel Name Template under Configuration on the Join-to-Create page, 🎧 {display_name} by default. Each lobby can have its own Name template. Placeholders:

• {display_name}: the member's name as shown in your server
• {username}: their Discord username
• {count}: how many rooms are open from that lobby, counting the new one
• {activity}: the game or stream they are in when the bot can see it, otherwise their display name

A member who saved a name with /voice prefs gets that name instead. The owner can rename the room with /voice rename or the Rename button on their control panel, up to 90 characters. Discord allows two renames per room every ten minutes.

They are the room owner's access controls, as /voice commands and on the control panel:

• Lock (/voice lock): nobody new can join; people already inside stay. /voice unlock opens it again.
• Hide (/voice hide): only permitted members and roles can see the room. /voice show undoes it.
• Permit (/voice permit): a member or role can see and join even while the room is locked or hidden.
• Reject (/voice reject): keeps a member or role out and disconnects them if they are inside. Owners can't reject server staff or anyone ranked at or above them.

Undo permit and Undo reject (/voice unpermit, /voice unreject) reverse them. The buttons that pick a member or role work on the panel /voice info opens in the server; on the copy sent by DM they point you to the command. Permits and rejects are remembered for the owner's next rooms, up to 25. Server settings can also make new rooms start locked or hidden.

Yes. /voice kick disconnects a member from the room. The Kick button does the same on the panel /voice info opens in the server; on the copy of the panel sent by DM it points you to the command. They can come back unless you lock or hide the room or reject them, so use Reject (/voice reject) to keep them out. The bot won't let an owner kick or reject server staff (members with Manage Channels or Administrator) or anyone whose highest role is at or above the owner's. Members with Manage Channels or Administrator can.

With Creator owns their channel on (the default), the owner also gets Discord's own Move Members, Mute Members and Deafen Members on their room, as long as the bot has them, so Discord's right-click menu works there too.

The owner can hand the room over with /voice transfer, or with the Transfer button on the panel /voice info opens in the server. The new owner has to be in the room. They get the owner permissions and a fresh control panel; the old owner's are removed. A manager can also transfer any room: on the Join-to-Create page, click Edit on the room under Live Channels and use Transfer Ownership with the member's Discord user ID.

If the owner leaves while others stay, Pass the room on when the owner leaves (on by default) makes the first person still inside the owner, and the room's chat says who. With it off, anyone inside can take over with /voice claim or the Claim button once the owner is gone. The room is only deleted when everyone has left.

With Delete when empty on (the default), a room is deleted as soon as the last person leaves; the bot checks again a moment later in case Discord still showed someone inside. If a member leaves the lobby before the bot moves them in, their new room is removed the same way. Rooms left empty while the bot was offline are cleaned up when it comes back. Lobbies are never deleted.

To keep one room, a manager opens the Join-to-Create page, clicks Edit on the room under Live Channels, then Untrack (keep channel in Discord). It becomes an ordinary voice channel: the service never deletes it, and /voice commands and the control panel no longer work in it. To keep every empty room, untick Delete when empty under Configuration and click Save Settings.

Choose under Channel access in Configuration on the Join-to-Create page, then click Save Settings:

• Inherit from category (the default): each new room copies the permissions of the category it is created in, so whoever can see and join that category can use the rooms.
• Custom role allowlist: @everyone is denied, and only the roles you pick under Allowed roles can see and join new rooms.

Either way the owner gets their owner permissions (with Creator owns their channel on) and the bot keeps its own access. Owners can still let others in with /voice permit. The choice applies to rooms created after you save; rooms already open keep their permissions.

Rooms that are already open keep working and are still deleted when they empty, but nobody can start a new room from that lobby.

• Your main lobby (the Lobby Channel ID in Configuration): click Re-create Lobby + Category on the Join-to-Create page. It makes a new lobby named from Lobby Channel Name, plus a new category if that is gone too. Or enter another voice channel's ID as the Lobby Channel ID and click Save Settings.
• An extra lobby: with Recreate if deleted ticked on its card, the bot makes a new one automatically, named after its Label when it has one. Otherwise click Remove on its card.

On the Messages page, on the Welcome tab, pick the Welcome channel, write the Message and click Save changes. If nothing is saved yet, your server's system channel is preselected. The message can use {user} (display name), {user.mention} (a mention of the member), {user.name} (username), {user.id} (user ID), {server} (server name), {member_count} (member count) and {created_at} (the date their account was made). The same variables work in goodbye and DM messages, and All tags and conditions under each message lists the rest. With Send as set to embed, the greeting is an embed in the Colour you pick under How it looks, with the member's avatar and their member number. As plain text, it's just the message. A welcome never pings @everyone or @here. In Discord, /welcome set channel and /welcome set message do the same (Manage Server needed).

Yes. On the Messages page, on the Welcome tab, open Rotating messages and click Add a message once per greeting, up to 25. Each greeting can use the usual variables and carry its own image or GIF link, which must start with https:// or the save is refused. Order picks one per join, either Random or In order, one after another. While the list has entries, the single Message above is not used, and a greeting's own image replaces the welcome card for that join. Goodbyes rotate the same way under Rotating messages on the Goodbye tab, and Order covers both lists. Click Save changes to keep your changes.

Yes. In the Card Studio, turn on Send a welcome card. Each new member then gets an image card with their avatar and name, with no watermark. Start from a template, pick a background (a picture from the library, a colour or gradient, your own upload or an https:// link) and change the text, the avatar and the shapes on the card; the preview draws the real card as you edit. The card is sent whether the greeting is an embed or plain text, except when the rotating message picked for that join has its own image, which takes the card's place. The bot needs Attach Files in the welcome channel.

Yes. On the Messages page, on the DM tab, turn on Send a welcome DM, write the Message and click Save changes. The DM can use the same variables as the welcome message, such as {user} and {server}, and is sent as plain text unless you set Send as to embed. It goes out when the member joins, even if they still have to pass the verification gate. Members who don't accept DMs from server members won't receive it. The DM also works on its own, so you can welcome people by DM with no welcome channel set. /welcome set dm turns it on or off from Discord (Manage Server needed).

Yes, though goodbyes are off by default. On the Messages page, on the Goodbye tab, turn on Send a goodbye, pick a Goodbye channel (it stays Same as the welcome channel unless you choose another), write the Message and click Save changes. It can use the same variables as the welcome, such as {user} and {member_count}, and the bot adds a line saying how many days they were a member unless the text already uses {user.member_for}. For variety, add several under Rotating messages, each with an optional image or GIF. Bots leaving are ignored. If a Log channel is set on the Logs & cleanup page, it also gets a line for each leave. /welcome set goodbye turns goodbyes on or off from Discord (Manage Server needed).

Yes. On the Roles page, under Roles on join, turn on Give roles on join, tick each role under Roles to give (as many as you like) and click Save changes. Options:

• Wait before giving them, up to 600 seconds, holds the roles back as an anti-raid measure. A member who leaves before it ends gets nothing.
• With the verification gate on, the roles wait until the member verifies.
• Restore roles when a member rejoins, under Sticky roles, gives back the roles a member had when they left, if they rejoin within 180 days.

Roles with dangerous permissions are never handed out: they're greyed out on the page, refused when you save and skipped when sticky roles are given back. Discord only lets the bot give roles below its own highest role. /welcome set autorole adds a role from Discord and turns roles on join on (Manage Server needed).

Until they verify, they keep the Unverified role (optional) if you set one, and they get no auto-roles or buddy. Nothing else happens unless you set a deadline with Deadline after joining, under If they don't verify on the Verification page, up to 10,080 minutes (7 days) after they join. Then:

• Reminder DM can send one reminder DM first, that many minutes before the deadline.
• At the deadline the bot does what you picked: kick (they can rejoin), ban, hold (gives them the Hold role and keeps them) or nothing. Before a kick, ban or hold it DMs the member to say which it is. Hold does nothing until you pick a Hold role.
• The Log channel gets a line for each member kicked, banned or put on hold.

Members who verify or leave in time are left alone, and nobody is acted on if you turn the gate or the deadline off. Kick needs Kick Members, ban needs Ban Members and hold needs Manage Roles.

Yes. Open Role menus in the Welcome service and click New menu. Then choose:

• Layout: Buttons, Dropdown or Emoji reactions
• Choice: Any combination or One at a time
• where it lives: a Channel to post into, or for a reaction menu the Message link of a message already in your server
• the message Style: Embed: title, colour and pictures or Plain text with markdown

Under Roles, click Add a role for each one, up to 25 (20 for a reaction menu), with an emoji, a label and an optional description, and click Save and publish. Members click a button or pick from the dropdown and get a private reply saying what changed; on a reaction menu, adding a reaction gives the role and removing it takes the role back. Roles with dangerous permissions are left out of the picker, and roles above the bot's highest role are skipped. Turn off Menu is on to pause a menu. Publishing a button or dropdown menu again replaces its old message, and a reaction menu is updated in place.

Yes. Open Quests in the Welcome service. Add up to 15 tasks under Add a task (emoji, Name, Description and How it gets done) or click Use the four defaults for a starter set, then click Turn quests on. When someone joins, the bot posts their checklist in the Quest channel (the welcome channel unless you pick one). Tasks tick off by themselves when the member sends a message, joins a voice channel, adds a reaction or posts in the welcome channel (Auto: Post Introduction). Manual: Admin Marks Complete tasks are ticked with /quests admin-complete (Manage Server needed). Under Rewards you can grant a role, send a message or award XP for one task or for finishing them all. Members check their progress with /quests list.

Yes, with the Buddy system on the Engagement page. Give your welcomers a role, pick it as the Buddy role, turn on Pair new members with a buddy and click Save changes. Each newcomer is paired with the pool member who has had the fewest newcomers so far, and the Introduction is posted in the welcome channel, where {user.mention} is the newcomer and {buddy.mention} is the buddy. Also DM the buddy sends the buddy, not the newcomer, a private note naming the newcomer. With the verification gate on, pairing waits until the member verifies. Bots are never picked, and nothing is posted if the pool role has no members or no welcome channel is set.

Yes. The First-message celebration on the Engagement page is on by default. When a new member posts for the first time, React with 🎉 (on by default) reacts to that message, Announce it (off by default) posts a shout-out naming them in the welcome channel and Give a role for it can give them a role. It only counts members who joined in the last 30 days, so switching it on doesn't celebrate your regulars, and each member is celebrated once. Click Save changes after changing it.

Yes. Under Member milestones on the Engagement page, turn on Celebrate member milestones (off by default), pick where to Post in (the welcome channel unless you choose another), list your numbers under Member counts separated by commas and click Save changes. The default list is 100, 250, 500, 1,000, 5,000 and 10,000. When a join brings your member count to exactly one of those numbers, the bot posts a celebration thanking everyone for being part of the server, without pinging anyone. Each milestone is announced once, even if your count drops and climbs back, and a number below one already announced is skipped. The message text is fixed.

Yes. Under Extras on the Welcome tab of the Messages page, tick up to five Start-here channels and click Save changes. They appear as clickable channel links under a Start here heading in the welcome message. They only show while the greeting is sent as an embed (Send as on the Messages page), because they are added to the embed, so a plain-text welcome doesn't include them. /welcome test shows them too.

Three ways, from quickest to fullest:

• The previews on the Messages page update as you edit, showing the welcome message, the goodbye and the DM as the bot renders them, with your saved welcome card.
• /welcome test in Discord (Manage Server needed) sends you a private preview of the welcome message and card built from your own account, using your embed, highlights and start-here settings. It can run once every 20 seconds per server, and with rotating messages it picks from the list each time.
• For the whole flow, including the DM, auto-roles and verification, join the server with a second Discord account.

On Scheduled Announcements, click + New Announcement, or click a day on the calendar to start with that date at 09:00. Pick the Channel, write the Message, leave Recurrence on Once (specific date/time) and set Send at (in the timezone above). Check Timezone first: it starts as your server timezone and accepts any IANA name, such as America/New_York. Click Schedule. The bot checks for due posts every 30 seconds, so it goes out within about half a minute of that time. To post right away from Discord instead, use /announce now.

Yes. The New Announcement form and the edit form show a Discord preview beside the fields, and it updates as you type. It renders Discord markdown, links, role mentions (with the role's name and color) and <t:...> timestamps, and it shows the channel name and when the post fires. Discord may render a little differently. The preview does not show anything from Embeds (advanced, optional), so to check an embed, schedule a test post to a private channel first.

Yes. The Message box takes up to 2,000 characters of Discord markdown, such as bold, italic, strikethrough, code, quotes and headings, plus links, mentions and custom emoji. For richer posts, open Embeds (advanced, optional) and paste raw Discord embed JSON: one embed or an array of up to 10. Invalid JSON is refused when you save. There is no image upload. To show an image, give an embed an image or thumbnail with a public link, for example {"image": {"url": "https://..."}}. The form needs message text even when you add embeds. /announce now in Discord sends plain text only.

Yes. Internal label (optional) at the top of the New Announcement form is for your team only. It names the announcement in the dashboard lists, on the calendar and in notifications about delivery problems, and it is never posted to Discord. It can be up to 200 characters. Without one, the dashboard shows the announcement by number (for example Announcement #12), the same number /announce list shows and /announce cancel takes.

Yes. Scheduled Announcements opens on a month calendar with weeks starting on Monday. Each day lists up to three posts with their time, then a count of the rest, and one-time and recurring posts have different colors. Hover a day to see each post's time and timezone, channel, repeat type and text, and click one to edit it. Click any day to start a new announcement on that date. The arrows change month and Today jumps back. Times show in each announcement's own timezone. Paused announcements are not on the calendar. They're listed below it, along with pending, completed, cancelled and failed ones.

Yes, from the lists under the calendar on Scheduled Announcements:

• Edit works on pending and paused announcements. Saving a repeating one works out its next time from now. For a one-time post, check Send at (in the timezone above) before you save. Completed and cancelled announcements can't be edited.
• Pause keeps an announcement without sending it. Resume restarts it: a repeating post carries on at its next scheduled time and skips the ones it missed, and a one-time post whose time passed while paused goes out right away.
• Fire now posts it within about 30 seconds. A one-time post is then done. A repeating post carries on at its next scheduled time, and the early send counts toward Max occurrences (optional).
• Cancel stops it for good, as does /announce cancel in Discord.

On the dashboard, people with the Owner or Manager role on your server can create, edit, pause, resume and cancel announcements and use Fire now. A Viewer can open the page and the calendar but can't save changes. You give these roles on the Access page.

In Discord, /announce now, /announce list and /announce cancel are for staff: the server owner and members with Administrator or Manage Server can use them. To let another role use one, open Services, click Commands on the Scheduled Announcements card, click EDIT on the command and add the role under Who can use it, or apply the Balanced preset with your moderator roles. Anyone else gets a private reply saying they need Manage Server or an allowed role.

Twitch, yes. On Social & Patches, click New Subscription, pick Twitch Streamer, enter the streamer's login name as it appears in their Twitch address, choose where to post and click Create Subscription. Twitch channels are checked every 120 seconds by default (60 at the fastest), and the alert pings the roles you picked. Under Stream options you can post only for certain games with Only alert for these games, give the streamer's Discord account a Live role while they are live and choose what happens to the alert when the stream ends. Kick alerts are not available: the Kick Streamer tile on the Add a Feed page can't be selected.

Yes. Pick Reddit Feed on the Add a Feed page and paste a full reddit.com feed address: a subreddit's address with /.rss on the end, a user's feed or a search feed, for example a search limited to one flair. Addresses must point at reddit.com. Reddit feeds are checked every 30 minutes by default. Post text is tidied for Discord, so Reddit's leftover links and its submitted-by footer are removed. Add Only post if it mentions or Never post if it mentions keywords if you only want some posts.

Yes, when the service's status page is an Atlassian Statuspage, like the Discord and Epic Games status pages. Pick Service Status on the Add a Feed page and paste the status page address. YourBot checks that it really is a Statuspage when you save and refuses other kinds; if a page is refused, try its address with www. in front. Each incident posts once for every update, from investigating through to resolved. Status pages are checked every 5 minutes by default. For Discord itself, Discord Status is ready-made in the game catalog.

The Game Patch Catalog (Browse catalog on the Add a Feed page, or Pick from game catalog on Setup) has 98 ready-made feeds in 12 groups: FPS, MOBA, ARPG, Survival, Sandbox, Strategy, Action, MMO, Battle Royale, AI, Drivers and Platform. It covers games such as Counter-Strike 2, League of Legends, Valorant, Path of Exile 2, Minecraft, FFXIV, Guild Wars 2, Fortnite and Helldivers 2, plus AI tools like Ollama and ComfyUI, GPU driver news and Discord's own status and change logs. Search or filter by group, click as many tiles as you want, pick one destination and click Create Subscriptions (the button shows how many). The Setup page also has starter packs (Popular Games, AI Services & Tools, Drivers & Hardware, MMOs, Platforms & Status and Battle Royale) that add a whole bundle with one click.

Yes, per feed, in the Message section of its edit page. Message text (optional) replaces the default text and accepts placeholders such as {title}, {url}, {body}, {display_name}, {source}, {author}, {published_at} and {role_mention}; Twitch feeds also have {game} and {viewers}. Keep {role_mention} in your text, or the feed's ping roles are not mentioned. With Send an embed on, set its Colour, Title prefix and Footer text and choose whether it shows the Feed name above the title, the Item text, the Feed icon and the Item image. With it off only your text is sent, so include {title} and {url}. The Discord preview next to the form updates as you type, and Test (posts for real) on the overview posts the newest item.

Yes. Pick one or more roles under Ping roles (optional) and leave Allow @everyone and @here unticked, which is the default. Each post then mentions only the roles you picked for that feed. Even if an item's title or text from the outside feed contains @everyone, a role mention or a user mention, nobody else is pinged. If you write your own Message text, keep {role_mention} in it so the roles are still mentioned.

You choose, per Twitch feed, under When the stream ends in Stream options:

• Keep the alert as it is (the default)
• Edit the alert: stream ended, duration, viewers and VOD link
• Delete the alert
• Post a short offline message

Nobody is pinged again. The VOD link shows once Twitch has published the recording. While the stream is live, the alert's title, game and viewer count are refreshed every Live refresh (seconds), 300 by default and at least 120. A Live role is taken off the streamer when the stream ends, and their next stream gets a new alert.

Each feed remembers the newest item it has seen and only posts what comes after it, and every posted item is recorded against the feed as a final check against repeats. When you add a feed, its first check only records what is already there, so old items are not dumped into your channel. A feed that falls behind posts only items newer than the last one it saw, and if it can't tell, it restarts from the newest item without posting a backlog. The same feed can't be added twice to one channel, and changing a feed's source key starts it fresh. Skip to current on the overview marks the newest item as seen, and History shows what a feed posted.

Up to 100 by default. Every feed counts toward the limit, whatever its source and whether it is switched on or off, so delete feeds you no longer need rather than disabling them. Adding from the catalog or a starter pack counts each new feed, and a feed that already posts to that channel doesn't count again. If an addition would go over the limit, it is refused with a message saying how many feeds the server already has.