> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/sigma-integration/metadata-extracted.md).

# Sigma Metadata Extracted

### What does Secoda extract from Sigma?

{% hint style="info" %}
NOTE: Preview of Sigma resources is available in Secoda if permissions are granted.
{% endhint %}

* Workspaces
  * Workspace Name
* Workbooks
  * Workbook Name
  * Workbook Updated At
  * Workbook Owners
  * Workbook URL
  * Workbook Badges
* Pages
  * Page Name
  * Page URL
* Elements
  * Element Name
  * Element URL
* Dataset
  * Dataset Name
  * Dataset
* Queries
* Lineage
  * Sigma Element <-> Sigma Workbook
  * Sigma Page <-> Sigma Workbook
  * Sigma Element <-> Sigma Page
  * Sigma Workbook or Elements <-> Tables from other sources
    * Note: These lineage relationships will pass through the Query to the Workbooks and Elements that that Query connects to.

{% hint style="info" %}
To determine lineage from Sigma, we parse the queries that we extract from Sigma using the APIs.
{% 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.secoda.co/integrations/data-visualization-tools/sigma-integration/metadata-extracted.md?ask=<question>&goal=<endgoal>
```

`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.