The Agent Identity KeyAgent identity finder

Reviewed 3 November 2026

ServiceNow

In short: ServiceNow separates agent invocation access from runtime permissions. Dynamic user is the default execution identity. A dedicated AI user keeps assigned roles across invokers. Zurich documentation describes role masking for dynamic users, but not AI users. Check your release and execution identity before relying on these controls.

What does ServiceNow already give you for agent identity?

Where is the gap?

Invocation access does not govern every runtime action. Zurich documentation distinguishes role masking from AI-user execution; confirm your release before applying that distinction.

Which key results usually apply?

Which products fit?

ProductFits when
Okta for AI AgentsMost of your people sign in through Okta.
NewCoreYou need a named person to approve risky agent actions before they run.
Cyera IdentityAuditors or regulators need evidence of why each agent action was allowed.

Questions buyers ask

Do invocation ACLs limit runtime actions?

ServiceNow says invocation ACLs do not govern what an agent may do once running.

Does a dynamic user always mean a person?

No. ServiceNow includes automated triggers, workflows and parent agents among sources of dynamic identity.

Does Zurich mask AI-user roles?

No. Zurich documentation says AI-user execution enforces all assigned AI-user roles without masking.