@nikola Have you checked out our kickstarts or APIs? You should be able to apply the license keys and configure your environments as needed.

If this isn't what you mean, please just give me a little more detail on what you are trying to do and I'll help the best I can.

@anthea-mo It looks like the fix is to upgrade.

I also found this on the users accounts being locked.

If this information does not get you where you need, please let me know.

You have a couple of options.

If you use the hosted login pages/authorization code grant, disabling all grants in the application settings page will prevent people from logging in. If you use the login API and have customer-based API keys, you could turn on the 'require API key for login API' and then disable the customer's API key. If you have the Enterprise plan, you could set up an IP ACL for a unroutable IP range.

However, the easiest way to make sure an application cannot be logged into is to deactivate the application.

Note that as of release 1.68.0 (released in late Jun 2026), there is a mfa_deleter role that can remove MFA from a user.

Please see the release notes for more details.

Since we can’t store API keys in code,

FYI, with the release of 1.64.0, you now can store secrets elsewhere and have lambdas retrieve them.

See the documentation for more details.

My understanding is that state is a map of parameters passed into the template context by FusionAuth, not something you explicitly define in the template itself. If that snippet works even though you can't find a local declaration, it's likely being injected by the email rendering process. Have you checked the template variable documentation or tried outputting the contents of state to see which keys are actually available at runtime?

As of 1.62.0, FusionAuth supports pre-verification of emails and phone numbers.

More details:

https://fusionauth.io/docs/lifecycle/manage-users/verification/identity-pre-verification-using-email

https://fusionauth.io/docs/lifecycle/manage-users/verification/identity-pre-verification-using-phone