> For the complete documentation index, see [llms.txt](https://d3fenders.gitbook.io/d3fenders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://d3fenders.gitbook.io/d3fenders/8.-d3fenders-alert-network-setup-and-troubleshooting.md). # 8. D3fenders Alert Network Setup & Troubleshooting ## D3fenders Security Alert Bot — Server‑Admin Setup Guide *** ### 1. Invite the bot * Join D3fenders server and open a ticket to apply to join the D3fenders Alert Network. Once accepted we will give you the invite link. * Open the link → choose your Discord server → Authorize. * Make sure the bot shows up in your member list (online).\
Permissions the bot requests * View Channel * Send Messages * Embed Links * Attach Files * Add Reactions * Use External Emoji * Manage Messages (to pin its button) * Mention Everyone (needed to ping your alert‑role) * Read Message History * Use Slash Commands *** ### 2. Create a notification role 1. Server Settings → Roles → Create Role 2. Name it something like @security alert. 3. Put it in the list where you want. 4. ⚙️ Permissions: none are strictly required; it’s just for pinging. (If you already have a security‑ping role, skip this step.) ### 3. Create two channels | Channel | Purpose | Suggested perms | | ----------------- | ----------------------------------------------------- | -------------------------------------------- | | #security‑reports | Where staff click the “Submit Security Alert” button. | Staff + mods: Send; Everyone: View or hidden | | #security‑alerts | Where embeds + pings are broadcast. | Everyone: View; only bot: Send | (Channel names are examples—use whatever fits your server.) *** ### 4. Copy the three Discord IDs Enable Developer Mode (User Settings → Advanced). | What to copy | How | | ---------------------------- | ----------------------------- | | #security‑reports channel ID | Right‑click channel → Copy ID | | #security‑alerts channel ID | Right‑click channel → Copy ID | | @security alert role ID | Right‑click role → Copy ID | Paste them somewhere—each is a long number like 123456789012345678. *** ### 5. Run the setup slash‑command In any channel where you have permission send the slash command: /setupalert You’ll see a modal—fill it like: | Field | Paste | | -------------------- | ----------------------- | | Report Channel ID | ID of #security‑reports | | Alert Channel ID | ID of #security‑alerts | | Notification Role ID | ID of @security alert | Submit → bot responds “✅ Setup complete!” and pins a 🛡️ Submit Security Alert button in #security‑reports. *** ### 6. Test it 1. Click 🛡️ Submit Security Alert. 2. Fill out “What Happened?” and “What Should Others Do?”. 3. Press Submit. Result in #security‑alerts: 🛑 Embed with incident details @security alert — @YourName submitted a new alert. Thank you for keeping the community safe! (The same alert simultaneously appears in every other guild that has configured the bot, creating a cross‑server security network.) *** ### 7. Admin commands you might need | Command | When to use | | ----------------- | ------------------------------------------------------------------------------------ | | /postbutton | Re‑post the Submit Alert button if it was deleted or the report channel was changed. | | /setupalert again | Re‑run setup if you move channels or change the ping role. | *** #### That’s it! Your server is now connected to the D3fenders Security Alert Network.\ Moderators can file incidents in seconds; every linked community sees them instantly. If something doesn’t work, ping a D3fenders staff member or open a support ticket. ## D3fenders Alert Network troubleshooting guide Use this guide when setting up the bot or encountering issues with submitting or broadcasting security alerts. **1. Verify Configuration with Debug Commands** **`!debugconfig`** * **Purpose:** Check what this guild’s saved IDs are. * **Usage:** ``` diffCopyEdit!debugconfig ``` * **What you’ll see:** ``` yamlCopyEditCurrent config for this guild: • Report channel ID: 123456789012345678 • Announcement channel ID: 234567890123456789 • Notification role ID: 345678901234567890 ``` * **If you see any `None`**, that server hasn’t been fully set up or lost its settings—run `/setupalert` once to restore. **`!dumpconfigs`** * **Purpose:** List every guild the bot knows about and their IDs. * **Usage:** ``` diffCopyEdit!dumpconfigs ``` * **What you’ll see:** ``` yamlCopyEditSaved guild configs: • Guild 111111111111111111: report=222222222222222222, announce=333333333333333333, role=444444444444444444 • Guild 555555555555555555: report=666666666666666666, announce=777777777777777777, role=888888888888888888 ``` * **If it returns “No guild configs found,”** you need to run `/setupalert` in each guild at least once. 2\. Bot Isn’t Responding to Setup or Commands Possible Causes: • Missing required permissions • Bot was added without full scope • Bot was quarantined by another security bot Fixes: • Ensure the bot was invited with this link: • Make sure the bot is not muted, quarantined, or banned by your internal security bots. • Confirm the bot shows up in the Member List of your server. 3\. “No Valid Admin Roles Found” During Setup Cause: • Admin role IDs or mentions were input incorrectly. • Discord role hierarchy is preventing recognition. Fixes: • Make sure you are pasting either: • A role mention (e.g., @Mod Team) • A numeric role ID (right-click the role > “Copy ID”) • Confirm the bot’s role is higher than the roles you’re assigning as admin. 4\. Alerts Aren’t Appearing in the Announcement Channel Cause: • The announcement channel does not have correct permissions. • The channel was entered incorrectly during setup. Fixes: • Double-check the channel input in setup — use: • Channel mentions (e.g., #security-alerts) • Or numeric channel ID • Verify the bot has permissions in that channel: • View Channel • Send Messages • Embed Links • Mention Roles • Add Reactions 5\. Submit Button Doesn’t Show Up in Report Channel Cause: • Bot lacks permission to post messages or embeds in the report channel. • Channel setup was incomplete. Fixes: • Verify that the report channel has the following permissions: • For the bot role: • View Channel • Send Messages • Use Slash Commands • Embed Links • If needed, run the /setup command again to fix the configuration. 6\. “This Interaction Failed” When Clicking the Button Cause: • Channel is missing Send Messages or Create Interaction permissions. • The modal submission is blocked due to validation error. Fixes: • Ensure the bot has all required permissions in the report channel. • Make sure all users clicking the button have permission to interact with modals (and have an eligible role, if applicable). • If the modal fields are too long (e.g., label > 45 characters), a new version may have fixed this — please update the bot. 7\. The Bot Is in the Server, But Nothing Works Checklist: • Bot is online and responding to /commands • Bot is not in quarantine • Bot has administrator or full required permissions • Channels were correctly referenced by ID or mention • Roles were properly mentioned or added by ID • /setup was successfully completed (and not interrupted) 8\. Final Tip: Always Confirm Permissions For all involved channels and roles, the bot should have: • View Channels • Send Messages • Embed Links • Add Reactions • Mention @roles • Use Slash Commands • Manage Messages (optional but recommended) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://d3fenders.gitbook.io/d3fenders/8.-d3fenders-alert-network-setup-and-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.