Skip to main content

Ingestion Correlation

Who this is for

Admins resolving duplicate or missing identity matches.

Goal

Fix correlation issues so each person maps to a single identity.

Prereqs

  • At least one connector sync completed

Success criteria

Identities map correctly to their external accounts.

Symptom: duplicate identities for one person

  • Likely cause: mismatched email or missing correlation rule.
  • Fix: standardize email formats and re‑sync the source system.

Symptom: account is not linked to any identity

  • Likely cause: missing attributes or filtered scope.
  • Fix: expand the sync scope and re‑run ingestion.

Example

Two identities exist for “jane@acme.com” and “jane.doe@acme.com.” Confirm the authoritative email source and re‑sync.

Troubleshooting

  • Always correct correlation before enabling automated access workflows.

Assumptions & Questions

  • What exact correlation rules and UI labels are available today?

Next steps

  • /implement/requests/access-requests
  • /reference/object-model