Cross-product connector import

What happens

Every Noviqent product shares one sign-in, and every organisation is also registered with Noviqent Business Platform so it shows up in one place across the fleet. When you create an organisation here and Business Platform already knows about an Incident Copilot organisation for the same admin email, this fetches that organisation's own Vault-backed connectors and creates matching ones here — automatically, before you even see the new organisation's dashboard.

Only connector types that exist in both products are imported (GitHub, GitLab, Jira, ServiceNow, Linear, Azure DevOps Boards, Grafana, Confluence, Slack). A type you've already configured directly here is left untouched — this only ever fills gaps, never overwrites.

No credential ever crosses products

Only Vault-backed connectors are ever offered for import — one that stores its credential directly, pasted rather than linked to Vault, is never included. What's actually copied is the connector's non-secret configuration and the name of its Vault secret; the real credential is resolved fresh from your own organisation's Vault space here, the same way every other Vault-linked connector already works.

Nothing to configure

This is entirely automatic and best-effort — there's no setting to turn on, and if the lookup or the import fails for any reason (Incident Copilot unreachable, no matching organisation, nothing importable), organisation creation still succeeds exactly as normal.