Topic starter
22/08/2026 12:00 pm
TL;DR: C1.ai says identity deployments can now start from a goal, read the live tenant, and assemble governance tasks, AI access setup, and approvals through agentic onboarding rather than a manual setup project. The deeper issue is that onboarding is becoming execution, so approval gates, evidence trails, and control design move earlier in the lifecycle.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “C1 Deploy: Onboarding that does the setup for you”.
Key questions
Q: What breaks when onboarding itself can execute identity setup tasks?
A: What breaks is the assumption that onboarding is only a pre-production configuration step.
Q: Why do agentic onboarding flows increase governance risk if they feel easier to use?
A: Because ease of use can hide the moment when the system stops collecting inputs and starts making operational decisions.
Q: How should teams govern MCP tools discovered during AI access onboarding?
A: Treat every discovered MCP tool as an entitlement that needs classification, approval, and ownership before use.
Practitioner guidance
- Define onboarding as a governed workflow Map which setup steps are informational, which are decision points, and which can be executed automatically during identity deployment.
- Review approval gates before agentic execution Require explicit approval for any onboarding step that changes access, creates campaigns, or applies governance actions to live accounts.
- Treat tenant discovery as sensitive data access Limit which identity attributes, reporting lines, and employment-status fields the onboarding flow can read before it builds a plan.
Bottom line: The article shows identity onboarding moving from manual setup toward goal-driven execution that can inspect tenant state and assemble governance work automatically.
What's in the full article
C1.ai's full blog post covers the operational detail this post intentionally leaves for the source:
- The step-by-step onboarding sequence from goal selection through directory connection and tenant discovery
- The live examples of how audit remediation, access reviews, and manager coverage checks are assembled during setup
- The mechanics of agent-assisted task execution and where user approval remains mandatory
- The AI access management flow for MCP servers, including how discovered tools are surfaced and classified
👉 Read C1.ai's blog post on agentic onboarding for identity governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/08/2026 12:02 pm
Goal-led onboarding is collapsing the distance between configuration and execution: the article shows that identity setup no longer has to be a human-run project that ends in a finished configuration. When the onboarding flow reads tenant state, proposes tasks, and can carry some of them out, the setup layer becomes part of the control plane. Practitioners should stop treating onboarding as pre-governance administration and start treating it as governed execution.
A question worth separating out:
Q: How does agentic onboarding change the relationship between human IAM and AI access governance?
A: Human identity governance becomes the foundation rather than a separate track. If directory data, manager relationships, and employment status are not clean, the AI access layer inherits those defects. Teams should therefore sequence people governance first, then allow agent access to build on that baseline.
👉 Read our full editorial: C1.ai onboarding shows how identity setup is becoming agentic