# ACUL MFA screen - User metadata fields availability

**URL:** <https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065>\
**Category:** Get Help\
**Tags:** phone-factor, mfa\
**Created:** [December 1, 2025, 11:16am UTC](https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065 "2025-12-01T11:16:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vvidal](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vvidal/32/73617_2.png) [@vvidal](https://community.auth0.com/u/vvidal)\
**Post date:** [December 1, 2025, 11:16am UTC](https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065/1 "2025-12-01T11:16:39Z")

</div>

Hello, good morning. I have been implementing the ACUL screens journey and everything has been going fine so far. I have only encountered an issue that haven’t been able to solve.

We are creating users dynamically via the management api and sending them a reset password afterwards. Once their password has been updated and they want to login for the first time, the `login` screen is shown. Then, the `mfa-sms-enrollment`screen popus up.

I have been carefully reading and following the ACUL docs and have seen that the `MfaSmsEnrollmentInstance` should have the following properties:  
[https://auth0.com/docs/customize/login-pages/advanced-customizations/reference/mfa/mfa-sms#properties-2](https://auth0.com/docs/customize/login-pages/advanced-customizations/reference/mfa/mfa-sms#properties-2)

What I need is to somehow get the user\_metadata fields on the `mfa-sms-enrollment` screen, as when I try to log them, they are always null.

I have tried:

```auto
import MfaSmsEnrollmentInstance from “/auth0-acul-js/mfa-sms-enrollment”;

export const useMfaSmsEnrollmentManager = () => {
  const mfaSmsEnrollmentInstance = useMemo(
    () => new MfaSmsEnrollmentInstance(),
    []
  );

  console.log({ user: mfaSmsEnrollmentInstance.user }); // The user object is displayed with the userMetadata property as null

  const metadata_prop_test = mfaSmsEnrollmentInstance?.user.userMetadata?.test;
  console.log({ metadata_prop_test }); // Undefined

...

```

I have double checked and the `test` field exists on the `user_metadata` object of the user:

`{`  
` “blocked”: false,`  
` “created_at”: “2025-11-27T16:31:37.707Z”,`  
` “email”: “email@email.com”,`  
` “email_verified”: false,`  
` “family_name”: “zzz”,`  
` “given_name”: “zzz”,`  
` “identities”: [`  
` {`  
` “connection”: “Username-Password-Authentication”,`  
` “provider”: “auth0”,`  
` “user_id”: “0000000000000000000”,`  
` “isSocial”: false`  
` }`  
` ],`  
` “name”: “zzz”,`  
` “nickname”: “zzz”,`  
` “phone_number”: “+34000000000”,`  
` “phone_verified”: false,`  
` “picture”: "zzz"`  
` “updated_at”: “2025-12-01T09:11:23.253Z”,`  
` “user_id”: “auth0|0000000000000000000”,`  
` “user_metadata”: {`  
` “test”: “12345”, // This is the field that I need`  
` },`  
` “last_ip”: “zzz”,`  
` “last_login”: “2025-12-01T09:11:23.252Z”,`  
` “logins_count”: 1,`  
` “blocked_for”: [],`  
` “guardian_authenticators”: [],`  
` “passkeys”: []`  
`}`

I have also tried adding a trigger on the post login action but it is not fired until the mfa has been completed. I don’t know if I’m missing something, but I have run out of ideas.

Any help would be highly appreciated. Many thanks.

---

<div class="post-metadata">

**Author:** ![vvidal](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vvidal/32/73617_2.png) [@vvidal](https://community.auth0.com/u/vvidal)\
**Post date:** [December 2, 2025, 12:03pm UTC](https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065/3 "2025-12-02T12:03:48Z")

</div>

Hello, I’m answering my own question one day later. I don’t know how could I miss it on the first place.

The Universal Login context can be customized: [Configure ACUL Screens](https://auth0.com/docs/customize/login-pages/advanced-customizations/getting-started/configure-acul-screens#customize-the-universal-login-context-object)

This way I can specify which fields are being sent to the client, so my issue is now solved.

 ![image](https://global.discourse-cdn.com/auth0/original/3X/c/d/cde76be42896e770cba0b6b8c9831369f08a90f6.png)

Hopefully this can help any other people that find themselves in a similar situation. 🙂

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [December 2, 2025, 4:31pm UTC](https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065/4 "2025-12-02T16:31:15Z")

</div>

Hi @vvidal

Thanks for sharing the solution and letting us know it got resolved!

If you ever have any other questions, feel free to let us know by posting here again!

Kind Regards,  
Nik

---

<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 16, 2025, 4:31pm UTC](https://community.auth0.com/t/acul-mfa-screen-user-metadata-fields-availability/195065/5 "2025-12-16T16:31:21Z")

</div>

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