# Disable PW reset option for blocked users

**URL:** <https://community.auth0.com/t/disable-pw-reset-option-for-blocked-users/194617>\
**Category:** Get Help\
**Tags:** user-password-management, user-management\
**Created:** [November 18, 2025, 8:03am UTC](https://community.auth0.com/t/disable-pw-reset-option-for-blocked-users/194617 "2025-11-18T08:03:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gateway.xelerators.s](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gateway.xelerators.s/32/72706_2.png) [@gateway.xelerators.s](https://community.auth0.com/u/gateway.xelerators.s)\
**Post date:** [November 18, 2025, 8:03am UTC](https://community.auth0.com/t/disable-pw-reset-option-for-blocked-users/194617/1 "2025-11-18T08:03:00Z")

</div>

Hi all,

I have an app for which I would like to prevent a blocked (bruteforce) user from resetting his password trough the link in the login window.

Yet, I want the non-blocked users to have this possibility.

Is this somehow possible trough a custom action or a template change? I tried changing the “reset password” email template, but was not able to detect if the user is blocked or not, inside of the email template using liquid operators.

---

<div class="post-metadata">

**Author:** ![remus.ivan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/remus.ivan/32/68771_2.png) [@remus.ivan](https://community.auth0.com/u/remus.ivan)\
**Post date:** [November 19, 2025, 8:43pm UTC](https://community.auth0.com/t/disable-pw-reset-option-for-blocked-users/194617/3 "2025-11-19T20:43:13Z")

</div>

Hi @gateway.xelerators.s,

Welcome to the Auth0 Community!

Unfortunately there is no out of the box solution that would disable the forgot password link only for specified users such as blocked ones, since this is an all-or-nothing setting and **Brute Force Protection** was designed this way, to allow users to login after a successful password reset. As already suggested in [community post](https://community.auth0.com/t/disable-password-reset-for-blocked-users-using-universal-login/131617) it would be beneficial to create a [feedback request](https://community.auth0.com/c/feedback/95) since others might be interested as well.

However you can try a workaround method as you have previously mentioned. Checking for a blocked user inside the _reset password_ template can not be done directly, but if you can set a flag in app\_metadata, then you can append this condition to template:

```auto
{% if user.app_metadata.blocked == true %}
  <p>Your account is currently suspended.</p>
  <p>Please contact support at support@yourapp.com to restore access.</p>

```

Or based on the metadata flag you could also deny access to the blocked user using the [Password Reset Triggers](https://auth0.com/docs/customize/actions/explore-triggers/password-reset-triggers)

The tricky part would be setting the true flag after a user is being blocked from Brute Force Protection. Different ways that I can think of would be:

- calling the Management API from your application ( the recommended way would be to do this from a backend application ) and checking if the user is blocked using the [Get a user’s blocks](https://auth0.com/docs/api/management/v2/user-blocks/get-user-blocks-by-id) endpoint, then [Update a User](https://auth0.com/docs/api/management/v2/users/patch-users-by-id)’s metadata with the required flag.
- When Auth0’s built-in brute-force protection blocks an account, it generates a log event with the type `limit_wc`. Use an external log streaming service to capture this event, then update the user’s app\_metadata

Thank you for your post and if you have other questions please let me know.  
Best regards,  
Remus

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 3, 2025, 8:43pm UTC](https://community.auth0.com/t/disable-pw-reset-option-for-blocked-users/194617/4 "2025-12-03T20:43:54Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
