Provisioning and onboarding
Planned management contract. Use current Gateway guides for deployed behavior.
Planned capability
This page describes a proposed management contract, not a setup procedure. Current request behavior is documented in the Gateway API reference.
Proposed directory integration
A future SCIM integration would need a supported deployment contract, authentication, source ownership, synchronization cadence and revocation behavior. SCIM identity provisioning alone would not establish manager relationships or allocation authority.
Proposed mappings
Directory users and groups would need explicit mappings to Cortex identities and memberships. Manager relationships, service owners and budget ownership would need separate source mappings. Unresolved relationships would remain unresolved rather than becoming inferred authority.
Proposed onboarding
Joining defaults and effective limits would require an explicit policy. Provisioning would not by itself establish a valid serving credential, available model or successful first request.
Use organization setup and Roles and visibility for the current onboarding contract.