Workday expands AI ambitions with C1.ai identity platform acquisition
Fresh off its $1.1 billion acquisition of AI startup Sana, Workday is making another bet on enterprise AI, this time targeting the governance challenge. The company said it will acquire agentic identity platform C1.ai to help customers manage and secure AI agents operating across enterprise applications.
Fresh off its $1.1 billion acquisition of AI startup Sana, Workday is making another bet on enterprise AI, this time targeting the governance challenge. The company said it will acquire agentic identity platform C1.ai to help customers manage and secure AI agents operating across enterprise applications.
The acquisition will build on Workday’s Agent System of Record, which gives enterprises a centralized view of their AI agents, by adding controls over what those agents can access across Workday and other enterprise systems, the company said.
That would allow enterprises to grant agents the permissions they need to perform specific tasks and revoke them when those tasks are completed, rather than risk agents retaining access to data and applications they no longer need, it added.
The combined capabilities could also help streamline access management for employees as they join an organization, change roles, or leave, reducing the manual work involved in managing permissions while limiting potential security gaps, it further said.
These governance and identity management capabilities become increasingly important as Workday, alongside the acquisition, also continues to expand the role of AI agents across its suite.
During the week, the company announced several updates to Sana, including making it the new home interface for its applications.
In context
- Topic: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Source: CIO
- Published: 15/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
There is a wide gap between a company that has technology projects and one that has a technology strategy. The first accumulates initiatives; the second decides what it will not do. Moves like this are usually the moment somebody at the top finally wrote down the list of what gets left out.
When I look at a move like this, the question is not which tool they bought but which capability was left installed: an architecture function that holds the line on criteria, a prioritised portfolio with real business owners, and metrics somebody actually reviews every week. Without that, any announcement dissolves within twelve months.
What usually goes wrong
What usually goes wrong is the part never discussed with the areas that will carry the work. It gets decided at the top, communicated downward, and the resistance shows up not as opposition but as slowness. Nobody says no; everything simply takes twice as long and nobody can explain why.
What to watch
- What gets switched off to fund the new thing; if nothing does, the budget will hurt in six months.
- How the relationship with current vendors is left, which is usually where the dependency nobody measured is sitting.
- Who ends up owning the decision, and with what budget of their own rather than borrowed.
How I read this entry
I would treat it less as a technology story and more as a market signal. If one player moves this way, in twelve to eighteen months the rest will have to answer something. Better to decide now, calmly, what that answer will be, rather than improvise it when a client asks.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
