> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2024.3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2024.3/data-and-integrations/registering-metadata.md).

# Registering Metadata

A data source is how data owners expose their data across their organization to other Immuta users. Throughout this process, the data is not copied. Instead, Immuta uses metadata from the data source to determine how to expose the data. An Immuta data source is a virtual representation of data that exists in a remote [data platform](/2024.3/data-and-integrations/registering-metadata/data-source-overview.md).

This section includes reference and how-to guides for registering and managing data sources.

## [Data sources in Immuta](/2024.3/data-and-integrations/registering-metadata/data-source-overview.md)

This reference guide describes Immuta data sources and their major components.

## [Register data sources](/2024.3/data-and-integrations/registering-metadata/register-data-sources/query-backed-tutorial.md)

This how-to guide illustrates how to register data in Immuta.

## [Data source settings](/2024.3/data-and-integrations/registering-metadata/data-source-settings.md)

The guides in this section illustrate how to manage and edit data sources and data dictionaries.

## [Schema monitoring](/2024.3/data-and-integrations/registering-metadata/schema-monitoring.md)

The reference and how-to guides in this section describe schema monitoring and illustrate how to configure it for your integration.


---

# 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://documentation.immuta.com/2024.3/data-and-integrations/registering-metadata.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.