# Services & configuration

The AI services configured for your tenant, and the per-service settings that control each one.

The **Services & configuration** settings are where you see the AI services your tenant sends data from and configure how each one behaves.

## What it is

A **service** is one of the AI services, agents, or MCP servers configured for your tenant — the sources that send telemetry to Brizz. This area lists those services and gives each one its own set of configuration tabs, so you can manage a single service's settings without affecting the others.

## The services list

The services list shows the AI services, agents, and MCP servers configured for your tenant. It's the entry point: pick a service from the list to open its configuration. Use the in-product list for the current set of services rather than tracking them elsewhere — it reflects what's actually reporting into your tenant.

## Per-service configuration

Open a service to reveal its configuration tabs. Each tab owns one aspect of how that service is set up.

### General

General holds the service's basic configuration. It's the default view for a service and is where you manage its core settings. Two areas within General are admin-only: **retention** (how long the service's data is kept) and **bring-your-own-model** settings. Members can view General; changing the admin-only areas requires **Admin** or higher.

### Health Center

Health Center checks the service's recent telemetry for missing or malformed data and suggests how to fix what it finds. Access requires **Admin** or higher and the page is available only when the feature is enabled for your organization.

### Timeline

Timeline is the service's change-event history — a record of how the service has changed over time, including **system-prompt changes**. Use it to correlate a shift in your agent's behavior or quality with a specific change: when a metric moves, the Timeline tells you what changed around then.

### Events

Events is where you manage the event and telemetry mappings for the service — how the events your code emits map into Brizz. This is the tab that turns your [custom events](/docs/instrument/custom-events.md) into the signals Brizz understands for this service. Managing event mappings requires **Admin** or higher.

### Webhooks

Webhooks configures **outbound** webhooks for the service: Brizz calls an endpoint you own when one of this service's sessions or traces matures — `session.matured` when a conversation goes idle and Brizz finishes analyzing it, `trace.matured` when a trace settles. It's the alternative to polling for new data. Managing webhooks requires **Admin** or higher, and the feature is off by default per organization — ask Brizz support to enable it. See [Outbound webhooks](/docs/api/webhooks.md) for the payload, signature verification, and retry behavior.

This is not the same as the *inbound* webhooks under **Integrations**, where an external system such as [Segment](/docs/integrations/segment.md) pushes events into Brizz at a URL Brizz provides. Those are configured per integration, not per service.

### Labeling rules

A service also has labeling rules that run against its data. Managing them requires **Admin** or higher. The rules are covered in the [Labels](/docs/platform/labels.md) documentation — see there for how they work and how to configure them.

## Availability

The services list requires **Organization Admin** or higher. Within a service, **General** and **Timeline** are viewable by any **Member**, while **Health Center**, **Events**, **Labeling rules**, and **Webhooks** require **Admin** or higher. Opening an admin-only tab directly as a **Member** shows an access-denied message. Health Center and outbound webhooks also have to be enabled for your organization; until outbound webhooks are enabled, creating a subscription returns `403`.

## See also

- [Labels](/docs/platform/labels.md) — labeling rules that run per service.
- [Outbound webhooks](/docs/api/webhooks.md) — the events the Webhooks tab subscribes to, and how to receive them.
- [API keys](/docs/admin/api-keys.md) — the keys a service uses to send telemetry.
- [Custom events](/docs/instrument/custom-events.md) — the events the Events mapping tab maps.
- [External links](/docs/instrument/external-links.md) — attach external links to a service's sessions.