# Omni Integration Discovered Resources ## Omni Integration Discovered Resources ### Overview The Omni integration discovers the following resources: * Omni Account * Omni Folder * 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 integration, representing the top-level Omni organization. #### Properties | Property | Value | | -------- | --------------------------------- | | name | The organization or instance name | | type | always `omni_account` | | subtype | always `omni_account` | ### Omni Folder Folders are organizational containers in Omni for organizing workbooks. Folders can be nested to create a hierarchy. #### Properties | Property | Value | | ----------- | ------------------------------------------------------------------------------------- | | name | The folder name | | type | always `omni_folder` | | subtype | always `omni_folder` | | created\_by | The name of the user who created the folder | | 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 | Value | | ----------- | ---------------------------------------------- | | name | The model name | | type | always `omni_model` | | subtype | always `omni_model` | | created\_at | The timestamp when the model was created | | updated\_at | The timestamp when the model was last modified | ### Omni View Views are defined within Omni models and represent tables or logical structures with fields. They can reference other views or database tables. #### Properties | Property | Value | | -------- | ------------------ | | name | The view name | | type | always `omni_view` | | subtype | always `omni_view` | ### Omni Topic Topics are business-friendly abstractions within Omni models that group related views and fields for analysis. #### Properties | Property | Value | | -------- | ------------------- | | 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 | Value | | -------- | ----------------------- | | name | The dimension name | | type | always `omni_dimension` | | subtype | always `omni_dimension` | ### Omni Measure Measures are aggregatable fields within Omni views or topics, typically used for numeric summarization in queries. #### Properties | Property | Value | | -------- | --------------------- | | name | The measure name | | type | always `omni_measure` | | subtype | always `omni_measure` | ## 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, we model the workbooks as a container, whose children are either Omni Queries, and up to one Omni Dashboard. #### Properties | Property | Value | | ----------- | ------------------------------------------------- | | 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 | The name of the user who created the workbook | ### Omni Query Queries are individual tabs within an Omni workbook. Each query tab represents a pivot-table or SQL-based analysis. #### Properties | Property | Value | | -------- | ------------------- | | name | The query tab name | | type | always `omni_query` | | subtype | always `omni_query` | ### Omni Dashboard Dashboards are visualizations in Omni that display charts, tables, and KPIs. They may be standalone or part of a workbook. #### Properties | Property | Value | | ----------- | ----------------------------------------- | | name | The dashboard name | | type | always `omni_dashboard` | | subtype | always `omni_dashboard` | | description | The dashboard description (when provided) | {% 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 integration 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 integration configuration. | Property | Description | | ----------- | --------------------------------------------- | | `name` | Display name of the group | | `native_id` | Group ID from Omni | | `subtype` | Always `omni` for groups discovered from Omni | ### Relationships #### Container Relationships * **Omni Account → Folders**: Top-level folders are direct children of the account * **Omni Account → Models**: Models are direct children of the account * **Folders → Subfolders**: Folders can be nested within other folders * **Folders → Workbooks**: Workbooks & Dashboards belong to folders * **Omni Model → Views**: Views belong to models * **Omni Model → Topics**: Topics belong to models * **Omni View → Dimensions**: Dimensions belong to views * **Omni View → Measures**: Measures belong to views * **Omni Topic → Dimensions**: Dimensions can belong to topics * **Omni Topic → Measures**: Measures can belong to topics * **Omni Workbook → Omni Query**: Query tabs are children of workbooks * **Omni Workbook → Omni Dashboard**: Dashboards can be children of workbooks #### Lineage Relationships * **Omni Workbook → Omni Model**: Workbooks can be `downstream` of a backing shared Omni model * **Omni Query → Omni View or Omni Topic**: Queries are `downstream` of either an Omni View or an Omni Topic * **Omni Query → Omni Dimension or Omni Measure**: Queries can be `downstream` of the dimensions/measures they reference (including query-level calculated fields) * **Omni Query ↛ Omni Model (direct)**: Direct query-to-model lineage is not observed * **Omni Dashboard → Omni Query**: Dashboards are `downstream` of the Omni Queries that they include as tiles * **Omni Topic → Omni View**: Topics are `downstream` of the Omni Views that they include #### User and Group Relationships * **Omni Folder** -> **User**: Users can be observed as `members` of Omni folders via folder permissions. * **Omni Folder** -> **User Group**: User groups can be observed as `members` of Omni folders via folder permissions. * **User Group** -> **User**: Users can be observed as `members` of Omni user groups from SCIM group memberships. {% hint style="info" %} The Omni crawler does **not** currently observe model-level user/group memberships. {% endhint %} {% hint style="info" %} `used` 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. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.euno.ai/sources/business-intelligence/omni-integration/omni-integration-discovered-resources.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.