Recurring Member Login Error

Hey ​@JanineMontgomery, thanks for reaching out!

That 422 error almost always comes down to the new email domain not being verified on your organisation. Figma blocks email changes at the SSO level until that's in place, even if the old account has been fully removed.

Here's what I'd suggest checking first:

1. Head to Admin settings → Domains
2. Check whether the new email domain shows as Verified
3. If it's not verified, you'll need to complete domain verification before the seat assignment will go through

If the domain is already verified and you're still hitting the 422, a couple of other things could be at play:

• A conflicting account- if the new email address already has a separate Figma account attached to it (even a free or personal one), that can block the reassignment
• An IdP-driven change- if IT made the email change through an Identity Provider like Okta or Azure AD, SCIM may be pushing the change automatically and hitting the verification blocker before you can act in Figma

You can find more detail on setting up domain verification in our Help Center: Domain verification for organisations.

Let me know what you find, happy to keep working through this with you!

Thank you so much for the help. 
It does seem to be a domain verification issues. But all our other team members are using it, so why would this one account have an issue? 
I’ve tried to verify it through the admin panel, but it’s returning an error saying it’s unable to verify. Also the link you have mentioned is returning a 404.

Hey ​@JanineMontgomery, really sorry about that! Here's the correct one: Domain verification for organisations.
I can see you've already got a support ticket open with us (#1943417), so you're in good hands. Someone from the team will be in touch with you directly to work through the verification error in more detail.

Appreciate your patience in the meantime!