--- title: "Discord Community" description: "Join the TurboPentest Discord server to connect with fellow security professionals, get support, share findings, and participate in community events." canonical: https://turbopentest.com/learn/ecosystem/discord-community source: "TurboPentest Learn" --- # Discord Community ## The TurboPentest Discord Server The TurboPentest Discord server is the primary community hub for users, security professionals, and the TurboPentest team. It is where you get real-time support, share knowledge, discuss findings, and stay informed about platform updates. Join at: **[turbopentest.com/discord](https://turbopentest.com/discord)** ## Channel Structure The Discord server is organized into purpose-specific channels to keep conversations focused and discoverable. ### Information Channels - **#announcements** - Official TurboPentest announcements including new features, platform updates, maintenance windows, and security advisories. Read-only for community members. - **#changelog** - Automated feed of every platform and documentation change, synchronized with the docs changelog. - **#roadmap** - Public roadmap discussion. Vote on upcoming features and suggest new ones. ### Support Channels - **#general-support** - Ask questions about using TurboPentest. Community members and the support team respond here. - **#api-support** - Questions specifically about the REST API, webhooks, and programmatic integrations. - **#integrations-help** - Help with GitHub Actions, MCP Server, Slack, Jira, and other integrations. - **#billing-support** - Credit purchases, subscription questions, and billing issues. Sensitive billing details should be handled via private support tickets. ### Discussion Channels - **#general** - Open discussion about anything related to security, pentesting, or TurboPentest. - **#findings-showcase** - Share interesting (anonymized) findings from your pentests. Learn from real-world examples of what TurboPentest discovers. - **#security-news** - Discuss the latest security news, CVE disclosures, and industry trends. - **#tool-talk** - Discussion about security tools in general - not just TurboPentest's Phase 1 tools, but the broader ecosystem. ### Learning Channels - **#capo-study-group** - Study for the CAPO certification with others. Ask questions about course material and share study tips. - **#capo-certified** - Exclusive channel unlocked after earning your CAPO certification. Network with other certified professionals. - **#tutorials** - Community-contributed tutorials, guides, and walkthroughs. ### Community Events - **#events** - Announcements for upcoming community events including webinars, AMAs (Ask Me Anything), and live pentesting demos. - **#voice-events** - Voice channel used during live events. Events are typically recorded and posted in #tutorials afterward. ## Community Roles Discord roles provide recognition and access control: - **Community Member** - Default role for all verified members - **CAPO Certified** - Earned by passing the CAPO Final Exam. Unlocks the #capo-certified channel and a special name badge - **Top Contributor** - Awarded to members who consistently help others in support channels - **Bug Bounty Hunter** - Awarded to members who have submitted valid bug bounty reports - **Beta Tester** - Access to beta features and the #beta-testing channel - **TurboPentest Team** - Official team members, identifiable by their distinct role color ## Getting the Most from the Community ### Asking Good Questions When seeking support, include: 1. **What you are trying to do** - The goal, not just the error 2. **What you have tried** - Steps already taken and their results 3. **Error messages** - Exact error text, not paraphrased 4. **Configuration** - Relevant settings (with sensitive values redacted) 5. **Tier and target type** - Which pentest tier you are using and what kind of target (web app, API, etc.) ### Sharing Findings When showcasing findings in #findings-showcase: - **Always anonymize** - Remove target URLs, IP addresses, and any identifying information - **Focus on the interesting aspect** - What made this finding notable? Was it a chain? A novel technique? - **Include the remediation** - Help others learn how to fix similar issues - **Tag the finding type** - Use channel tags like `[XSS]`, `[SSRF]`, `[Chain]` for discoverability ### Participating in Events Community events run on a regular schedule: - **Monthly AMA** - The TurboPentest team answers community questions live - **Bi-weekly Webinar** - Deep dives into specific features, integration patterns, or security topics - **Quarterly Pentest Challenge** - Competitive events where participants pentest designated targets for prizes ## Community Guidelines The TurboPentest Discord follows these core principles: 1. **Be respectful** - Treat every member with professionalism and courtesy 2. **No unauthorized testing** - Never discuss pentesting targets you do not have authorization to test 3. **No credential sharing** - Never share API keys, account credentials, or licensed content 4. **Keep it constructive** - Criticism should be actionable and focused on improvement 5. **Protect privacy** - Never share personal information about others without consent Violations result in warnings, temporary mutes, or permanent bans depending on severity. ## Linking Your Discord Account TurboPentest supports **Discord account linking** today. Using Discord OAuth (the `identify` scope only), you connect your Discord identity to your TurboPentest account from Settings > Integrations > Discord. Linking stores your Discord ID and username on your TurboPentest account; it does not grant TurboPentest access to your messages. (Automatic in-server role assignment from this link - for example granting a CAPO Certified or Bug Bounty Hunter role - is not yet wired up.) > **Roadmap - in-channel bot commands.** An interactive Discord bot with slash commands (for example checking a pentest's status, searching the docs, or viewing your credit balance from inside Discord) is a planned enhancement, not a shipped feature. Today there is no interactions endpoint or command handler - only the account-linking flow above is live. Do not rely on slash commands until they are announced in #announcements.