Administration — Integrations

Configure external platform connections — identity providers, API credentials, AI providers, source control, ChatOps, communication, and platform payment services.

ⓘ Open Administration → Integrations from the Administration navigation • Legacy integration links redirect to this page • After AI credentials are saved, configure routing in Model Platform

Permissions

The hub requires at least one Integrations hub permission. Individual category cards appear only when you hold that category’s manage permission.

Scope	Permission(s)
Open Integrations hub (any category page under the Integrations hub)	Any of: enterprise:manage, identity:manage, api_key:manage, ai_gateway:manage, vcs:manage, git:manage, chatops:manage, communication:manage, cloud:manage

Org API keys are not an Integrations hub category. The api_key:manage permission unlocks hub access and is used elsewhere (for example platform administration). Integration changes are recorded in Audit Logs.

♧

Integration hub

Central place to connect and manage integrations. Category cards show live health, configured count, and last sync where applicable — not fixed totals.

Quick actions

• Add Integration — menu of categories you can manage; navigates to the category page
• Import Configuration — upload JSON (integrations-config-<orgId>.json); currently creates missing secret providers only
• Export Configuration — download JSON metadata for source control, secret providers, cloud, identity, AI, and ChatOps (no secret values)
• Test All Connections — validates source-control connections, cloud connections, and enabled ChatOps integrations; results open in a dialog

Import shows a summary dialog (created / skipped). Credential-backed integrations must still be configured on their category pages after import.

Integration categories

Cards you see depend on your permissions and organization type. Each card shows a health chip (Healthy, Warning, Error, or Not Configured), N configured, and Last sync. Click Manage or Configure to open the category.

⌘

Source Control ›

GitHub, GitLab, Bitbucket, Azure DevOps — repository browsing, stack provisioning, webhooks, GitOps.

git:manage or vcs:manage

♙

Secret Management ›

Platform Secrets, AWS Secrets Manager, Azure Key Vault, Google Secret Manager, Oracle Cloud Vault, HashiCorp Vault.

enterprise:manage

☁

Cloud Providers ›

AWS, Azure, GCP, OCI, DigitalOcean — discovery, provisioning, and cloud account sync.

cloud:manage

♙

Authentication Providers ›

Microsoft Entra ID, LDAP, Okta, Google Workspace, GitHub, GitLab, generic OIDC, generic SAML 2.0.

identity:manage or enterprise:manage

◈

AI Providers ›

OpenAI, Google Gemini, AWS Bedrock, Ollama, Vertex AI, Azure AI Foundry — credentials via platform secret references.

ai_gateway:manage

□

ChatOps ›

Slack, Microsoft Teams, Google Chat, generic webhooks — infrastructure card delivery.

chatops:manage

⌁

Infracost ›

Infracost CLI token for cost estimation and pipeline runs (built-in pricing remains available).

cost:manage

▣

Change Management ›

Jira — governance remediation tickets and ITSM sync.

governance:manage

◇

Container Registry ›

Generic, ECR, ACR, GCR (Artifact Registry), GHCR, Docker Hub — private IaC runtime images.

execution:manage or runner:manage

✉

Communication ›

SMTP, SendGrid (email), AWS SNS (SMS) — verification, MFA delivery, and notifications.

communication:manage

▣

Payments ›

Platform-wide payment processing for billing and subscription checkout.

Platform provider org only · subscription:manage or enterprise:manage

Health & Analytics

Below the category grid, the hub shows Integration Summary KPIs (clickable filters that scroll to categories), distribution charts, and recommendations.

▣

ConnectedCategories with at least one configured integration

▣

CategoriesVisible categories for your permissions

☁

Cloud ProvidersConfigured cloud connections

⌘

Source ControlConfigured Git connections

✓

HealthyCategories in healthy state with config

!

Pending AuthCategories needing authentication or setup

Integration Categories

Configured count per visible category.

Connected Platforms

Cloud and source-control provider distribution from the organization dashboard.

Recommendations (for example “Connect your cloud provider”) appear when the org dashboard detects gaps. Click a KPI again to clear that filter.

Authentication Providers — SCIM

ⓘ On Authentication Providers, the SCIM provisioning section supports Microsoft Entra ID, Okta, Google Workspace, and a Generic SCIM Client. Entra can also use directory sync when Entra SSO is enabled. LDAP, generic OIDC/SAML, GitHub, and GitLab support SSO but not the same SCIM flow unless noted on the provider card.

Export & import format

Export produces version: 1 JSON with organization ID, timestamp, and non-secret metadata:

• Source control — id, provider, auth type, name, account, status
• Secret providers — name, type, config shape (values not included)
• Cloud — id, provider, name, auth method, status, regions, sync mode
• Identity — id, name, type, domain, enabled
• AI providers — id, kind, name, slug, enabled, health status
• ChatOps — id, provider, name, events, enabled

Import validates version and organization ID, then creates secret providers that do not already exist (matched by name and type). Other categories are not auto-created from import.