> For the complete documentation index, see [llms.txt](https://docs.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2core.b2broker.com/how-to-articles/manage-system-settings/how-to-set-up-the-registration-wazard/how-to-set-up-fields-for-the-advanced-step.md).

# How to set up fields for the Advanced step

The Advanced step is *deprecated* and can no longer be added to new Registration wizards. If the Advanced step was previously added to your existing wizard, you can edit or remove it, but you can't add new fields to this step.

After registration, the information collected in the Advanced step is displayed on the [Advanced tab](/back-office-guide/clients/general/advanced-tab.md) in the client details.

To set up fields for the Advanced step:

{% stepper %}
{% step %}
Navigate to **System** > **Wizards**.
{% endstep %}

{% step %}
Select an existing Registration wizard and click **Edit**.
{% endstep %}

{% step %}
Go to the **Workflow** tab.
{% endstep %}

{% step %}
Click the **Edit** button located in the Advanced step row.
{% endstep %}

{% step %}
Go to the **Custom fields** tab.
{% endstep %}

{% step %}
To modify settings of an existing field, click the **Edit** button located in the field row.

Configure the following field settings:

* In the **Main field settings** section:
  * In the **Type** dropdown, select the field type.
  * In the **Enabled** dropdown, select `Enabled` to display the field during registration or `Disabled` to hide the field.
* In the **Field attributes** section:
  * In the **Name** field, enter the field name used in the Back Office. Only Latin characters, digits, and underscores are allowed.
  * In the **Label** field, enter the field label. Field labels are displayed on the **Sign Up** page in the B2CORE UI.
  * In the **Rules** dropdown, select one or more rules for validating the data entered in the field by clients.

{% hint style="info" %}
For descriptions of all available field types and data validation rules that can be assigned to the fields, refer to [Field types](/how-to-articles/manage-system-settings/how-to-set-up-the-registration-wazard/field-types-and-validation-rules.md#field-types) and [Validation rules](/how-to-articles/manage-system-settings/how-to-set-up-the-registration-wazard/field-types-and-validation-rules.md#validation-rules).
{% endhint %}
{% endstep %}

{% step %}
Click **Save** to apply the changes to the field settings.

After saving the field settings, you'll be redirected to the fields list on the **Custom fields** tab.
{% endstep %}

{% step %}
Ensure that all the fields you want clients to complete at the Advanced step are enabled.
{% endstep %}

{% step %}
To remove a field that you no longer need in the Advanced step, click the **bin** icon located in the field row.
{% endstep %}

{% step %}
Click **Save** to apply the changes to the wizard.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.b2core.b2broker.com/how-to-articles/manage-system-settings/how-to-set-up-the-registration-wazard/how-to-set-up-fields-for-the-advanced-step.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.