Hello @User17354584642792984449 (Customer)​ , thank you for contacting Okta Community.

Yes, you can have multiple accounts (from multiple orgs) in the same Okta Verify app.

You can use the Troubleshooter tool to check the state of your device. Open the Okta Verify app and tap the account you have added. Scroll down to the Troubleshooter, then tap it. The Troubleshooter will scan your device and look for any obvious issues (like a device time mismatch, a missed update, a network issue, and more) and provide you with tips on how to fix it.

You can also try re-installing the Okta Verify app. There are two scenarios:

1. If you have another super admin account with access to the first org (that you currently have set up with Okta Verify), you can try uninstalling Okta Verify from the system (for example, a phone), then re-installing it. This would be followed by resetting this factor on the affected user's profile in the Okta Admin console. Please note that only a Super Admin can reset the factors or credentials of another Super Admin.
2. If you do not have another super admin account, you must first log into the org (the one with the account already added in Okta Verify). From the Admin dashboard, make sure you have another factor set up, so that you won't, at any point, be left without MFA - that will lock you out (potentially permanently).

• From the end-user dashboard, go to your profile, then settings. Depending on your settings, you may see a list of your enrolled factors (and devices) under Security Methods. You need to find the account that needs to be removed and remove it, while using another factor to validate your identity.
• Then, on the device with Okta Verify, open the Okta Verify app and remove your account. Now, you can uninstall the Okta Verify app and re-install it.
• Refresh the Security Methods app. For Okta Verify, you should now have a button to add the factor. That will trigger the enrollment flow so you can add your account to your device in Okta Verify.
• After this is done, you can try adding the account for the other org (the one that previously showed you the error).

If you are using any software to encrypt the laptop, try to also re-enroll the laptop and check any certificates or keys that the program may have added to the laptop.

If you have a VPN or a network zone set up, it's worth looking into it to ensure your user is permitted to access the org. This you would check in the org that you are having trouble adding.

If those tips do not resolve the issue, more in-depth troubleshooting may be required. In alignment with the Okta Secure Identity Commitment, an org cannot remain without any MFA factors set up for the admin accounts, otherwise it may result in a lockout. If you have a paid account, you can open a Support ticket here (Customer Support Account ID number required).

Unfortunately, if no paid developer or production account is available and you cannot add a factor for the org's sole Super Admin account, the only option left is to sign up for a new free trial or developer account. You may need a different email address for this.

Alternatively, if you do not have a paid account but are interested in getting one, you can contact our Sales team. There is a chance for a paid account to be used to request assistance for a connected free account, but the Sales team would have more details on that. 

Regards.

--

Help others in the community by liking or hitting Select as Best if this response helped you.