Topic starter
11/08/2026 3:18 pm
TL;DR: Identity categories still help buyers and vendors, but modern enterprises operate through fluid relationships that cross workforce, customer, partner, service account, and AI agent boundaries, according to Fischer Identity. The governance shift is from account-centric administration to lifecycle-aware control of every relationship, because access now changes as the relationship changes.
Editorial analysis by NHI Mgmt Group, based on content published by Fischer Identity: “Why Workforce IAM and CIAM Are No Longer Enough”.
Key questions
A: They should govern the relationship state, not just the account label.
Q: Why do separate workforce and CIAM systems create governance gaps?
A: Because separate systems often lose the enterprise view of which relationships are active, which access rights were granted for each one and which relationship actually owns the account.
Q: What should organisations do first when identity categories no longer match business reality?
A: Start by identifying the relationship types that exist across the organisation, then map which access rights each relationship justifies and who owns each one.
Practitioner guidance
- Map identities by relationship state Inventory the relationship types your organisation actually governs, such as employee, customer, contractor, vendor, service account and AI agent, then define the access rules tied to each state.
- Tie lifecycle events to access outcomes Require provisioning, deprovisioning, access modification and certification triggers when a relationship starts, changes, pauses or ends, rather than relying on periodic cleanup.
- Assign an accountable owner to every identity For each human and non-human identity, record who sponsors it, who approves it and who is responsible when the relationship changes or expires.
Bottom line: Modern identity programmes fail when they treat workforce, customer and non-human accounts as separate governance problems instead of as changing relationships.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/08/2026 3:30 pm
Relationship, not account, is the correct unit of identity governance. Workforce IAM and CIAM are useful categories, but they are too coarse to describe how modern access actually behaves. A person or system can hold multiple roles over time, and each role changes the meaning of the identity record. The governance consequence is that access must be evaluated against current relationship state, not the presence of an account.
A question worth separating out:
Q: What is the difference between account-centric identity and relationship-aware identity?
A: Account-centric identity treats the login or record as the thing to manage. Relationship-aware identity treats the business relationship behind the identity as the source of authority, so access is governed by purpose, duration, ownership and change state rather than by category alone.
👉 Read our full editorial: Why workforce IAM and CIAM no longer cover identity relationships