Topic starter
23/06/2026 9:11 pm
TL;DR: C1.ai says custom connectors can shorten IGA onboarding from code-heavy projects to YAML-driven configuration or SDK-based builds, normalising users, groups, entitlements, and grants across SaaS apps, APIs, databases, and homegrown systems. The governance shift is not just faster integration: it is whether access reviews and application growth can stay aligned without sacrificing a consistent data model.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “Custom Connectors: Simplifying Integrations Without Code”.
Key questions
Q: How should teams balance speed and governance in application onboarding?
A: Teams should accelerate the repeatable parts of onboarding while keeping ownership, scope, and privilege decisions under governance review.
Q: When does connector speed become a governance problem?
A: It becomes a problem when onboarding delays leave applications outside review and provisioning workflows for too long.
Q: What breaks when application-specific identity data is not normalized?
A: Provisioning and recertification lose consistency because the same access concept is represented differently across systems.
Practitioner guidance
- Define a canonical connector data model Standardise how users, groups, entitlements, and grants are represented before onboarding new applications so every integration feeds the same governance logic.
- Separate complex integrations from configuration-led ones Use code-based builds only where custom logic, pagination, or rate limiting makes them necessary, and prefer configuration where mappings are stable.
- Measure onboarding latency as governance risk Track how long it takes to bring a new application into review and provisioning scope, then treat long delays as unmanaged identity exposure.
Bottom line: Custom connectors matter because application onboarding speed now directly affects how fast governance coverage can expand with the business.
What's in the full article
C1.ai's full post covers the implementation detail this analysis intentionally leaves for the source:
- How Baton SDK structures traits, resource types, resources, entitlements, and grants
- How YAML configuration maps users, groups, and projects without code
- How the connector behaves across cloud and self-hosted deployment options
- How C1.ai positions its 300+ out-of-the-box connectors alongside custom builds
👉 Read C1.ai's guide to custom connectors and IGA onboarding speed →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:21 am
Connector governance is now an IGA control plane issue, not a back-office integration task. The article shows that onboarding speed directly shapes how quickly applications can enter governance scope. When integrations are slow, organisations leave applications partially managed or unmanaged for too long, and that is a lifecycle risk as much as an implementation problem. The practitioner conclusion is that connector strategy belongs in identity architecture decisions, not in isolated engineering backlog management.
A question worth separating out:
Q: How do you decide between code-based and configuration-led connectors?
A: Choose code-based connectors for systems with complex logic, edge cases, or protocol handling needs, and use configuration-led connectors when the target model is stable enough to map without custom development.
👉 Read our full editorial: Custom connectors change IGA onboarding speed for application growth