> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-release-notes/zbrain-coi-release-notes/version-2.3.6-or-jul-17-2025.md).

# Version 2.3.6 | Jul 17, 2025

Read the official release notes for ZBrain CoI version 2.3.6. This security and maintenance release introduces reCAPTCHA on the sign-in page to block automated access and fixes a bug preventing ROI

### **Overview**  <a href="#overview" id="overview"></a>

This release strengthens the security of the COI platform with the addition of reCAPTCHA on the sign-in page to block unauthorized automated access. It also resolves a key issue where ROI values were not being displayed in the AI Opportunities section of the AI CoE Dashboard.

### **Release summary** <a href="#release-summary" id="release-summary"></a>

| **Component**                    | **Capability**        | **What it delivers**                                                                               |
| -------------------------------- | --------------------- | -------------------------------------------------------------------------------------------------- |
| Authentication (Sign-in/sign-up) | reCAPTCHA integration | Adds a reCAPTCHA step to the sign-in process to block bot access and increase security             |
| AI CoE Dashboard                 | ROI data visibility   | Fixed the issue of missing ROI values in AI Opportunities, displaying correct metrics per use case |

### **New f**eatures <a href="#new-features" id="new-features"></a>

#### reCAPTCHA integration on COI sign-in <a href="#recaptcha-integration-on-coi-sign-in" id="recaptcha-integration-on-coi-sign-in"></a>

To strengthen authentication and prevent automated login attempts, reCAPTCHA has been added to the COI sign-in process.

* **What’s new**:
  * A reCAPTCHA widget is now displayed during sign-in.
  * Sign-in is blocked unless the reCAPTCHA is completed.
  * Users receive an appropriate error message if reCAPTCHA validation fails or is skipped.
  * On passing reCAPTCHA and entering valid credentials, the user is signed in as usual.
* **Benefits**:
  * Prevents bots and automated programs from accessing the platform.
  * Strengthens user authentication and protects sensitive user accounts from unauthorized access.

### **Bug fixes** <a href="#bug-fixes" id="bug-fixes"></a>

#### **ROI values not displayed in AI opportunities** <a href="#roi-values-not-displayed-in-ai-opportunities" id="roi-values-not-displayed-in-ai-opportunities"></a>

* In the AI CoE Dashboard, the ROI column under AI Opportunities displayed a dash ("–") instead of the actual ROI values, despite related data such as "Budget Used" and "Impact" being available. ROI values are now calculated and shown properly for each use case. The column now consistently displays a numeric ROI value alongside other performance metrics.


---

# 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://docs.zbrain.ai/zbrain-release-notes/zbrain-coi-release-notes/version-2.3.6-or-jul-17-2025.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.
