---
title: "Release 5.10.0"
description: "Scenario Builder co-editing across sections; KBPlugin AI Vision counted in AI Answers statistics; more reliable client identity in OperatorLine."
---

# Release 5.10.0

## What Changed

- **Scenario Builder — co-editing.** Live editor roster, canvas cursors, section-level locks, partial section save, and a request-to-transfer protocol when two editors need the same section.
- **Fast Line Pro / KBPlugin — AI Vision billing visibility.** KBPlugin AI Vision usage during knowledge-base sync is now included in the existing **"Answers provided to clients"** metric on the Fastline tab — no new charts or tabs.
- **OperatorLine — fewer duplicate client cards.** Centralized client creation and channel linking reduces merged or split chat histories caused by duplicate `alias` rows per bot.

## How It Changed

### Scenario Builder — parallel section editing

**Before:** Opening a scenario locked the entire process for one editor; teammates could not work on different sections at the same time.

**Now:** Multiple editors can work on **different sections** of the same scenario in parallel: you see who is online, where their cursor is, and which section is locked. Save applies only to sections you changed; edits in someone else's locked section cannot be published by mistake. Section transfer on request gives an active owner 30 seconds to decline; an idle owner transfers immediately.

See: [Edit a scenario together with colleagues](/en/scenariobuilder/how-to/edit-scenario.md)

### Fast Line Pro — AI Vision in AI Answers statistics

**Before:** AI Vision calls made by KBPlugin during KB sync were not reflected in the overall AI Answers count in Native Statistics.

**Now:** Successful KBPlugin AI Vision usage is added to the existing **"Answers provided to clients"** card (AI Answers section on the Fastline tab). Dashboard layout is unchanged — only the total count grows.

### Operator Panel — duplicate client prevention

**Before:** Without a unique constraint and with non-atomic create paths, duplicate client cards with the same alias within a bot could appear and mix or split OperatorLine histories.

**Now:** Client creation and channel attachment go through centralized atomic logic; on clean instances the unique alias + bot pair is restored. This stops **new** duplicates instead of requiring manual card merges.

## Why It Matters

Scenario teams can ship bot changes faster without waiting on a single editor lock. Finance and operations see KBPlugin AI usage in the metric they already track. Support and operators get more stable client identity across channels.

## Please note

- Co-editing is controlled by **instance feature flags** (`ff_scenario_presence`, `ff_scenario_section_concurrent_edit`) and ships **OFF by default** until ConnectiveOne enables them for your instance.
- Restoring the unique client index on instances that already have duplicate rows requires data cleanup first — the index is skipped while conflicts remain.
- AI Answers statistics for KBPlugin count usage recorded after deploy; historical periods are not backfilled automatically.

## Related Documentation

- [Edit a scenario together with colleagues](/en/scenariobuilder/how-to/edit-scenario.md)
- [Scenario Builder — integrator hub](/en/scenariobuilder/integrator-hub.md)
- [Operator Panel (Operator Line)](/en/operatorline/operator-hub.md)
- [Fast Line Pro — admin hub](/en/fastlinepro/admin-hub.md)