Registration

View and manage registration profiles that define the client registration process in the B2CORE UI, for both individual and corporate clients

On this page, you can view and manage registration profiles that define the client registration process in the B2CORE UI.

The new registration settings replace Registration wizards and work together with custom fields, allowing you to build a registration process tailored to your needs — from a simple form with an email address and a password to a multi-step process with custom fields.

After enabling a registration profile, Registration wizards are automatically disabled.

The following information is provided about each registration profile:

Type

The type of clients to which the registration profile applies: Individual or Corporate.

Caption

The name of the registration profile.

Enabled

Indicates whether the registration profile is enabled.

To create a new registration profile, click the Create button.

Pre-filling registration fields with a link

You can share a sign-up link that opens the registration form with some fields already filled in — for example, the email address and the country you already know about the client. Every pre-filled value stays editable, so the client can correct it before submitting.

Pre-filling works only with the simplified registration flow — the new registration flow in the B2CORE UI, built from the registration profiles described on this page. It has no effect on the form of the legacy Registration wizards.

Build the link

Look up the machine name of each field you want to pre-fill.

For custom fields, it is the Machine name on the System > Custom Fields > Fields page (see Custom fields). Standard fields use their own names, such as email.

Take the sign-up URL of your B2CORE UI and add the ID of the registration flow to open, followed by one init[<machine name>]=<value> parameter per field:

https://example.com/auth/register/01936f7a-4b21-70c8-9d5e-6a1f2c3b4d5e?init[email]=john.doe@example.com&init[country]=196

Replace https://example.com with the address of your B2CORE UI, 01936f7a-… with the ID of your registration flow, and URL-encode the values.

The ID makes the link open one specific registration form, so the client does not have to choose the client type first. You find it in the list of registration profiles on this page, in System > Registration.

A link without the ID works as well:

https://example.com/auth/register?init[email]=john.doe@example.com&init[country]=196

The client picks the client type first, and the parameters survive that step and reach the form.

Values by field type

Field type	What the link can pass
Text, Multiline, Email, URL, Phone, Integer, Decimal, Date, Date & time	One value. If the parameter is repeated, the first value is used.
Select	One value that matches an option configured for the field. A value that matches no option is ignored.
Multiselect	Several matching option values, passed as repeated parameters (`init[hobbies]=chess&init[hobbies]=golf`), in the array form (`init[hobbies][]=chess&init[hobbies][]=golf`), or as a comma-separated list (`init[hobbies]=chess,golf`).
Boolean	Only `true` selects the field. Any other value leaves the field as it is.

For Select and Multiselect fields, the link must carry the value of the option, not the label the client sees. For a field with a reference list, such as the country field, the option value is its numeric ID — for example, init[country]=196.

Password fields, and any other fields that hold secret values, are never pre-filled — the value in the link is ignored. Read-only fields and names that do not exist in the form are ignored as well.

Good to know

Pre-filled values are validated straight away, so a value that does not pass the field validation is highlighted as soon as the form opens.
In multi-step registration forms, values are applied to all steps at once, and stepping back and forth does not overwrite what the client has typed.
The parameters stay in the address bar: if the client reloads the page, the values from the link are applied again and any edits are lost.
Values are limited to 1,000 characters; anything longer is truncated.
A value that contains a comma is pre-filled only up to the comma, because commas separate multiple values.