> For the complete documentation index, see [llms.txt](https://datalab-docs.datacamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://datalab-docs.datacamp.com/work/report-view.md).

# Report view

### Overview

*Report* is a simplified view of your notebook that automatically hides code cells. This article provides guidance on how to use Report.

You can find the Report toggle on the top right in your workbook interface.

<figure><img src="https://4179539225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZqboFGZzD87nn7oPsm%2Fuploads%2FF34h5nxFdTW742SR5l7K%2Fimage.png?alt=media&amp;token=e1403bdf-8c48-4f15-b37f-b1e3c9da6210" alt=""><figcaption></figcaption></figure>

### How Report View Works

In Report view, code cells are hidden by default, presenting a cleaner view focused on the notebook's text content and outputs. However, the code is not removed or altered, and you can access any hidden code cell at any time by clicking on *View code* next to the cell, when hovering over it.

<figure><img src="https://4179539225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZqboFGZzD87nn7oPsm%2Fuploads%2FZGE8H6yyy7aLNUYabTUd%2Fimage.png?alt=media&amp;token=ee9f8bd2-b482-4158-bceb-81a1afe89724" alt=""><figcaption></figcaption></figure>

Remember that changing the reader mode status does not alter the notebook contents—it only changes the way it is displayed.


---

# 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://datalab-docs.datacamp.com/work/report-view.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.
