Integrations

Notification destinations — Slack workspaces, Microsoft Teams channels, Jira sites, and custom webhooks — are managed at the organisation level. Connect a destination once and every project in the organisation can route its events to it. This page explains where the new Organisation Settings → Integrations tab lives, what it contains, and which permission gates it.

Accessing the tab

Open Organisation Settings from the user menu, then click the Integrations tab. Customers with the manageIntegrations permission can edit; everyone else is redirected away from the org settings page entirely.

Choosing which events from a given project fire on each destination happens under Project Settings → Notifications. The org tab below is where destinations themselves are connected, edited, and removed.

Project Settings → NotificationsWire this project's events to the destinations your organisation has connected, plus the per-project deliveries log.

What's on the page

Notification keywords

The keyword gate decides which experiments fire notifications. Every new organisation starts with LIVE and PROD pre-configured. Name an experiment "LIVE Checkout copy" and it fires; name it "Internal QA test" and it stays silent. Add, edit, or remove keywords from this panel — removing a keyword shows an impact preview listing the running experiments whose notifications will be silenced.

Notification keywordsHow keywords gate experiment notifications, the default keywords, the safety bypass for SRM and guardrail events, and the impact-preview flow.

Slack workspaces

Connect Slack workspaces via OAuth and add channels under each connected workspace. Disconnecting a workspace revokes its bot token and deletes every channel destination configured on it. Reconnect to resume notifications if the token is revoked outside of A vs B.

Slack integrationOAuth installation, adding channels, signing-secret rotation, and the event schema.

Microsoft Teams channels

Paste a Power Automate workflow URL or a classic incoming-webhook URL. The destination appears in every project's routing panel so any project can wire its events to that channel. Replace the URL in place when Teams regenerates it.

Teams integrationPower Automate vs. classic webhooks, URL rotation, and Adaptive Card payloads.

Jira sites and destinations

Connect Jira Cloud sites via OAuth, then add destinations that map a site to a specific project and issue type. Tickets are auto-filed on safety events (SRM, guardrail breach) and bidirectionally linked from each experiment's results page. Each destination has a Send test ticket button that verifies the OAuth scopes, project mapping, and issue type before any real event fires — and a Delete this test ticket affordance so verification leaves no permanent footprint in the project backlog.

Jira integrationOAuth site connection, destination mapping, ticket creation rules, the test-ticket modal, and bidirectional issue linking.

Webhooks

Create custom webhook destinations that POST signed JSON to any HTTPS endpoint. Each webhook has a signing secret you can reveal once at creation time and rotate on demand. Per-event routing is set per project after the webhook is created.

Webhooks integrationCreating a webhook, signing-secret rotation, payload schema, and delivery retries.

Deliveries log

Every notification attempt across every project in the organisation, with filters for destination, status (delivered, failed, permanent failure, pending), and event type. Failed deliveries can be replayed inline. Project-scoped deliveries also appear under Project Settings → Integrations.

Permissions

Access to this tab requires the manageIntegrationspermission, which is granted to organisation admins and any custom role that explicitly enables it. Project owners without this permission can still read and edit the project's routing panel but cannot connect or remove the underlying destinations.