Skip to main content
Identities connect external system records to durable Atlas objects. Examples include CRM IDs, CCaaS agent IDs, HRIS employee numbers, email addresses, and external account IDs. Identity resolution lets Atlas connect operations across systems without treating each provider record as a different business entity. Mappings and lifecycle changes should be auditable.

​
Identity tuple

Treat an external identity as a scoped tuple:
For each identifier, define:
  • who issues and owns it;
  • the object type it can identify;
  • normalization and case rules;
  • whether it can be reassigned;
  • how conflicts are reviewed;
  • whether it is primary or alternate.

​
Resolution principles

  1. Prefer immutable provider identifiers over names or labels.
  2. Normalize before matching, using a documented rule.
  3. Keep raw source values available for traceability where policy allows.
  4. Make ambiguous matches reviewable instead of silently choosing a record.
  5. Treat merge and split operations as governed lifecycle events.
The external identity write and resolution contracts are not yet published. Use this model to prepare mappings; do not infer an endpoint or payload from the examples.