> 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/virtual-sources-and-objects/virtual-sources.md).

# Overview

Decube supports two models for bringing source metadata into your catalog: automated ingestion via a native connector, and manual ingestion via virtual sources. Virtual sources give you full control — you push the metadata to Decube directly through the UI or API, on your own schedule, without needing a connector. This makes virtual sources the right choice for tightly secured systems, on-premises infrastructure, or any source where you prefer to own and manage exactly what metadata enters Decube.

{% embed url="<https://youtu.be/OJg_VybvQ6c?si=4RTbYMZ59Ilw3mWY>" %}

## What are virtual sources?

A virtual source is a data source whose metadata you manage directly in Decube, rather than having Decube pull it from the system automatically. You populate objects using Decube's existing data model through the UI or API, giving you precise control over what is documented and how. Virtual sources and the objects under them are fully searchable in the Catalog, can be linked to Glossary terms, and support manual lineage edges to any other asset in your workspace.

## Supported object types

Each virtual source can contain the following types of objects:

| Hierarchy                        | Object types                          |
| -------------------------------- | ------------------------------------- |
| Source → Schema → Table → Column | Schema, Virtual Table, Virtual Column |
| Source → Data Job → Data Task    | Data Job, Data Task                   |
| Source → Dashboard               | Dashboard                             |
| Source → Chart                   | Chart                                 |

## What's not available for virtual objects

Virtual sources don't support operations that require a live connection to the underlying system:

* **Profiling and sampling** — no Preview or Profile tabs on virtual assets
* **Data Quality monitors** — Monitors and Incidents tabs are unavailable on virtual assets
* **Automated lineage** — lineage must be added manually

All other catalog features work as they do on native assets: documentation, tags, custom attributes, ownership, manual lineage, and Glossary links.

## Permissions

Creating, editing, and deleting virtual sources and their objects requires the **Manage data sources** permission (`admin_data_source:edit`). Viewing virtual sources requires view access to the source. If you have view but not edit access, all editing controls are visible but disabled in the UI.

***

{% content-ref url="/pages/HgudG62v5zAZqLrMERQK" %}
[Manage Virtual Sources](/virtual-sources-and-objects/manage-virtual-sources.md)
{% endcontent-ref %}

{% content-ref url="/pages/g96V6dpECdQFUkW5mkAH" %}
[Manage Virtual Objects](/virtual-sources-and-objects/manage-virtual-objects.md)
{% endcontent-ref %}

{% content-ref url="/pages/AOBuHq3Rf5WZIUSynFE6" %}
[Virtual Sources in Lineage](/virtual-sources-and-objects/virtual-sources-in-lineage.md)
{% endcontent-ref %}