Discord Turned On Teen Defaults. Five Things Quietly Broke in Your Server.

Discord began a phased global rollout of teen-by-default settings in early March, then pushed the wider age assurance expansion to the second half of 2026 after a rough reception. Most of the coverage was about face scans. That was the wrong thing to worry about.

If you run a server, the part that affects you is not verification. It is that several defaults flipped, and a few of them silently break things community managers have done for years.

What actually changed

• Age-gated spaces. Only age-assured adults can open age-restricted channels, age-restricted servers, and app commands inside them.
• Message Request Inbox. DMs from people a user does not know are routed to a separate inbox by default, and only age-assured adults can change that setting.
• Content filters. Sensitive media stays blurred until an adult verifies.
• Stage restrictions. Speaking on Stage is limited for accounts that have not been age-assured.
• Friend request alerts. Users get a warning prompt on requests from accounts they have no connection to.

Five checks worth doing this week

• Look at your server's age-restricted flag. If you flagged the whole server years ago because of one channel, your reachable audience is now verified adults only. Move the content into a single flagged channel and unflag the server.
• Assume your welcome DM is unread. If onboarding depends on a bot DM to new members, a large share of it now lands in a folder nobody opens. Put the critical step in a public onboarding channel instead.
• Check bots living in flagged channels. App commands are gated in age-restricted spaces. A verification bot or ticket bot sitting in one stops working for exactly the people who need it.
• Use spoiler channels instead of age flags. Discord shipped spoiler channels so operators stop reaching for the age toggle to hide plot leaks and unannounced drops. Same effect, no audience cut.
• Give Stage AMAs a fallback. If your guest has not been age-assured, they may not be able to speak. Confirm before you announce the event, not ten minutes into it.

About the face scan panic

Discord published an unusually blunt post in February admitting it handled the announcement badly. Its own words: "we should have provided more detail about our intentions and how the process works." The company says over 90% of users will never be asked to verify anything, that facial age estimation runs on-device so the video never leaves the phone, and that it added credit card verification after the backlash so nobody is forced into a face scan or an ID upload.

Worth saying plainly: those are Discord's claims about Discord, and right now they are the only numbers anyone has. Discord promised a technical methodology post and transparency reports before the global launch. That is the thing to actually read when it lands.

Why this is happening now

The rollout is not a standalone product decision. Brazil's Digital Statute for Children and Adolescents took effect on March 17, 2026, and the UK and Australia already have obligations in force. Discord is building one system to satisfy several regulators at once, which is why the settings apply globally rather than country by country.

Most servers will get through this without touching anything. The ones that will not are the servers where onboarding was one DM and a prayer. Go check yours.

We run communities for games, brands and Web3 projects, and we build the software they run on. If your server needs someone to actually own this, that is the job we do.