
## What does Atlan crawl from Omni?

URL: https://docs.atlan.com/apps/connectors/business-intelligence/omni/references/what-does-atlan-crawl-from-omni

> During an Omni crawl, Atlan extracts metadata for Models, Topics, Folders, and Documents (Dashboards and Workbooks). Reference tables map each Omni property to its Atlan asset.

Atlan extracts metadata for Models, Topics, Folders, and Documents (the unified type for Omni Dashboards and Workbooks) from Omni and maps each property to its Atlan asset model. The tables below list which Omni properties are read and how they appear on the corresponding Atlan asset. Atlan also supports the following lineage:

- Asset-level lineage from **warehouse tables** (upstream) through **Omni topics** to **Omni documents** (downstream), rendered as a two-hop chain: `Table → Process → OmniTopic → Process → OmniDocument`. Lineage is emitted at runtime as `Process` entities—there is no typed `warehouseTables` relationship on `OmniTopic`. The warehouse → topic hop is bound by qualified-name lookup matched the Atlan warehouse connection you map in the workflow's **Atlan source-connection map** field (see [Crawl Omni](https://docs.atlan.com/llms/connectors/omni/crawl-omni/llms.txt)); the topic → document hop is emitted from the topics each document is built on.
- Column-level lineage isn't yet supported—table-level only.

:::info Asset types
Every Omni asset inherits from a single abstract supertype, `Omni`, which carries two cross-cutting attributes—`omniId` and `omniUrl`—that apply to every concrete subtype. The concrete types Atlan materializes are `OmniModel`, `OmniTopic`, `OmniFolder`, and `OmniDocument`.
:::

## Models

Atlan maps models from Omni to its `OmniModel` asset type.

| Source property | Atlan property | Where in Atlan |
| --- | --- | --- |
| `models[].name` | `name` | asset profile and overview sidebar |
| `models[].description` | `description` | asset profile and overview sidebar |
| `models[].id` | `omniId` | asset profile |
| `models[].updatedAt` | `sourceUpdatedAt` | asset profile |
| `models[].ownerName` | `ownerUsers` | asset profile and overview sidebar |
| `models[].modelKind` | `modelKind` (`SHARED` or `WORKBOOK`) | asset profile |

## Topics 🔀

Atlan maps topics from Omni to its `OmniTopic` asset type. **Topics are the anchor for warehouse → Omni lineage**—lineage `Process` entities point at the `OmniTopic` from the upstream warehouse `Table`.

| Source property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Topic name | `name` | asset profile and overview sidebar |
| Topic description | `description` | asset profile and overview sidebar |
| Topic id | `omniId` | asset profile |
| Topic name (Omni-native) | `omniName` | API only—indexed for search |
| Topic `baseViewName` | `baseViewName` | asset profile |
| Topic `updatedAt` | `sourceUpdatedAt` | asset profile |

> Warehouse → Topic lineage (and, in turn, Topic → Document lineage) is emitted at runtime as `Process` entities by the Omni connector. There is no typed `warehouseTables` relationship on `OmniTopic`.

## Folders

Atlan maps folders from Omni to its `OmniFolder` asset type. Folders are purely structural and play no role in lineage.

| Source property | Atlan property | Where in Atlan |
| --- | --- | --- |
| `folders[].name` | `name` | asset profile and overview sidebar |
| `folders[].id` | `omniId` | asset profile |
| Fully qualified folder path | `path` | asset profile—indexed for search |
| `/api/v1/folders/{folderId}/permissions` | `ownerUsers` | asset profile |

## Documents (dashboards and workbooks) 🔀

Atlan maps Omni Dashboards and Workbooks to a single unified asset type, `OmniDocument`, distinguished by the `documentType` attribute (`DASHBOARD` or `WORKBOOK`). **Documents are downstream lineage participants**—`Process` entities point at the `OmniDocument` from the `OmniTopic` it's built on.

| Source property | Atlan property | Where in Atlan |
| --- | --- | --- |
| `documents[].name` | `name` | asset profile and overview sidebar |
| `documents[].description` | `description` | asset profile and overview sidebar |
| `documents[].id` | `omniId` | asset profile |
| `documents[].url` | `sourceURL` | asset profile—opens Omni in a new tab |
| `documents[].url` | `omniUrl` | asset profile—Omni deep link |
| `documents[].updatedAt` | `sourceUpdatedAt` | asset profile |
| `documents[].documentType` | `documentType` (`DASHBOARD` or `WORKBOOK`) | asset profile and overview sidebar |
| `documents[].sourceType` | `sourceType` | asset profile |
| Folder path (denormalized) | `folderPath` | asset profile—indexed for fast lookup |
| `/api/v1/documents/{documentId}/permissions` | `ownerUsers` | asset profile |

## Warehouse sources supported for lineage

The table below lists databases supported by the App.

| Omni source database |
| --- |
| Amazon Athena |
| Amazon Redshift |
| ClickHouse |
| Databricks |
| Google BigQuery |
| Microsoft SQL Server |
| MySQL |
| PostgreSQL |
| Snowflake |

---
