> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/learning-data/getting-started-thoughtspot.md). # Getting Started: ThoughtSpot In the left sidebar under **ThoughtSpot**, click **Answers and Liveboards or Data** to see all your liveboards, answers, tables, views and worksheets, ordered by Last Edited.

## Answers and Liveboards From here, use `Cmd/Ctrl+F` or click the :mag: icon in the header to open a filter on the page.

You can also use the **Filters** on the right side of the page to change which Answer or Liveboard you see based on [Tags](/data-management/tag-management.md), created by and more.

The Created By filter at the top allows you to find dashboards created by a specific user, if you click **+ Add Filter**. ## Data From here, use `Cmd/Ctrl+F` or click the :mag: icon in the header to open a filter on the page.

## Lineage Use the Lineage button on the top right or the Explore button to open the Data Lineage modal.

Here you can the lineage across all ThoughtSpot objects, as well as your Data Warehouse tables or views.

--- # 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.selectstar.com/learning-data/getting-started-thoughtspot.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.