> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/transformation-tools/additional-configurations.md).
# Additional configurations
Here's what you can do with to complete the lineage of your connections.
To identify the lineage across your tools from origin to destination, you will need to connect your data sources to decube. For example, if you want to see a transformation from PostgreSQL table to dbt, you'll need to have both PostgreSQL and dbt connected to see the full lineage.
{% hint style="info" %}
It's best if you connect your data warehouses or relational databases first to decube if you haven't done so, before connecting your transformation tools or BI tools.
{% endhint %}
From the tools you've connected, we figure out the connection names referenced within your queries and list them out in the **Additional Config** so you can map them to existing connections within decube.
### Mapping the data source connections
1. Once you've connected your connections, all you need to do now is to head to the **My Account** page and see all your connections in the Data Sources tab.
Head to the My Account page to see all the connected Data Sources
2. Click on the **Modify** button on your data source. You will land on the **Credentials** tab.
Modifying Data Source
3. Go ahead and map the connections sources to the data sources that you have added into decube. Once done, click on **Save**.
