> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/data/data-overview.md).

# Data overview

Everything in Trulyp starts with data. The **Data** section is where you connect your databases and turn them into semantic models that Analytics, SuperTables and other extensions can use. **Data** › **Overview** is your starting point: it shows where to go next and lets you jump back to what you were working on.

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-cabc3a09c4b315284abb24e2e930d65b423c81a0%2FData_Overview.png?alt=media" alt=""><figcaption><p>Data › Overview</p></figcaption></figure>

### What's on the page

* **Shortcuts**: go straight to **Open connections**, **Manage semantic providers** or **Browse semantic models**.
* **Three steps to a governed model**: a short checklist that ticks off as you go.
  1. **Create new connection**: connect a database. See [Connections](/trulyp/data/database-connections.md).
  2. **Shape a semantic model**: pick the table your users will work with. See [Semantic modeling](/trulyp/data/semantic-modeling.md).
  3. **Publish confidently**: reuse the model in dashboards, workflows and write-back.
* **Pick up where you left off**: the connections and semantic models you edited most recently, so you can continue right where you stopped.

### How the pieces fit together

|                                                             | What it is                                                                                                                                                           | Who manages it          |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |
| [**Connection**](/trulyp/data/database-connections.md)      | The details Trulyp needs to reach one of your databases.                                                                                                             | **Connections manager** |
| [**Semantic provider**](/trulyp/data/semantic-providers.md) | A link to an external semantic layer, such as Tableau's VizQL Data Service (VDS).                                                                                    | **Connections manager** |
| [**Semantic model**](/trulyp/data/semantic-modeling.md)     | A business-friendly layer on top of a connection or provider: the table, friendly names, descriptions and which columns to show. Analytics and extensions use these. | **Semantic manager**    |

Administrators can do everything. You only see the parts of **Data** that your roles give you access to; see [Roles](/trulyp/settings/members-teams-roles-and-access/roles.md).

{% hint style="info" %}
**Who sees which data?** Each connection and semantic provider is shared with one or more teams. Semantic models follow the teams of the connection or provider they're built on, so you don't set teams on a model itself.
{% endhint %}

Ready? Start by [creating your first connection](/trulyp/data/database-connections.md).


---

# 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.infotopics.com/trulyp/data/data-overview.md?ask=<question>&goal=<user_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.