> For the complete documentation index, see [llms.txt](https://securitybot.gitbook.io/securitybot-knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/chat-filters/bypass-settings.md). # Bypass Settings {% hint style="info" %} **Available on all tiers** — Channel and category bypass settings work on both Free and Premium. [Compare plans →](/securitybot-knowledge-hub/plans-and-pricing/plans-and-pricing.md) {% endhint %} SecurityBot allows you to bypass filtering for specific **channels** and **categories**, giving you control over where its protections are enforced. This is especially useful for: * Staff-only channels * Bot logs or system channels * Internal support or testing areas Bypasses apply across all chat filters, including link blocking, invite filtering, ADA Handles, wallet addresses, and more. *** ## How to Manage Bypass Settings ### Ignore a channel To exclude a specific channel from all SecurityBot filters: ``` /ignore_channel [channel] ``` Example: ``` /ignore_channel staff-chat ``` {% hint style="info" %} **Use the same command again** to remove the channel from the ignore list, this acts as a toggle. {% endhint %} Once ignored, messages in that channel will no longer be scanned or removed by chat filters. You’ll see a confirmation message in Discord: * “Now ignoring channel #staff-chat” (if newly added) * “No longer ignoring channel #staff-chat” (if previously ignored) *** ### Ignore a Category To bypass filtering in every channel under a specific category: ``` /ignore_category [category] ``` Once a category is ignored, SecurityBot will not filter any of the channels it contains. * Repeating the same command again will remove the category from the ignore list. {% hint style="info" %} Use this sparingly. Entire category-level ignores should be limited to trusted internal sections. {% endhint %} *** ### View your current bypasses To review which channels or categories are currently exempt from filtering: ``` /chat_filters exempt_channel view ``` Choose from: * **Ignored Channels** * **Ignored Categories** These appear in a private embed, visible only to you. *** ### Best Practices * Ignore only private or trusted channels such as `#staff-chat`, `#mod-notes`, or bot logs * Avoid ignoring public channels or discussion areas where scams may occur * Use category ignores with caution — they apply to **all** channels within * Audit your ignored areas regularly using `/chat_filters exempt_channel view` and `/chat_filters exempt_category view` {% hint style="info" %} Only users with the Admin role or Discord’s Administrator permission can manage bypass settings. {% endhint %} *** ## Managing Shill Channel Bypass Shillers - they’re everywhere in Web3. While often harmless, some promote malicious Discords, scam projects, or unsafe links. SecurityBot gives you control over where (if anywhere) shilling is allowed. By default, the shill filter is **disabled**. When enabled, it will block any message containing a Discord invite that is not explicitly allowed. Unless it’s posted in your configured **shill channel**. *** ### Enable the shill filter To toggle shill filtering, use: ``` /settings view ``` Then click the **“Block Shills”** button in the private embed response. Once active, all unapproved Discord invites will be blocked server-wide. {% hint style="info" %} Only users with the Admin role or Discord’s Administrator permission can configure shill channel settings. {% endhint %} *** ### What you'll see in the embed When using `/settings view`, you’ll receive a **Block Shills** embed that displays your current shill filtering configuration. The embed will show: * Whether shill blocking is currently **enabled or disabled** * The assigned **Shill Channel**, if one is set * A button that allows you to **toggle the feature** {% hint style="info" %} The button may appear **green** (Enable Shills) or **red** (Allow Shills), depending on whether the filter is currently off or on. {% endhint %} *** ### Set a designated shill channel To allow shilling in one specific place (and block it everywhere else), use: ``` /settings shill_channel [channel] ``` Example: ``` /settings shill_channel #shill-zone ``` {% hint style="info" %} If you enable the shill filter but **do not set a shill channel**, all unapproved invites will be removed server-wide. {% endhint %} *** ### Shill Filter Best Practices * Always set a **clear shill channel** (e.g. `#shill`, `#promotions`) if you allow any self-promotion * Use this filter alongside the **Invite Filter** for better scam prevention * Don’t enable shill blocking without assigning a shill channel or you’ll block all invites *** Next up: Explore additional [scam prevention tools](/securitybot-knowledge-hub/bot-guide/scam-prevention-features.md) designed to protect your community from compromised accounts, scam links, and more. --- # 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: ``` GET https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/chat-filters/bypass-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.