> 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/2024/september-2024.md).

# September 2024

## September 17th, 2024

{% file src="/files/tQXJDUnqShL6b1d8AiHC" %}

### New Feature <a href="#new-feature" id="new-feature"></a>

#### [**New Screenlock on Facilitator Dashboard**](https://helpdocs.conducttr.com/feature-documentation/running/exercise-control/facilitation/facilitator-dashboard#screenlock)

The "Facilitator Lock" feature allows facilitators to securely lock their dashboard during an ongoing exercise without interrupting the flow of the activity. This feature provides two main options:

1. **Manual Lock**: The facilitator can manually lock the dashboard at any time, such as when they need to step away briefly. The exercise continues without interruption, and the dashboard remains inaccessible until the facilitator returns and unlocks it with their password.
2. **Auto Lock with Timer**: The facilitator can set a timer to automatically lock the dashboard after a specified period of inactivity. This is useful for maintaining security while multitasking. If the facilitator leaves the screen unattended for the set duration, the dashboard locks automatically, but the exercise continues running. The facilitator can unlock it upon their return by entering their password.

### Improvements  <a href="#improvement" id="improvement"></a>

#### [**Microblog improvements**](https://helpdocs.conducttr.com/feature-documentation/running/players-training-audience/navigating-channels/teams-based-channels/social-media/microblog-twitter)

We have enhanced the Microblog Channel to resemble the design and feel of "X" (formerly Twitter), featuring:

1. **New Look and Feel**: The channel's color scheme has been updated from blue to a sleek black, aligning with "X's" aesthetic.
2. **Side Menu**: The options menu has been relocated to the side of the channel for better accessibility and a streamlined user experience.
3. **Customizable Likes Visibility**: Users can now choose to show or hide likes on posts. When likes are hidden, no one can see which posts others have liked, adding an extra layer of privacy and anonymity.

#### **Notification improvement**

if a Choice without any options is selected, then it's recognized as Notification timer.

### Bugs & Fixes

* Eliminated the misleading message “Channel icons only appear in the iPad view” from the Style section.
* Resolved an issue where emails were incorrectly flagged as non-valid due to formatting errors.
* Fixed a bug that was causing file access errors when exporting a Library sharefile.
* Fixed a bug that was causing team upload to fail under certain conditions.&#x20;
* Fixed a bug where "<" ">" symbols in passwords were causing Team Upload to crash.&#x20;

### Performance Enhancements / Improvements

* General performance improvements.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/release-notes/2024/september-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
