Your AI problem is an identity problem
Every agent rollout we've run has stalled in the same place. Not model quality. Not context windows. Permissions.
There's a version of the AI conversation that's entirely about capability. Which model reasons better. How long the context window is. Whether the next release will finally handle your edge cases.
We deploy agents inside real operating companies, and we can tell you that almost none of our blocked projects have been blocked by capability. They've been blocked by an admin who couldn't grant a scope, an OAuth consent screen nobody owned, a credential sitting in someone's password manager, or a simple unanswered question: who is this agent, exactly, and what is it allowed to do?
The models got good faster than our permission systems got ready for them.
Every enterprise tool assumes a human
Identity and access management was designed around a person: one human, one account, one login, one set of roles, revoked when they leave. It handles delegation badly and non-human actors barely at all.
Now you want to introduce something that isn't a person, works across a dozen systems at once, acts hundreds of times a day, and needs a permission surface that's narrower than an admin but wider than any single employee. There's usually no clean way to express that. So teams do one of two things, and both are wrong:
- Give the agent a super-admin account. It works immediately. You now have an unaccountable actor with keys to everything and no meaningful audit trail.
- Give the agent a real person's credentials. Also works. Now your audit log is a lie, and when that person leaves, an unknown amount of automation dies with them.
We've seen both, more than once. The second is more common and more dangerous, because it looks fine until it doesn't.
Treat the agent as a first-class identity
The fix isn't clever prompting. It's boring infrastructure, and it should be in place before the first agent does anything useful:
- Its own identity. The agent gets an account, not a borrowed one. It appears in your directory. It can be suspended without taking a human's access with it.
- Scopes tied to a job, not a person. Don't ask "what can Nina do?" Ask "what does processing an invoice require?" That's a much smaller list, and it's stable when people change roles.
- Credentials held centrally, never pasted. A vault, with rotation. If a key lives in a prompt, a config file or a chat thread, you've already lost the thread of who can do what.
- An audit trail that names the agent. Every action attributable, reviewable, reversible. If you can't answer "who did this and under whose authority", you don't have automation — you have exposure.
- A revocation path you've actually tested. Not theoretically. Actually turn it off once and see what breaks.
The uncomfortable part
This work is unglamorous. It produces no demo. It's the least interesting slide in any deck and the first thing cut when a pilot needs to show progress by Friday.
It's also, in our experience, the single largest determinant of whether an AI programme reaches production or dies as a proof of concept. The pilots that stall don't stall because the agent was stupid. They stall because month three arrives and nobody can safely widen the agent's access without someone senior signing off on a risk they can't articulate.
Capability is being solved for you, quickly, by people with far more compute than you have. Identity is the part nobody else can do on your behalf. If you want a serious answer to "can we let this thing act", start there — long before you start comparing models.
← All posts