> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs.md). # Navigate Synthesis Outputs Learn how to navigate Synthesis outputs as a reviewer or stakeholder. If you've been sent a link to a Nested Knowledge review, this section is for you. Reading and exploring a review's results doesn't require an account, software experience, or prior familiarity with Nested Knowledge. Everything here is called **Synthesis**: the shareable view of what a review found. A nest is what Nested Knowledge calls one review project. Nothing on these pages is editable. If you're a reviewer building or changing outputs, see [Set up Synthesis Outputs](/review-workflow/synthesis/set-up-synthesis-outputs.md).

A Synthesis review page showing the available review outputs. — Open a shared review to explore its available Synthesis outputs.

### Find Your Page At A Glance | If you want... | Go to | | -------------------------------------------------------------------------------- | -------------------------- | | To ask a question in plain English instead of clicking through pages | Synthesis Chat | | The big picture before diving into any one page — first time viewing this review | Synthesis Abstract | | Findings organized by topic and theme | Qualitative Synthesis | | The numeric, statistical results | Quantitative Synthesis | | A modular visual summary built from cards and charts | Dashboard in Synthesis | | A full written narrative, like a published article | Manuscript in Synthesis | | To see how studies were found and selected | PRISMA Chart | | To see how trustworthy the included studies' methods were | Critical Appraisal Visuals |

The Synthesis navigation menu listing pages such as Abstract, Qualitative Synthesis, and Dashboard. — Use the navigation menu to move between Synthesis outputs.

### Filtering And Exploring Across Pages [**Filters on Synthesis**](/review-workflow/synthesis/navigate-synthesis-outputs/filters-on-synthesis.md) lets you narrow most of the pages above down to a specific subset of studies at once — for example, only studies published after a certain date, or only ones judged low-risk. Dashboard and Manuscript are the two exceptions, since both are already built from exactly the studies and data their author chose. [**Synthesis Chat**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md) is an AI assistant you can ask questions directly — useful if you'd rather type a question than click through diagrams yourself. Every answer is backed by citations to the actual studies in the review. ### Next Steps


Synthesis Abstract	Read the review’s landing page and abstract.	Synthesis Abstract
Qualitative Synthesis	Explore findings by topic.	Qualitative Synthesis
Quantitative Synthesis	Explore numeric findings and comparisons.	Quantitative Synthesis
Dashboard in Synthesis	View the reviewer’s curated summaries.	Dashboard in Synthesis
Manuscript in Synthesis	Read the full written report.	Manuscript in Synthesis
PRISMA Chart	Follow the review’s screening flow.	PRISMA Chart
Critical Appraisal Visuals	View appraisal results.	Critical Appraisal Outputs
Synthesis Chat	Ask questions about the review.	Synthesis Chat
Set up Synthesis Outputs	Build or edit these outputs.	Set up Synthesis Outputs
Exports	Download one-time files from the review.	Exports

--- # 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.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs.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.