> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/release-notes/change_log/change_log_workbench_31.md).

# Change log workbench 31

## Features

* User access policy allows organization to select whether invited Illumina support teams will have access to case data and meta data.
* New ordering role with access only to create a case on Emedgene.

## Bug Fixes

* Visualization | Fixed bug of visualization failing when a large pedigree contains members with and without samples.
* Visualization | A display issue that affected some CNV/SV variants has been fixed.
* Variant Page | Related Cases | CNV overlap calculation logic has been updated to comply with Curate. The overlap percent is calculated by dividing the number of common base pairs between variants from different cases by the size of the variant under investigation
* Population Statistics | Fixed the issue with CNV population data being displayed incorrectly in some cases.
* If case is resolved and case status is changed, case resolution will not be updated


---

# 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://help.bioinsight.illumina.com/emedgene/release-notes/change_log/change_log_workbench_31.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.