Riva Insight: "User Already Exists Under a Different Organization" Error

Grace Wannapongsai
Grace Wannapongsai
  • Updated

Overview

When attempting to log in to Riva Insight or add a user to a Riva Cloud policy, you may encounter one of the following errors:

  • There was an error authenticating you. User with username [email] already exists under a different org.
  • Corporate user with username [email] already exists under a different organization.
  • [email] user already exists in another company.

This error usually means the user’s email address is already associated with another Riva Cloud account, policy, or environment. As a result, Riva cannot complete the login or user setup until the duplicate or conflicting record is corrected.

This issue typically requires assistance from our Riva Support Team.

Common Causes

1. Email Address Exists in the “Notification Email” Field of Another Account

The affected user’s email address may be listed in the Notification Email field of one or more other Riva Cloud admin or sync accounts, in addition to the user’s own sync account.

This can create an identity conflict during authentication.

2. Duplicate or Conflicting LDAP Entry

The user may have more than one entry in Riva’s LDAP directory.

Common scenarios include:

  • The user has both a standard/full sync user entry and an Insight SignOn user entry.
  • The assistantPhone field in LDAP, which stores the OrgId/UserId, is applied to multiple users.

3. User Exists Across Multiple Riva Cloud Instances

The user’s email may be registered in more than one Riva Cloud instance, such as both a production and test/UAT environment.

This can cause a conflict when the user attempts to authenticate.

4. User Was Previously Active in Another Policy

The user may have previously been active in another policy, such as a staging or sandbox policy, and was not fully removed before being added to a new one.

A disabled user with a residual LDAP entry can still trigger this error.

Resolution

This issue requires our Riva Support Team to resolve. Open or escalate a support ticket with Riva and provide the following information:

  • Affected user’s email address
  • Policy Owner, Policy GUID, and connection details from the Policy Advanced Options page
  • Pod/node where the environment is hosted

Riva Support Team will investigate the LDAP entries and remove or correct the conflicting record.

Depending on the root cause, the issue may be resolved by:

  • Removing the user’s email address from the Notification Email field on any other Riva Cloud accounts where it appears.
  • Deleting the conflicting or duplicate LDAP entry for the user so that a clean Insight SignOn user is created on the next login.
  • Searching all LDAP entries to confirm the user’s email address does not exist anywhere else unexpectedly.

After Riva Applies the Fix

After Riva confirms the conflicting user record has been corrected, ask the affected user to:

  1. Close and relaunch Outlook.
  2. Reload Riva Insight settings.
  3. Clear browser cookies/cache if the issue continues.
  4. Attempt to log in or authenticate again.