# Does mark\_email\_as\_verified work with Custom Databases during initial password setup?

**URL:** <https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438>\
**Category:** Get Help\
**Tags:** email-verification, user-management\
**Created:** [January 21, 2026, 3:22pm UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438 "2026-01-21T15:22:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MPtechteam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mptechteam/32/60385_2.png) [@MPtechteam](https://community.auth0.com/u/MPtechteam)\
**Post date:** [January 21, 2026, 3:22pm UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438/1 "2026-01-21T15:22:27Z")

</div>

In the case of a change password/reset password flow, where the goal is to take advantage of the user’s first password initialization to simultaneously verify their email address, is the `mark_email_as_verified` feature properly applied even when a custom database is used?

---

<div class="post-metadata">

**Author:** ![vlad.murarasu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vlad.murarasu/32/72793_2.png) [@vlad.murarasu](https://community.auth0.com/u/vlad.murarasu)\
**Post date:** [January 21, 2026, 6:53pm UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438/3 "2026-01-21T18:53:24Z")

</div>

Hi @MPtechteam,

Welcome to the Auth0 Community!

**Yes** , the `mark_email_as_verified` parameter is respected when using a Custom Database.

Ensure your Custom Database **Login** and **Get User** scripts return the `email_verified` field correctly. If your underlying legacy database doesn’t store this flag, Auth0 will rely on its own internal user profile metadata once the ticket is processed.

If you have any other questions, feel free to reach out!

Have a good one,  
Vlad

---

<div class="post-metadata">

**Author:** ![MPtechteam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mptechteam/32/60385_2.png) [@MPtechteam](https://community.auth0.com/u/MPtechteam)\
**Post date:** [January 22, 2026, 8:05am UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438/4 "2026-01-22T08:05:36Z")

</div>

Hello Vlad,

Thank you for your response, it was very clear.

I have a follow-up question, mostly out of personal curiosity 😊

Do you think it would be relevant for the Verify script to be executed when the mark\_email\_as\_verified property is set to true, in order to take advantage of that step to update the Custom Database?

In my case, the email\_verified field is stored in the legacy database, and the goal would be to persist this information on the Custom DB side during the verification process, rather than relying solely on Auth0’s internal user profile.

I was therefore wondering whether this behavior is something that is envisioned or recommended, or if there is a specific reason why the Verify script is not triggered in this scenario.

Thanks in advance for your insights.

Best regards,

---

<div class="post-metadata">

**Author:** ![vlad.murarasu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vlad.murarasu/32/72793_2.png) [@vlad.murarasu](https://community.auth0.com/u/vlad.murarasu)\
**Post date:** [January 22, 2026, 1:04pm UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438/5 "2026-01-22T13:04:44Z")

</div>

Hi again @MPtechteam,

The behavior you are seeing stems from how Auth0 separates **Identity Management** (the Auth0 side) from **Identity Provisioning** (your legacy side).

When you use a Change Password ticket with `mark_email_as_verified: true`, Auth0 treats the successful password set as a “proof of ownership” for the email. Auth0 then updates its internal record of that user. However, the **Verify** script is architecturally decoupled from the password reset flow.

The **Verify** script is only invoked when the `POST /api/v2/jobs/verification-email` flow is used and the user interacts with that specific email verification link. Using the “Password Reset” flow to verify an email is an optimization provided by the ticket API, but it doesn’t simulate a full “Verification Email” lifecycle.

Have a good one,  
Vlad

---

<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:** [February 5, 2026, 1:05pm UTC](https://community.auth0.com/t/does-mark-email-as-verified-work-with-custom-databases-during-initial-password-setup/196438/6 "2026-02-05T13:05:19Z")

</div>

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