> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/requirements/views.md).
# Views
Violet offers three complementary views of requirements data to facilitate ease of development and review: Table, Graph, and Document. Filters can be applied in any view, and you can switch between [structural groupings](/features/requirements/structure.md) to view requirements in hierarchical or system clusters.
## Table View
To switch back to the standard tabular view, toggle the view selector back to **Table**. Violet will retain any selected filters as it switches between views.
## Graph View
To visualize your requirements graphically, toggle the selector in the top portion of the screen to **Graph** view.
## Document View
To visualize your requirements in a traditional document organization, toggle the selector to Doc View. Use the Doc View settings to select which labels to show or hide. Note: to export a document of your requirements, begin the export process from a table view; see more guidance [here.](/features/requirements/import-and-export.md#export-violet-requirements)
---
# 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.violetlabs.com/features/requirements/views.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.
