# Email verification for Enterprise users

**URL:** <https://community.auth0.com/t/email-verification-for-enterprise-users/28230>\
**Category:** Get Help\
**Created:** [July 19, 2019, 3:00pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230 "2019-07-19T15:00:28Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [August 22, 2019, 1:22pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/4 "2019-08-22T13:22:16Z")

</div>

Hello @mcrawshaw,

Welcome to the Community! If the identity provider is an OIDC provider (e.g., Google), you should get `email_verified` in the security token from the provider. If it is a SAML provider, you have a couple options:

1. Have the provider add an `email_verified` claim to the SAML assertion,
2. Map some other value to `email_verified`.

We went with the second option. From what I can tell, because `email_verified` is a boolean, you can map any [truthy value](https://www.sitepoint.com/javascript-truthy-falsy/) to it. For example, we are mapping the `nameidentifier` field to `email_verified`:

```auto
{
    "user_id": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
    "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
    "email_verified": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"
}

```

We know our 3rd party provider will always provide a valid `nameidentifier`, which in this case happens to be the user’s email address, so by mapping that string to `email_verified`, we get `email_verified` set to `true` at account creation time. I am submitting feedback to Auth0 to allow us to edit `email_verified` for Enterprise users.

---

_[View the full topic](https://community.auth0.com/t/email-verification-for-enterprise-users/28230)._