> 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/2025/november-2025.md).

# November 2025

## <mark style="background-color:$primary;">What’s New in This Release</mark> <a href="#whats-new-in-this-release-summary" id="whats-new-in-this-release-summary"></a>

This release provides greater control of the **Mail channel**.

Designers can now prevent the display of email addresses in the Contact List and Autocomplete suggestions on a per persona and per player basis.

## <mark style="background-color:$primary;">Improvements & New Features</mark> <a href="#improvements-and-new-features" id="improvements-and-new-features"></a>

#### **Exercise Editor – Email Channel Visibility Controls** <a href="#exercise-editor-email-channel-visibility-controls" id="exercise-editor-email-channel-visibility-controls"></a>

**What’s Improved**\
Designers can now **hide** specific persona and player email addresses from players’ view in the Mail channel.

This helps keep the Contact List and Autocomplete suggestions focused only on relevant and desirable personas.

<details>

<summary>⚙ <strong>How It Works</strong></summary>

A new **Hide email** toggle has been added in several places. When enabled, email addresses marked as hidden will no longer appear in the player’s Mail Contact List or in Autocomplete when composing a new message:

* **Mail Channel Configuration:** The option allows designers to hide all player emails
* **Teams Table:** Each player now includes an individual toggle to “Hide email”, allowing designers to select which players should be hidden.
* **Persona Details:** Designers can now decide whether a persona’s email should appear in the Contact List or be hidden from player view.
* **Help Desk Channel:** The option keeps the support address available for system use but invisible to players. Note that you need to turn this off even if Help Desk Channel is marked as inactive.

</details>

{% hint style="info" %}
**Use Case Example**\
In many exercises, designers may want players to interact only with fictional personas rather than with other participants.&#x20;

For example, role players or observers may need to log in using specific email addresses that shouldn’t be visible to participants.
{% endhint %}

***

### <mark style="background-color:$primary;">Bug fixes</mark> <a href="#bug-fixes" id="bug-fixes"></a>

Several bugs have been resolved.

&#x20;

&#x20;


---

# 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/2025/november-2025.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.