# 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. Organization admins can also choose **Add service** here to start the setup flow.

The top-bar service selector is separate from this settings list. It can show names from active DSNs that have not yet appeared as registered services as non-selectable **Waiting for data..** or **No data** rows; those pending rows do not appear on this page.

Use the settings list for the current set of registered services rather than tracking them elsewhere.

## 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 restricted: **retention** (how long the service's data is kept) is read-only and managed by Brizz, and **bring-your-own-model** settings appear only for organization admins when the feature is enabled.

New services start with your organization's default retention period for session and conversation data. New organizations start at 90 days; an organization without a default creates services with unlimited retention. Existing services keep their current period unless Brizz applies the default to them. A session's metric scores expire with it; raw OpenTelemetry metrics are not affected. Retention is managed by Brizz — to change it, use the **Contact Brizz support** link in the service's retention policy.

### Context

Each service carries a context: what it does, what it can do, and its limitations. Brizz uses it to produce more relevant insights and recommendations.

Brizz fills an entirely empty context automatically, deriving it from the service's captured system prompts once the service has enough sessions and a recent system prompt. The automatic fill writes all three fields together and only while they are still empty, so it never overwrites a context that is already set. Services excluded from AI analytics are skipped.

### 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.

### Processing rules

The **Session configuration** tab holds the service's processing rules: which model call compacts the history, which tool runs other tools, and which tool starts another agent. Editing them requires **Admin** or higher. See [Processing rules](/docs/admin/processing-rules.md) for how to fill one in.

### Labeling rules

A service also has labeling rules that run against its data. The **Sessions** tab labels matching sessions; organizations with issue labeling rules enabled also get an **Issues** tab for automatically labeling issues that match its filters. Managing either kind requires **Admin** or higher. See [Labels](/docs/platform/labels.md) for how the rules follow matching data over time.

## 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.
- [Processing rules](/docs/admin/processing-rules.md) — shape how a service's conversations read.
- [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.

---

[All Brizz documentation](https://docs.brizz.ai/llms.txt) · [Full documentation (single file)](https://docs.brizz.ai/llms-full.txt)
