> 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/reports/multisource/faq.md).
# FAQ
### How do I manage the columns shown within the table?
We provide two options for managing column visibility.
1. Click on the word **Columns** on the left of the table to open the tool panel. Here you can check or checkbox specific columns of your choosing.
2. Hover over a column header name to prompt a hamburger icon (three horizontal lines) to appear. Click on the icon to list all columns alongside checkboxes to manage which columns you see.
The Revision column is unchecked and hidden from view.
Unchecking columns hides them from both the table and downloaded files.
### What file types are supported for download?
Data from the table are downloadable in Excel and CSV formats.
### W**hat additional features can I expect tied to Multisource Reports?**
We’re actively building out additional relationship types and properties in the table. Supporting a row detail view and manual entity Insertion are on our near-term roadmap. Check back soon for an enhanced feature set!
---
# 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/reports/multisource/faq.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.
