Skip to main content
Version: Beta 🚧

DM Lock

Zallom enabled the DM Lock.
ChaussetteToday at 3:12 AM
🎁 Tu as gagné un Nitro ! Réclame-le ici : nitro-gift.click
sent as a DM to every member of the server…
Your message could not be delivered.
Mass DM · 1/5 received
Arthur
Dawoox
Ichiifriend
Zallom
user28471

RaidProtect's DM Lock feature allows you to permanently close access to direct messages (DMs) sent from the server, surpassing Discord's native limitation which only allows this blocking for 24 hours via the "Pause DMs" security action.

🚦 Use cases and recommendations​

  • Servers exposed to spam or harassment: DM Lock is particularly recommended for public or large-audience communities, where the risk of DM abuse is higher.
  • Temporary events or sensitive periods: During launches, important announcements or periods of high traffic (e.g., contests, promotions), enabling DM Lock helps prevent phishing or scam attempts.
  • Communities with a young audience: For servers with a large number of minors, restricting DMs can strengthen security and prevent inappropriate behavior.
  • Continuous protection: Thanks to automation, there is no vulnerability window caused by forgetting the manual renewal.

❓ How DM Lock works​

RaidProtect automatically renews the DM blocking before it expires, with no vulnerability window.

info

It remains possible to send and receive messages with:

  • friends
  • bots
  • staff
warning

Discord's community features are essential for DM Lock to work properly. Follow our guide to verify that community is enabled on your server.

🚩 DM Lock configuration​

  1. Run the /settings command.
  2. Open the "Protection" tab.
  3. Click "Edit" next to "DM Lock".
  4. In the window that opens, check or uncheck "Close the server's direct messages", then confirm.

/dmlock command​

You can also use the command: /dmlock

It opens the "DM Lock configuration" screen, with a switch to enable or disable the protection. If a prerequisite is missing (Community mode or the "Manage Server" permission), a box tells you and the "Refresh" button lets you check again after fixing it. The command is reserved for members who have the "Manage Server" permission.

DM Lock configuration
Configure the closing of private messages to prevent phishing or scam attempts.

RaidProtect will permanently disable private messages until you disable this protection. We use Discord's "Cybersecurity actions" feature (limited to 24h by Discord, extended to permanent by RaidProtect)


ℹ️ /dmlock-info command​

The /dmlock-info command lets you inform members about the current status of DM Lock on the server. It displays a clear message indicating whether the restriction is enabled or disabled, along with an educational explanation of its purpose.

Objective:

  • Explain why DMs are restricted (fighting spam, scams, phishing).
  • Reduce confusion and recurring questions from new members.
  • Remind members of the conditions for continuing to chat via DMs (friends, staff, bots, previous contacts).

Display example

dmlock-info command screenshot enabled

⚙️ Best practices​

  • Encourage active members to use /dmlock-info to answer new members' questions.
  • Post it regularly or pin it in your welcome channels.
  • Combine it with your rules or announcements to remind members of the server's anti-spam policy.

Frequently asked questions​

Where do I enable DM Lock?​

In /settings, Protection tab, by clicking "Edit" next to "DM Lock", then checking "Close the server's direct messages". The /dmlock command also opens a dedicated screen.

Why can't I enable DM Lock?​

A prerequisite is missing: Discord's Community mode must be enabled on your server, and RaidProtect must have the "Manage Server" permission.

How long do DMs stay closed?​

As long as the protection is active. Discord limits its security action to 24 hours, and we renew it automatically until you disable DM Lock.

Can members still DM each other?​

Yes, if they are friends or have already talked. Bots and staff can also always send DMs.

Does DISCON enable DM Lock?​

Yes, from level 3 of DISCON. When going back down, we only disable it if DISCON was the one that enabled it.

Didn't find what you were looking for?

Search the whole documentation, the glossary and the blog.