Org-level Integrations

An Organization-level integration is a connection to a third-party provider (for example, Datadog) that is configured once on the Organization and managed by Organization administrators. This is distinct from a per-project webhook, which is configured inside a single project and only sends data for that project's Monitors.

Use an org-level integration when you want a single, centrally managed connection to an external system that applies across the Organization. Use a per-project webhook when you want alerting that is scoped to — and owned within — one project.

note

Org-level integrations are managed from the Organization settings area. Organization settings (including Integrations, Certificates, and Downtimes) are an Enterprise-tier capability. See the pricing page for plan availability.

Org-level integrations vs per-project webhooks

The two mechanisms solve different problems. The table below summarizes where each is configured, who manages it, and what it covers.

	Org-level integration	Per-project webhook
Where configured	Organization settings → Integrations tab	Inside a project, on the Alerts & Webhooks page
Scope	The Organization (a shared, centrally managed provider connection)	A single project's Monitors
Who manages it	Organization administrators	Project Owners and Editors
Typical use	One managed connection to a provider (e.g. Datadog) for the whole Organization	Route a specific project's PASS / SLOW / WARNING / FAIL events to Slack, Teams, PagerDuty, email, OpenTelemetry, etc.
Lifecycle	Created, edited, and removed at the Organization level	Created, edited, and removed within the project

In short: org-level integrations are an Organization concern, configured and owned by Organization administrators; per-project webhooks are a project concern, configured and owned within each project. For the full list of webhook providers and how to add a per-project webhook, see Using Webhooks.

View and manage Organization integrations

1. Open the Organization settings for your Organization (the gear/settings control next to the Organization picker).
2. Select the Integrations tab.
3. The Integrations list shows each connected provider with its Name, Provider (for example, Datadog), Created At, and Last Modified.

From this tab, Organization administrators add, edit, and remove provider connections that are shared across the Organization.

note

The exact in-product steps for adding a new provider connection could not be verified against a live tenant for this guide and may vary by provider. If you do not see the Integrations tab, confirm that your account has Organization administrator access and that your plan includes Organization settings (see plan availability and pricing).

How an integration relates to other Organization settings

The Integrations tab sits alongside the other Organization-level settings:

• Certificates — Organization-managed mTLS and signing certificates.
• Downtimes — Organization-wide downtime windows that all schedules respect. See Downtimes.

These are all configured once at the Organization level rather than per project.

See also

• Using Webhooks — per-project alerting and the full list of supported webhook providers.
• Downtimes — Organization-wide and schedule downtime windows.
• Pricing — plan availability for Organization settings.