Workday acquires C1.ai: implications for agentic identity governance

At a glance

What this is: This is an acquisition announcement that frames agentic enterprise identity governance as the next control plane for work, with continuous access management replacing legacy review cycles.

Why it matters: It matters because IAM, IGA, and PAM teams now have to govern people and AI agents together, with access decisions tied to runtime business events instead of periodic certification alone.

👉 Read C1.ai's announcement about joining Workday and agentic identity governance

Context

The central issue is governance of identity in an environment where AI agents act alongside people. Traditional identity programmes assume that accounts are created, reviewed, and retired around human employment events, but agentic systems can appear and act far faster than those governance cycles.

C1.ai's announcement uses the Workday acquisition to argue that identity now sits at the centre of enterprise operations. The practical question for security leaders is not whether AI is involved, but whether existing access models can govern both people and agents without breaking lifecycle discipline.

This is not a breach or incident analysis. It is a market signal that identity governance is moving from a back-office control to an operational core for agentic enterprise design.

Key questions

Q: How should security teams govern access when AI agents and humans share the same apps?

A: Treat AI agents as separate identity subjects with their own approvals, scope limits, and monitoring. Human access policy assumes a person controls the session, but agentic access can chain actions across tools and timing. Governance should separate authentication from authorisation and require explicit policy for non-human actors before they are allowed to reach business apps.

Q: Why do periodic access reviews fail for agentic identity programs?

A: Because access reviews assume privilege persists long enough to be certified. Agents can request, use, and release access inside a single task window, so the control has to shift toward real-time policy enforcement and event-based revocation.

Q: What breaks when AI agents inherit human IAM controls?

A: Human IAM controls break because they assume a person makes a request, waits, and can later be reviewed or deprovisioned. AI agents can chain actions, spawn downstream agents, and complete tasks faster than review cycles can observe. The result is weak attribution, stale privilege, and revocation paths that are too blunt to contain one actor cleanly.

Q: How do organisations know if agent governance is actually working?

A: Agent governance is working when every agent is discoverable, owned, least privileged, and auditable at the action level. Look for reduced shadow AI, fewer embedded secrets, clean revocation on retirement, and logs that show which tools and data paths were used. If those signals are missing, governance is still partial.

How it works in practice

Why quarterly access review breaks for agentic enterprise identity

Quarterly certification assumes a stable identity, a stable privilege set, and enough time between grant and review for the process to matter. Agentic systems invert that assumption because they can be instantiated quickly, act across multiple systems, and change scope within a single business process. In practice, governance has to move from after-the-fact review to issuance-time control, with policy, logging, and revocation attached to each identity event. The technical problem is not simply more automation. It is that the review cadence no longer matches the speed at which the actor can request, use, and discard access.

Practical implication: Shift governance controls toward event-driven issuance and revocation instead of relying on periodic access attestations.

How one system of record changes identity lifecycle control

A system of record for people and agents only matters if it anchors the lifecycle of both identity types. For human users, lifecycle states still map to joiner, mover, and leaver events. For agents, the lifecycle is tied to purpose, scope, runtime context, and shutdown conditions, which means the identity object needs attributes that describe what the agent is allowed to do and when that permission ends. The governance gap appears when the platform tracks the agent but not the access state attached to the agent. That is where identity and authorization drift apart.

Practical implication: Define lifecycle states for agents explicitly so access ends when the agent's purpose or operating context ends.

What identity control plane means in an agentic enterprise

An identity control plane is the layer that decides who or what gets access, under which policy, and for how long, across all connected systems. In an agentic enterprise, that means the control plane must handle human identities, NHI, and AI agents without treating any one of them as an exception path. The architectural shift is important because agent action is not just another workload event. It is a decision-making actor with operational reach. That changes how least privilege is enforced, how activity is recorded, and how accountability is preserved when the actor is not a person.

Practical implication: Treat identity control as a cross-actor policy layer and align it with entitlement, logging, and offboarding workflows.

NHI Mgmt Group analysis

Identity governance is becoming the control plane for agentic work, not a downstream compliance function. The announcement reflects a broader market shift in which access decisions must be made at the point of action, not only at onboarding or quarterly review. When agents can operate continuously across email, finance, code, and cloud, the governance model that matters is the one that can follow runtime behaviour. Practitioners should treat this as a signal to re-centre IAM and IGA around execution-time authority.

The old assumption that privilege is stable long enough to review no longer holds for agentic actors. Quarterly certification was built for human-paced access change. That assumption fails when an identity can be created, exercised, and retired inside a workflow or task window. The implication is not just new tooling but a different governance premise: review cycles no longer prove control over actors that move faster than the review itself.

Named concept: runtime identity control plane. This article points to a governance model in which the identity layer decides access continuously across people, NHIs, and agents. That concept is useful because it distinguishes operational identity control from static directory management and from post-hoc audit. Practitioners should use it to separate lifecycle administration from real-time authorization.

Workforce governance will increasingly converge on shared identity records for people and agents. The Workday angle matters because it suggests agent identity will be managed alongside employee identity rather than in a separate security silo. That convergence can improve visibility, but it also raises the bar for entitlement design, offboarding, and auditability across mixed identity populations. Security teams should prepare for governance models that span HR events, NHI lifecycle, and agent purpose controls in one operating model.

What this signals

Agentic identity governance is moving into the same operational tier as workforce administration, which means identity teams will need to think in terms of control planes rather than directory hygiene. The organisations that can describe each agent's purpose, owner, and termination condition will have the strongest foundation for mixed human and machine identity governance.

Runtime identity control plane: the useful shift is from periodic certification to control at the moment access is issued, expanded, or revoked. That matters because agent behaviour changes the timing of governance, and timing is what legacy access review models were never built to absorb.

For practitioners

• Define separate lifecycle rules for agents Map agent creation, activation, scope change, suspension, and shutdown to explicit governance states instead of reusing human joiner-mover-leaver logic unchanged.
• Move access decisions to issuance time Replace quarterly review dependency with policy checks at the moment access is granted or expanded, especially for agents that can act autonomously across systems.
• Inventory agent-facing entitlements Create a complete map of which agents can reach email, CRM, code repositories, finance systems, and cloud infrastructure, then tie each entitlement to an owner.
• Align identity records to business purpose Record what each agent is for, what systems it may touch, and what condition ends that access so identity state and operational intent do not diverge.

Key takeaways

• The announcement reflects a governance shift where AI agents are treated as first-class identities rather than exceptions hidden inside automation stacks.
• The central control problem is timing, because periodic access review cannot keep pace with identities that act and expire inside workflow windows.
• Practitioners should rework lifecycle, entitlement, and audit models so agent access is tied to purpose, owner, and termination conditions.

Key terms

• Agentic enterprise: An operating model where humans and autonomous AI systems work together inside the same business workflows. The security challenge is that decisions, data movement, and access all happen at machine speed, so governance must track both the actor and the workflow context.
• Identity Control Plane: An identity control plane is the governance layer that decides who or what can access systems and under what conditions. In practice, it coordinates authentication, authorization, privilege review, and lifecycle management across human and machine identities so access policy is enforced consistently across environments.
• Runtime Authorisation: Runtime authorisation is the practice of deciding access while a task is in progress, rather than only at provisioning time. It matters for NHIs because credentials and entitlements can change risk mid-session, especially when automation or AI agents interact with sensitive systems.
• Agent Lifecycle Management: The process of provisioning, governing, updating, and retiring an AI agent or other non-human identity. It includes credential issuance, permission changes, logging, rotation, and offboarding. Without lifecycle control, agents can retain access after their business purpose ends, creating persistent risk.

What's in the full announcement

C1.ai's full post covers the operational detail this analysis intentionally leaves for the source:

• The acquisition context and how the company describes its next operating model inside Workday
• Direct wording on the Workday Agent System of Record and the governance role it plays
• The company's own positioning on governing people and agents across enterprise systems
• The forward-looking mission statement and customer-facing messaging that this post does not reproduce

👉 C1.ai's full post adds the acquisition context and the company’s own framing of identity at the centre of the agentic enterprise.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an identity security programme, it is worth exploring.