> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/business-intelligence/omni-integration/omni-integration-discovered-resources.md). # Omni Integration Discovered Resources ## Omni Integration Discovered Resources ### Overview The Omni integration discovers the following resources: * Omni Account * Omni Folder (including structural **Hub** and per-user **personal folder** containers) * Omni Model * Omni View * Omni Topic * Omni Dimension * Omni Measure * Omni Workbook * Omni Query * Omni Dashboard * Users (when "Observe users" is enabled) * User groups (when "Observe groups" is enabled) ### Omni Account A single resource of type `omni_account` is observed for each configured Omni source, representing the top-level Omni organization. #### Properties | Property | Description | | ---------------- | --------------------------------- | | `name` | The organization or instance name | | `type` | Always `omni_account` | | `subtype` | Always `omni_account` | | `external_links` | Link to open the Omni instance | ### Omni Folder Folders are organizational containers in Omni for organizing workbooks. Folders can be nested to create a hierarchy. Euno also observes structural **Hub** and per-user **personal folder** containers under the account so organization and restricted folder trees have a consistent parent in Euno. #### Properties | Property | Description | | ---------------- | ------------------------------------------------------------------------------------- | | `name` | The folder name | | `type` | Always `omni_folder` | | `subtype` | Always `omni_folder` | | `created_by` | The name of the user who created the folder | | `external_links` | Link to open the folder in Omni | | `members` | Users and/or user groups that have access to the folder (with optional role metadata) | ## Omni Semantic Layer ### Omni Model Models are semantic layers in Omni that provide business-friendly views of your data warehouse. They contain views and topics, and serve as the data source for workbooks and dashboards. #### Properties | Property | Description | | --------------------- | -------------------------------------------------------------- | | `name` | The model name | | `type` | Always `omni_model` | | `subtype` | Omni model kind (for example `SHARED`) | | `created_at` | The timestamp when the model was created | | `updated_at` | The timestamp when the model was last modified | | `database_technology` | Warehouse technology for the model connection (when available) | ### Omni View Views are defined within Omni models or workbooks and represent tables or logical structures with fields. They can reference other views or database tables. #### Properties | Property | Description | | --------- | ------------------ | | `name` | The view name | | `type` | Always `omni_view` | | `subtype` | Always `omni_view` | ### Omni Topic Topics are business-friendly abstractions within Omni models or workbooks that group related views and fields for analysis. #### Properties | Property | Description | | --------- | ------------------- | | `name` | The topic name | | `type` | Always `omni_topic` | | `subtype` | Always `omni_topic` | ### Omni Dimension Dimensions are dimensional fields within Omni views or topics, typically used for grouping and filtering in queries. #### Properties | Property | Description | | ------------- | ------------------------------------------------------------------ | | `name` | The dimension name (label when provided, otherwise the field name) | | `type` | Always `omni_dimension` | | `subtype` | Always `omni_dimension` | | `label` | Display label from Omni (when provided) | | `description` | Field description from Omni (when provided) | ### Omni Measure Measures are aggregatable fields within Omni views or topics, typically used for numeric summarization in queries. #### Properties | Property | Description | | ------------- | ---------------------------------------------------------------- | | `name` | The measure name (label when provided, otherwise the field name) | | `type` | Always `omni_measure` | | `subtype` | Always `omni_measure` | | `label` | Display label from Omni (when provided) | | `description` | Field description from Omni (when provided) | ## Omni Data Analysis Layer ### Omni Workbooks In Omni, workbooks are the main organization unit for queries. A workbook can either have a dashboard or not. In Euno, workbooks are modeled as containers whose children are query tabs and, at most, one dashboard. #### Properties | Property | Description | | ---------------- | ------------------------------------------------------------ | | `name` | The workbook name | | `type` | Always `omni_workbook` | | `subtype` | Always `omni_workbook` | | `description` | The workbook description (when provided) | | `updated_at` | The timestamp when the workbook was last modified | | `created_by` | Display name of the creating user (from Omni owner metadata) | | `external_links` | Link to open the workbook in Omni | | `tags` | Omni labels, excluding verified/certification labels | | `meta` | Certification metadata when Omni verified labels are loaded | ### Omni Query Queries are individual tabs within an Omni workbook. Each query tab represents a pivot-table or SQL-based analysis. #### Properties | Property | Description | | ---------------- | ------------------------------ | | `name` | The query tab name | | `type` | Always `omni_query` | | `subtype` | Always `omni_query` | | `external_links` | Link to open the query in Omni | ### Omni Dashboard Dashboards are visualizations in Omni that display charts, tables, and KPIs. They are observed as children of workbooks when the workbook has a dashboard. #### Properties | Property | Description | | ---------------- | ----------------------------------------------------------- | | `name` | The dashboard name | | `type` | Always `omni_dashboard` | | `subtype` | Always `omni_dashboard` | | `description` | The dashboard description (when provided) | | `external_links` | Link to open the dashboard in Omni | | `tags` | Omni labels, excluding verified/certification labels | | `meta` | Certification metadata when Omni verified labels are loaded | {% hint style="warning" %} Dashboard lineage (dashboard → query) relies on an unstable Omni API endpoint (`/api/unstable/documents/{id}/export`). This endpoint may change or be removed by Omni in the future, which could temporarily affect dashboard lineage until an alternative is available. {% endhint %} ### Users (`user`) Users are discovered when "Observe users" is enabled in the Omni source configuration. | Property | Description | | --------------- | --------------------------------------------- | | `name` | User's email address (used as the identifier) | | `email_address` | User's email address | | `label` | User's display name from Omni | ### User Groups (`user_group`) User groups are discovered when "Observe groups" is enabled in the Omni source configuration. | Property | Description | | ----------- | --------------------------------------------- | | `name` | Display name of the group | | `native_id` | Group ID from Omni | | `subtype` | Always `omni` for groups discovered from Omni | ### Relationships #### Containment (`has parent` / `has child`) | Source type(s) | Relationship | Target type(s) | Notes | | -------------------------------- | ------------ | ------------------------- | ---------------------------------------------------- | | `omni_folder`, `omni_model` | has parent | `omni_account` | Includes structural **Hub** folder under the account | | `omni_folder`, `omni_workbook` | has parent | `omni_folder` | Organization and personal (restricted) folder trees | | `omni_view`, `omni_topic` | has parent | `omni_model` | Shared-model semantic resources | | `omni_view`, `omni_topic` | has parent | `omni_workbook` | Workbook-scoped semantic resources | | `omni_dimension`, `omni_measure` | has parent | `omni_view`, `omni_topic` | | | `omni_dimension` | has parent | `omni_query` | Query-level calculated fields | | `omni_query`, `omni_dashboard` | has parent | `omni_workbook` | A workbook has at most one dashboard child | #### Resource lineage (`has upstream` / `has downstream`) | Source type(s) | Relationship | Target type(s) | Notes | | ---------------- | ------------ | ------------------------- | ----------------------------------------------------------------------------------------------------------- | | `omni_model` | has upstream | `table` | When the model's warehouse tables are observed and Snowflake connection mapping is configured | | `omni_view` | has upstream | `table` | View SQL references warehouse tables | | `omni_workbook` | has upstream | `omni_model` | When linked to a backing shared model | | `omni_query` | has upstream | `omni_view`, `omni_topic` | Query tabs depend on semantic resources; warehouse tables are reached through the referenced views' lineage | | `omni_dashboard` | has upstream | `omni_query` | Dashboard tiles depend on query tabs | | `omni_topic` | has upstream | `omni_view` | Topics include joined/base views | Direct query-to-model lineage (`omni_query` → `omni_model`) is not observed. #### Column-level lineage (`has upstream_fields` / `has downstream_fields`) | Source type(s) | Relationship | Target type(s) | Notes | | -------------------------------- | -------------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------- | | `omni_dimension`, `omni_measure` | has upstream\_fields | `column`, `omni_dimension`, `omni_measure` | View fields point at warehouse columns when observed; topic-scoped fields point at their definition-view fields | | `omni_query` | has upstream\_fields | `omni_dimension`, `omni_measure` | Including query-level calculated fields | #### User and group relationships (`has group` / `has member`) | Source type(s) | Relationship | Target type(s) | Notes | | -------------- | ------------ | -------------------- | -------------------------------------------------------------- | | `omni_folder` | has group | `user`, `user_group` | From folder permission metadata | | `user_group` | has member | `user` | From SCIM group memberships when **Observe groups** is enabled | {% hint style="info" %} The Omni crawler does **not** currently observe model-level user or group memberships. {% endhint %} {% hint style="info" %} `is used by` relationships on `omni_workbook` and `omni_dashboard` come from the separate [Omni Usage integration](/sources/business-intelligence/omni-integration/omni-usage-setup.md), not from the Omni crawler itself. See [Omni Usage Data](/using-euno/usage-optimization/omni-usage-data.md). {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.euno.ai/sources/business-intelligence/omni-integration/omni-integration-discovered-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.