# Nested additionalSignUpFields

**URL:** <https://community.auth0.com/t/nested-additionalsignupfields/8591>\
**Category:** Get Help\
**Tags:** additionalsignupfiel, signup\
**Created:** [October 26, 2017, 3:44pm UTC](https://community.auth0.com/t/nested-additionalsignupfields/8591 "2017-10-26T15:44:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tdroste](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@tdroste](https://community.auth0.com/u/tdroste)\
**Post date:** [October 26, 2017, 3:44pm UTC](https://community.auth0.com/t/nested-additionalsignupfields/8591/1 "2017-10-26T15:44:51Z")

</div>

How can I nest additional fields with lock for web version 10.23?

We tried the following with no positive results:

```
additionalSignUpFields:

    {
        name: "mySettings",
        placeholder: "Settings",
        prefill: { "interest": "20"}
    }
]

additionalSignUpFields:

    {
        name: "mySettings.interest",
        placeholder: "Settings",
        prefill: "20"
    }
]

```

We need the user metadata to look like this:

```
"user_metadata": {
    "mySettings": {
        "interest": "20"
    }
}

```

When the user signs up these settings should be set in his account.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [October 27, 2017, 5:01pm UTC](https://community.auth0.com/t/nested-additionalsignupfields/8591/2 "2017-10-27T17:01:58Z")

</div>

That is not supported in the [underlying API used to signup](https://auth0.com/docs/api/authentication#signup) end-users so there is also not support within the Lock option that leverages that same API. In particular, from the API docs:

> `user_metadata` - The user metadata to be associated with the user. If set, the field must be an object containing no more than ten properties. Property names can have a maximum of 100 characters, **and property values must be strings of no more than 500 characters**.

(emphasis is mine)

Each additional user metadata property at signup time cannot be an object, however, you can consider if the use of a [pre-registration hook](https://auth0.com/docs/hooks/extensibility-points/pre-user-registration) to reorganize the user metadata would be a suitable complement to the overall solution. If suitable the hook would be the best place to do it, however, you could always re-arrange metadata in a rule.

---

<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:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/nested-additionalsignupfields/8591/3 "2018-03-02T05:57:09Z")

</div>


