Merge duplicate people

Owner: Noor Haddad · Epic: ENG-1688 · Shipped: Tuesday 22 September · Shaped in Emargen as "Merge duplicate people"

Why

A sign-in through single sign-on is matched to a person by email. When the email we hold differs from the person's username in Entra ID or Okta, they can't sign in, and someone usually makes them a new account. Now there are two records: the old one with their roles and requests, the new one they sign in with. Vossberg had about 300 after moving to Okta (SUP-1113).

What we built

• People › Possible duplicates: pairs with the same name at the same home depot, or the same phone number or employee number.
• An administrator picks the record to keep. The other record's roles, depot assignments, waiting requests, history and sign-in move to it, and the other is removed.
• Every merge is written to the audit log with both records.
• A merge can't be undone.

What we left out

• Merging on our own without an administrator.
• Stopping duplicates before they happen.

Since

• 26 October: Kelderby's first single sign-on weekend left nine duplicates, merged the same morning (SUP-1264). Engineering is looking at matching on the employee number at sign-in when the email doesn't match (ENG-1838).