> ## Documentation Index > Fetch the complete documentation index at: https://docs.authenticateme.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Core settings > Logs, alerts, the Help Desk, DMs, Auto Kick, cooldowns, and the other settings that shape how verification works. Core settings decide how members verify and what they're told along the way. They work in every [verification mode](https://docs.authenticateme.xyz/setup/verification-modes.md) unless noted. ## Verified Role and Verification Channel The two settings every server needs. The Verified Role is given to members who pass, and the Verification Channel is where they start. Both are covered in detail in [Roles and channels](https://docs.authenticateme.xyz/setup/roles-and-channels.md). ## Verification Mode How members verify, which is one of Web-Link, Button-Click, or Instant-Grant. See [Verification modes](https://docs.authenticateme.xyz/setup/verification-modes.md). ## Logs Logs keep your staff informed about every verification. They're split into **modules**, and each module can post to its own channel. A module without a channel isn't logged. ![The Logs card with 24 modules set up](https://mintcdn.com/authenticate-me/uiYE6L6ar1H7VuT4/images/settings/card-logs-light.webp?fit=max\&auto=format\&n=uiYE6L6ar1H7VuT4\&q=85\&s=f6455863ee46036f7ce9a37611255fd5) Turn on **Logs**, then click **Configure**. ![The Logs window, with a channel picked for each category](https://mintcdn.com/authenticate-me/uiYE6L6ar1H7VuT4/images/settings/logs-modal-light.webp?fit=max\&auto=format\&n=uiYE6L6ar1H7VuT4\&q=85\&s=17a8e9ec8dae467360df40576d3654fb) * **Every category** sets one channel for everything at once. * Each category row sets a channel for all of its modules. Expand a row to pick a channel per module. * The **All** checkbox turns every module in that row on or off. ### Modules | Module | What it reports | | - | - | | General Logs | Manual verifications, verification resets, bypass sessions, and Premium changes | | Successful Verifications | Every member who passes | | One module per check | Every member who fails that check, such as Block VPN or Account Age | | Auto Kick | Members kicked for not verifying in time | | Help Desk | Help threads being opened and closed, and a warning if the Help Desk is missing permissions | | Honeypot | Members who posted in the Honeypot channel, and a warning if the Honeypot is missing permissions | A common setup sends Successful Verifications and General Logs to a quiet channel, and every failure to a separate channel your moderators watch. ### What a log looks like **Passed** ![A successful verification log showing the account and the role it was given](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/discord/log-success-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=6252ef593f0851d14d43b9c8ec752e59) Shows the member and the role they were given. If they verified with a [bypass link](https://docs.authenticateme.xyz/moderation/bypasses.md), the skipped checks are listed too. **Failed** ![A failed verification log for a VPN detection, pinging the Moderators role](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/discord/log-failure-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=96a13083cef206ae75753cb89585b0d1) Shows the member, what caught them, and extra details for some checks. For example, Account Age shows the minimum age, GeoGate shows whether the server uses a blocklist or an allowlist, and Block Alternative Account shows both accounts and how they were linked. > [!NOTE] > > Logs only show what staff need. Raw IP addresses, emails, cookies, and fingerprints are never posted. See [Data Collection](https://authenticateme.xyz/data/collection). ## Alerts Alerts ping a role in a module's logs channel whenever that check catches someone. They need Logs to be on, and a check only shows up here once its module has a logs channel. ![The Alerts card with 4 alerts set up](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-alerts-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=58aa67eb54a7e28fe7ac19f35d66f7ef) Turn on **Alerts**, click **Configure**, and pick the role each detection should ping. ![The Alerts window, with the Moderators role picked for some detections](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/alerts-modal-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=f43bbaa3b1b58f6c34a100fba8c93341) > [!NOTE] > > The role has to be mentionable, or AuthenticateMe needs the **Mention @everyone, @here and All Roles** permission in the logs channels it pings in. The [Health](https://docs.authenticateme.xyz/dashboard/health.md) page warns you if a role can't be pinged. ## Auto DM DM members when they join, and when they pass or fail verification. ![The Auto DM card](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-auto-dm-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=c4139ec3dcc959a9e81a84baf4c77261) | Option | Value | | - | - | | Default | On | | Modes | All | With Auto DM on, members get a DM as soon as they join. In Web-Link mode it holds their personal verification link, and in Button-Click mode it points them to the verification channel. AuthenticateMe also DMs members when their time to verify runs out, and in Instant-Grant mode when they're verified. > [!NOTE] > > Members always get a DM with the result after they verify on the web page or with the Verify button, even with Auto DM off, so they know why they weren't let in. ## Notify to open DMs Ping members in the verification channel when their DMs are closed. ![The Notify to open DMs card](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-auto-dm-notify-open-dms-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=53e7c8b4962966623a9c949c1ac50de7) | Option | Value | | - | - | | Default | On, 30 seconds | | Duration | 30 seconds to 5 minutes | | Modes | Web-Link and Button-Click | | Needs | Auto DM | When the join DM can't be delivered, AuthenticateMe mentions the member in the verification channel and explains how to verify anyway. The message deletes itself after the duration you pick. ![The notice posted in the verification channel when a member's DMs are closed](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/discord/notify-open-dms-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=35dfd95cdb9736d9d0e944ff802a8f2d) ## Auto Kick Kick members who haven't verified within the set time. ![The Auto Kick card](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-auto-kick-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=502a2593c6c859cd64e6ed3f7a9d7f81) | Option | Value | | - | - | | Default | Off, 10 minutes | | Timeout | 5 minutes to 7 days | | Modes | All | | Needs | The Kick Members permission | The timer starts when a member joins. If they're still unverified when it runs out, they're kicked with the reason "Auto Kick" and a log is posted. With Auto Kick on, the join DM tells members how long they have, and their verification link stays valid for the same time. ## Cooldown Make members who fail verification wait before trying again. ![The Cooldown card](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-cooldown-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=8669ed38817f976ae91def1295063f1a) | Option | Value | | - | - | | Default | Off | | Timeout | 1 second to 24 hours | | Modes | All | The wait is counted from the member's last failed attempt. A member on cooldown sees "You're on cooldown, try again in" followed by the time left. Being on cooldown isn't a failure, so it isn't logged and no action is taken. ## Help Desk The Help Desk adds a **Help** button to your verification message. Members who can't get verified press it, and AuthenticateMe opens a private thread between them and your support team, with their verification history already in it. ![The Help Desk card](https://mintcdn.com/authenticate-me/doqmYpEurtBuXylj/images/settings/card-help-desk-light.webp?fit=max\&auto=format\&n=doqmYpEurtBuXylj\&q=85\&s=ed0d4f2940c785ba4ea144ba5cd9ae7a) ### Set up the Help Desk **1. Turn on Help Desk** In **Settings → Core**, switch on **Help Desk** and click **Configure**. **2. Pick a Support Role** Everyone with this role is added to each help thread. The role has to be mentionable, or AuthenticateMe needs the **Mention @everyone, @here and All Roles** permission. **3. Choose how threads open and close** ![The Help Desk window with the Support Role and its open and close options](https://mintcdn.com/authenticate-me/uiYE6L6ar1H7VuT4/images/settings/help-desk-modal-light.webp?fit=max\&auto=format\&n=uiYE6L6ar1H7VuT4\&q=85\&s=56a89fc490939181b2bed2475b21d4ca) | Option | Default | What it does | | - | :-: | - | | Require Attempt | On | Members have to try verifying before they can open a thread. | | Support Redirect | Off | The **Contact Support** button on the verification page opens a help thread instead of the AuthenticateMe support server. | | Auto Close | Off | Closes the thread automatically once the member verifies. | | Member Close | Off | Lets members close their own threads. | **4. Save** AuthenticateMe reposts the verification message with the **Help** button. Use the paintbrush on the card to change the first message posted in each thread. > [!WARNING] > > Threads are opened in the verification channel, so it has to be a regular text channel. AuthenticateMe needs **Create Private Threads**, **Send Messages in Threads**, and **Manage Threads** there. If anything is missing when you save, a warning is posted to your Help Desk logs. ### What members see When a member presses **Help**, AuthenticateMe opens a private thread named after them and pings them and your Support Role in it. Pressing it again later reopens their existing thread instead of starting a new one. The first message in the thread is pinned. It shows your Help Desk message, which by default asks the member to describe what went wrong, and a **Verification Records** list of their failed attempts so staff can see the problem right away. Threads archive themselves after a week of inactivity, and close automatically when the member leaves the server. ### Close a thread Press **Close** in the thread. Members of the Support Role and anyone with **Manage Threads** can always close threads, and the member who opened it can too when **Member Close** is on. Closed threads are locked and archived. Opening and closing a thread is posted to the Help Desk logs module, with a button that jumps to the thread. See [Logs](#logs). ## Unverified Role Give members a role until they complete verification. ![The Unverified Role card](https://mintcdn.com/authenticate-me/uiYE6L6ar1H7VuT4/images/settings/card-unverified-role-light.webp?fit=max\&auto=format\&n=uiYE6L6ar1H7VuT4\&q=85\&s=de86ff5479592cae15aa18c6a973f026) | Option | Value | | - | - | | Default | Off | | Modes | Web-Link and Button-Click | The role is added when a member joins and removed when they verify. When you [reset](https://docs.authenticateme.xyz/moderation/reset-verification.md) a member, they get it back. The role has to sit below the AuthenticateMe role, and it can't be `@everyone` or a role managed by another app. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.