> 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/emedgene-analyze-manual/variant_page/related_cases_section/network-data-view-controls.md).
# Network data view controls
The Network data view controls enable users to display network-wide case data alongside internal case data, providing a broader context for variant interpretation.
These controls are located on top of the Related cases tab.
## Display modes
There are two display modes for the Network data view: Simple mode and Advanced mode. Each mode provides a different level of control depending on your needs.
{% tabs %}
{% tab title="Simple mode (default)" %}
Offers a toggle to quickly switch between viewing internal data only or both internal and network-wide data.
{% endtab %}
{% tab title="Advanced mode" %}
Provides a list of networks with checkboxes, allowing users to select specific networks to include in the view.
{% endtab %}
{% endtabs %}
To change between modes:
* Click Switch to advanced to enable detailed network selection
* Click Switch to simple to return to the basic toggle view
---
# 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/emedgene-analyze-manual/variant_page/related_cases_section/network-data-view-controls.md?ask=&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.
.png?alt=media)
.png?alt=media)