What each integration gives you
You can connect several integrations of one type — two workspaces, two clusters — each
as its own integration with its own name and credential.
The lifecycle
Every integration follows the same path: create → verify → operate → disable → delete.- Create checks the configuration and, for credential-bearing types, proves the credential against the vendor before anything is stored. A credential the vendor refuses is never saved.
- Verify re-checks the integration on demand, live. Its status is observed, never declared — the note under it says exactly what was established, in plain words.
- Disable stops the integration (deliveries are refused, investigations skip it) but keeps the record, its verification history and its credential. Re-enabling restores it as it was.
- Delete is refused while anything depends on the integration — signals, incidents or investigation records. Disable is the retirement path; the record of what a source produced survives.
Statuses
Degraded is not broken: a Slack workspace connected with a bot token, for example, is
degraded only because message search needs a user token — everything else works.