> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/connector-onboarding-guide/sigma.md).

# Sigma

This guide sets up the Sigma connector using **OAuth client credentials** (Client ID and Client Secret), Sigma's recommended method for application-level access to the Sigma REST API. Datalogz reads metadata only; it never accesses the data inside your workbooks.

You will complete four steps: confirm Admin access and API availability, identify your API base URL, generate client credentials, and create the connector in Datalogz Control Tower.

### Step 1: Confirm Admin access and API availability

1. You must be a member of the **Admin** account type in Sigma to generate API client credentials.
2. Your Sigma plan must include API access. If you are unsure, ask your Sigma account team to confirm the API is enabled for your organization.

{% hint style="info" %}
API credentials inherit the permissions of the user account you assign them to. We recommend creating a dedicated service account user in Sigma, rather than tying credentials to an individual, so access is not disrupted if that person leaves.
{% endhint %}

### Step 2: Identify your Sigma API base URL

Sigma hosts customers across multiple clouds and regions, and the correct API base URL depends on where your organization is provisioned.

1. Log in to Sigma and go to **Administration > Developer Access**.
2. Copy the **API base URL**.

Common examples:

* AWS US (West): <https://aws-api.sigmacomputing.com>
* AWS US (East): <https://api.us-a.aws.sigmacomputing.com>
* GCP: <https://api.sigmacomputing.com>
* Azure: <https://api.us-a.azure.sigmacomputing.com>

{% hint style="warning" %}
Using the wrong host causes authentication to fail even with valid credentials.
{% endhint %}

### Step 3: Generate API client credentials

1. In Sigma, go to **Administration > Developer Access**.
2. Click **Create New**.
3. Select **REST API** as the scope.
4. Enter a **Name** (for example, Datalogz Control Tower) and an optional **Description**.
5. Select the **Owner** for the credentials. We recommend the dedicated service account from Step 1.
6. Click **Create** and copy the **Client ID** and **Client Secret**. The secret is only displayed once.

### Step 4: Create the connector in Control Tower

1. Sign in to Datalogz Control Tower and go to **Settings > BI Connectors**.
2. Click **New Connector** and select **Sigma**.
3. Enter the **API base URL**, **Client ID**, and **Client Secret**, then click **Connect**.
4. Enter a **Connector Name** and select the snapshot frequency (for example Daily or Weekly).
5. Click **Next**, then **Confirm and Finish**.

For questions or help with this setup, contact <support@datalogz.io>.


---

# 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.datalogz.io/guides/organizational-setup/connector-onboarding-guide/sigma.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.