Notifications
Clear all
Topic starter
25/06/2026 1:03 am
TL;DR: Most organisations still see the same customer as separate records across apps, CRM, support, and billing, and Liminal says only 11% have fully implemented a consolidated view. That fragmentation distorts analytics, weakens policy consistency, and turns customer identity into a governance problem rather than a simple UX issue.
NHIMG editorial — based on content published by Frontegg: Identity unification matters in SaaS and multi-tenant environments
Questions worth separating out
Q: How should teams unify customer identity across multiple systems?
A: Start by inventorying every system that stores identity data, then define one authoritative record model and one matching rule set.
Q: Why does identity fragmentation create security and compliance risk?
A: Fragmentation makes it hard to apply the same policy to the same person because each system may see a different version of the record.
Q: What do organizations get wrong about customer identity unification?
A: They often treat it as a one-time data cleanup project instead of an ongoing governance process.
Practitioner guidance
- Map every identity source before attempting consolidation Inventory authentication providers, product databases, CRM, billing, and support systems, then document which identifiers each one trusts and updates.
- Set deterministic record-matching rules Prefer stable identifiers such as externalId where available, then fall back to controlled matching logic for email or phone only when the confidence threshold is explicit.
- Build conflict rules for stale or contradictory attributes Define field precedence for contact details, role assignments, and verified identifiers so older values do not reappear after synchronization.
What's in the full article
Frontegg's full article covers the operational detail this post intentionally leaves for the source:
- How the platform maps federated identities from enterprise SSO providers to existing customer profiles.
- How multi-tenant identity management supports one user across multiple organizations or workspaces.
- How manual merge workflows and audit logs are handled in day-to-day administration.
- How compliance and access controls are applied to unified customer profiles.
👉 Read Frontegg's analysis of customer identity unification and profile mapping →
Identity unification across apps: what IAM teams keep missing?
Explore further
25/06/2026 10:11 am
Identity fragmentation is a governance failure, not just a data architecture issue. When a customer exists as multiple records across login, CRM, support, and billing, the organisation cannot enforce one policy view across the lifecycle. That breaks the assumptions behind consistent access decisions, audit trails, and user accountability. Practitioners should treat unification as a control plane for identity governance, not as a back-office housekeeping task.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: How do teams know if unified identity is actually working?
A: Look for fewer duplicate accounts, fewer manual support corrections, stable policy enforcement across systems, and clean audit trails for merges and updates. If identities still split across business units or reappear after synchronization, the control is not working as intended.
👉 Read our full editorial: Customer identity unification is becoming a governance problem
