> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/release-notes/2026/august/15-august.md).

# 15 August

## What's New in This Release

Superteams is here for Osprey & Eagle users! Designers can now create collections of teams and publish content with a single inject to the whole collection. And a team can belong to multiple Superteams. This is perfect for large industry-wide and multi-agency exercises where this improvement will considerable increase productivity.

Also in this release, our AI assistant LISA can now be given documents.

## New Features

### Superteams

> *This release covers Superteams support for MEL content only. Support for publishing Pattern of Life content to Superteams ships in next week's release on 22 August 2026.*

**What's new**

Superteams lets exercise designers and facilitators group multiple teams into a larger collection called a “Superteam.” Any team can belong to multiple Superteams. This release adds Superteam support for MEL content, plus a new Superteam page in the Editor and a new Superteam page in the Facilitator Dashboard.

**Why it matters**

For exercise designers, Superteams removes the need to duplicate injects for what is effectively the same audience across multiple teams - speeding up exercise creation and reducing platform load caused by unnecessary content duplication. For facilitators, Superteams will support dynamic “branching” on a live exercise, such as moving a team into a Superteam to show the consequences of a decision.&#x20;

**Key Features**

* Create and manage Superteams (collections of teams)
* Send injects (MEL) to Superteams *(PoL support arrives 22 August)*
* Move teams between Superteams live during an exercise
* API support: new GET and POST endpoints for creating and retrieving Superteams

> **Licence**
>
> Superteams - Osprey and Eagle
>
> Superteams API - Eagle

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FFIkmhK6SA8BneNyC4nOr%2Fsuperteams%20gif.gif?alt=media&amp;token=07fd3806-9b79-4609-9c8f-fc396a94ac10" alt=""><figcaption></figcaption></figure>

<details>

<summary><strong>⚙️ How it works</strong></summary>

* Each player can only belong to one team, but that team can belong to multiple Superteams.
* The MEL Excel/CSV import format now supports Superteams with additional columns “To Type” and “To” columns:
  * “To Type” has predefined (static) values - Position, Team, Superteam, Role - which cannot be customized.
  * To send content to a Superteam, enter its name in “To” (e.g., “FinanceSector”) and set “To Type” to *superteam*.
  * If “To” is filled in but “To Type” is left empty, the system will create a new Position by design - so “To Type” must be set explicitly for Superteam, Team, or Role targets.
* Post-exercise data downloads and reports will only show the player's team, not their Superteam(s).

</details>

{% hint style="info" %}
**Use Case Example**

For an industry-wide exercise, injects might need to go out to “all banks,” “the finance sector,” and “challenger banks.” A team called “Bank Alpha” can belong to all three Superteams, letting the designer message different audience collections without duplicating injects.
{% endhint %}

### File Uploads for LISA

**What's new**

LISA Assistant now supports file uploads - a capability already available on other Conducttr assistants. Designers can attach documents directly to LISA - briefs, scenario outlines, reference reports - and LISA uses that content to help generate exercise events and injects, speeding up exercise creation and improving accuracy against source material.

{% hint style="info" %}
**Use Case Example**

A designer uploads a real-world incident report to LISA, which uses it as source material to generate a set of exercise events modelled on the incident.
{% endhint %}

## Product Improvements

#### Enter Key to Send in Msngr+

In Msngr+, pressing Enter now sends the message, and Shift+Enter adds a new line - matching standard messaging conventions.

#### Enter Key to Send in Msngr

The same Enter-to-send / Shift+Enter-for-new-line behaviour has been added to Msngr.

#### SSO on Facilitator Dashboard by Default

Eagle clients with SSO enabled will now have SSO enabled by default in the Facilitator Dashboard.

#### Email Reply Threads Open at the Most Recent Message

When replying to an email thread, players now see the most recent email first - the one they're actually replying to - instead of the thread opening at the very first email and requiring scrolling in long threads.

#### Magic Prompt Control for AI Image Generation

The Scenario Editor's AI image generation now includes a "Magic Prompt" toggle near the prompt box. Enabled by default, it lets the AI automatically enhance the prompt before generating the image; when disabled, the original prompt is used exactly as entered, with no enhancement.

## Bug Fixes

Several bugs have been fixed across the platform including fixes for navigation and content handling in the Exercise Editor, Player View and Facilitator Dashboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocs.conducttr.com/release-notes/2026/august/15-august.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
