> 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/sigma-integration/sigma-integration-discovered-resources.md). # Sigma Integration Discovered Resources ## Overview The Sigma integration discovers the following resources: * Sigma Account * Sigma Folder (Workspaces and Folders) * Sigma Data Model * Sigma Workbook * Sigma Workbook Element * Sigma Data Model Element * Data Warehouse Tables (referenced by workbooks) ## Sigma Account A single resource of type `sigma_account` is observed for each configured Sigma integration, representing the top-level Sigma organization. ### Properties | Property | Value | | --------------- | -------------------------------------------------------------------------------------------- | | name | The organization name, or `"Sigma Account ({organization_id})"` if the name is not available | | type | always `sigma_account` | | subtype | always `sigma_account` | | native\_id | The Sigma organization ID | | container\_type | always `pure_container` | | external\_links | List of links to open this resource in Sigma. See [External links](#external-links) below. | ### External links Many Sigma resources expose an **external\_links** property so API and UI consumers can offer “open in Sigma”–style actions. This property is a list of link objects. Each object has: | Field | Type | Description | | ----- | ------ | ----------------------------------------------------------------------- | | label | string | Display label for the link (e.g. `"Open in Sigma"`, `"Sigma Account"`). | | url | string | URL that opens the resource in the Sigma web application. | **Where it appears:** * **sigma\_account**: Typically one link with label `"Sigma Account"` pointing to the organization in Sigma (e.g. `https://app.sigmacomputing.com/{organization_name}`). * **sigma\_folder**: Link with label `"Open in Sigma"` to the folder in the Sigma UI (when a URL is available). * **sigma\_data\_model**: Link with label `"Open in Sigma"` to the data model. * **sigma\_workbook**: Link with label `"Open in Sigma"` to the workbook. * **sigma\_workbook\_element**: Link with label `"Open in Sigma"` to the element within its workbook. * **sigma\_data\_model\_element**: Link with label `"Open in Sigma"` to the element within its workbook. If the Sigma API does not provide a URL for the resource, **external\_links** may be an empty list. ## Sigma Folders and workspaces Folders and workspaces are organizational containers in Sigma. Workspaces are top-level folders, while folders can be nested within workspaces or other folders. ### Properties | Property | Value | | --------------- | ------------------------------------------------------------------------- | | name | The folder or workspace name | | type | always `sigma_folder` | | subtype | `sigma_folder` or `sigma_workspace` | | native\_id | The unique folder/workspace ID in Sigma | | created\_at | The timestamp when the folder was created | | updated\_at | The timestamp when the folder was last modified | | created\_by | The email address of the user who created the folder | | updated\_by | The email address of the user who last updated the folder | | owner | The owner of the folder | | external\_links | Links to open the folder in Sigma. See [External links](#external-links). | ## Sigma Data Model Data models are reusable semantic layers in Sigma that provide business-friendly views of data warehouse tables. ### Properties | Property | Value | | --------------- | ----------------------------------------------------------------------------- | | name | The data model name | | type | always `sigma_data_model` | | subtype | always `sigma_data_model` | | native\_id | The unique data model ID in Sigma | | created\_at | The timestamp when the data model was created | | updated\_at | The timestamp when the data model was last modified | | created\_by | The email address of the user who created the data model | | updated\_by | The email address of the user who last updated the data model | | owner | The owner of the data model | | tags | List of version tag names associated with the data model | | external\_links | Links to open the data model in Sigma. See [External links](#external-links). | ## Sigma Workbook Workbooks are analytics documents in Sigma containing visualizations, tables, and analyses. ### Properties | Property | Value | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | name | The workbook name | | type | always `sigma_workbook` | | subtype | always `sigma_workbook` | | native\_id | The unique workbook ID in Sigma | | description | The workbook description, if provided | | created\_at | The timestamp when the workbook was created | | updated\_at | The timestamp when the workbook was last modified | | created\_by | The email address of the user who created the workbook | | updated\_by | The email address of the user who last updated the workbook | | owner | The owner of the workbook | | tags | List of version tag names associated with the workbook | | external\_links | Links to open the workbook in Sigma. See [External links](#external-links). | | total\_read\_queries\_14/30/60d | When integrated with a supported warehouse, the total read queries for the timeframe are propagated to the resource. | | total\_read\_cost\_14/30/60d | When integrated with Snowflake warehouse, the total read cost for the timeframe propagated to the resource. | | total\_read\_credits\_14/30/60d | When integrated with Snowflake, the total read credits for the timeframe propagated to the resource. | ## Sigma Element Elements are individual components within a Sigma workbook or a data model, such as tables, visualizations, or calculations. Each element may contain SQL queries and can reference other elements or data warehouse tables. ### Properties | Property | Value | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | name | The element name | | type | `sigma_workbook_element` or `sigma_data_model_element` | | subtype | `sigma_workbook_element` or `sigma_data_model_element` | | native\_id |

The element ID in the format {workbook\_uri}/{element\_id}
or {semantic\_model\_uri}/{element\_id}

| | external\_links | Links to open the element in Sigma. See [External links](#external-links). | | total\_read\_queries\_14/30/60d | When integrated with a supported warehouse, the total read queries for the timeframe are propagated to the resource. | | total\_read\_cost\_14/30/60d | When integrated with Snowflake warehouse, the total read cost for the timeframe propagated to the resource. | | total\_read\_credits\_14/30/60d | When integrated with Snowflake, the total read credits for the timeframe propagated to the resource. | ## Data Warehouse Tables When a Sigma workbook references a data warehouse table, Euno automatically observes that table if it hasn't been discovered yet. ### Properties | Property | Value | | -------------------- | ----------------------- | | name | The table name | | type | always `table` | | subtype | always `table` | | database\_technology | The data warehouse type | | database | The database name | | schema | The schema name | ## Relationships ### Container Relationships * **Sigma Account → Workspaces**: Workspaces are top-level folders under the account * **Workspaces → Folders**: Folders can be nested within workspaces * **Folders → Subfolders**: Folders can contain other folders * **Folders → Workbooks**: Workbooks belong to folders * **Sigma Account → Data Models**: Data models are direct children of the account * **Workbooks → Workbook Elements**: Workbook Elements belong to workbooks * **Data Model → Data Model Elements**: Data Model Elements belong to workbooks ### Lineage Relationships | Source type(s) | Relationship | Target type(s) | Notes | | ------------------------ | ------------ | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | `sigma_workbook` | has upstream | `sigma_workbook_element` | Workbook depends on its elements | | `sigma_workbook_element` | has upstream | `table`, `sigma_workbook_element`, `sigma_data_model_element` | Root elements reference warehouse tables; non-root reference other elements or data model elements | ### Column level lineage | Source type(s) | Relationship | Target type(s) | Notes | | -------------------------- | -------------------- | -------------- | ------------------------ | | `sigma_workbook_element` | has upstream\_fields | `column` | Root workbook elements | | `sigma_data_model_element` | has upstream\_fields | `column` | Root data model elements | --- # 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/sigma-integration/sigma-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.