Skip to main content

A User With That Email Already Exists In The System - Error Message When Creating A Login

Resolve “A User With That Email Already Exists In The System” error when creating a user in ChiroHD.

Updated over 5 months ago

📝 Overview

If you receive the error “A User With That Email Already Exists In The System” while creating a user login in ChiroHD, it typically means that the email address is already in use, possibly by a duplicate or inactive user.


⚠️ Reason for the Error

  • The email address you're trying to use is already associated with an existing or inactive user account in the system.


🛠️ Solution Steps

1. 🔍 Check for Duplicate or Inactive Users

  • Go to Settings > Users

  • Click the “Show inactive” checkbox

    • Inactive users will appear in red at the bottom of both the Location User and Organization User tabs


2. ✏️ Edit the Inactive User’s Email

  • Locate the inactive user using the conflicting email

  • Click to edit their profile

  • Modify the email address by adding +inactive before the @

    Example:
    Original: [email protected]
    Edited: [email protected]


3. 💾 Save and Refresh

  • Click Save

  • Refresh your browser to make sure the changes are applied


4. 🔄 Update the Desired User’s Email

  • Go back to the user you want to set up

  • Use the now-available email address

  • Create the user again

  • Resend the ChiroHD invite if needed


Key Takeaways

  • This error occurs when a duplicate or inactive user already uses the same email

  • Use the Show inactive filter to uncover hidden conflicts

  • Add +inactive to the email to retain the old account but free up the address

  • Always refresh your browser after saving changes

  • Re-attempt to create or update the user with the corrected email


📌 Conclusion

ChiroHD requires each user to have a unique email address, even if the account is inactive. By identifying and updating any inactive user accounts, you can quickly resolve email conflicts and ensure seamless user creation and access.

Did this answer your question?