Thank you for the clarification! It still looks a bit odd. For example if you provide both options, true and false, for the single Checkbox field, you will actually see two checkboxes on the form. And even can check them both.

And the value in you custom data becomes not boolean, but array of booleans.

Still it does what I need and even more. I have problems with Complete Registration form: it just crashes when the Self-consent field is the only field required to complete registration (will open the Issue on GitHub).
But now if you set the only one option (true) for the Checkbox field and make it required, it can nicely serve as a Consent field.

Thank you for the clarification! It still looks a bit odd. For example if you provide both options, true and false, for the single Checkbox field, you will actually see two checkboxes on the form. And even can check them both.

And the value in you custom data becomes not boolean, but array of booleans.

Still it does what I need and even more. I have problems with Complete Registration form: it just crashes when the Self-consent field is the only field required to complete registration (will open the Issue on GitHub).
But now if you set the only one option (true) for the Checkbox field and make it required, it can nicely serve as a Consent field.

After upgrading from 1.19 to 1.22.1 when I try to create form field as Checkbox control of type Boolean and assign its value to user.data.subscribe, FusionAuth forces me to provide a list of options. I believe it should work just as single boolean value: true or false.

I deleted all users via admin GUI. I'm not sure what is hard or soft delete. I have entered the DELETE word to confirm the deletion.
Yes, the only difference is the initial registration via Facebook.
On the Source tab in the raw data for the user it has {verified: false}, but in the registration data it shows as verified {registrations: [{applicationId: '...', verified: true}]}
Like If the registration has been cached between user deletion/creation attempts. I hope it helps.

The tenant's SMTP setting are correct and test emails are successfully delivered. I'm evaluating the FusionAuth right now and often delete/re-create users with the same emails. Verification emails are delivered to all users but one. The only thing that distinguishes the problem user from the others is the fact I initially registered him via Facebook identity provider, so his email was automatically verified. After that I deleted the user and trying to register it with just an email (not Facebook). And emails are not delivered. Manually sent SMTP test emails to that address also delivered successfully.

Hi, I have the same problem here. The tenant's SMTP setting are correct and test emails are successfully delivered. I'm evaluating the FusionAuth right now and often delete/re-register users with the same emails. Verification emails are delivered to all users but one. The only thing that distinguish the problem user from the others is the fact I initially registered him via Facebook identity provider, so his email was automatically verified. After that I deleted the user and trying to register with just email (not Facebook). And emails are not delivered. Manually sent SMTP test emails to that address also delivered successfully. I hope this help to investigate.

Is it possible to list all active user sessions and to end/invalidate some of them?