> 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/getting-started/data-source-setup.md).
# 1. Data Source Setup
In this guide, we will walk you through how to connect your data to Select Star through our integrations and star utilizing your metadata through lineage generation.
The first thing you need to do when setting up Select Star is to connect a data source.
Visit the [Integrations](/integrations.md) page to see a list of integrations. Find the page for your data source to see specific setup instructions.
{% content-ref url="/pages/-MgSVP4u2TS\_45Ykm4-n" %}
[Integrations](/integrations.md)
{% endcontent-ref %}
The steps for granting Select Star access to your metadata are slightly different for each source, but you will need admin access to any source you want to connect.
Add your data source to Select Star by going to **Settings.**
Click **Data** in the sidebar, then **+ Add** on the page.
Clicking **+ Add** will open a modal with a dropdown where you can select your data source.
{% hint style="warning" %}
If you have a data warehouse, it is strongly recommended that you add the data warehouse connection **first**, before you add BI tools and other integrations.
{% endhint %}
Once you connect your source, [lineage](/features/lineage.md) will be automatically generated for each data asset across your data sources, as well as the popularity of any tables, columns, and dashboards. \*\*\*\*
---
# 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/getting-started/data-source-setup.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.
