> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.sigmacomputing.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.sigmacomputing.com/_mcp/server.

# Manage API credential and connection access

> View, request, and grant access to API credentials and connectors in Sigma, including how to approve or deny access requests.

API connectors enable you to configure a [**Call API** action](/docs/create-actions-that-call-api-endpoints) in a workbook. After you [configure API connectors and credentials](/docs/configure-api-credentials-and-connectors-in-sigma), you can manage user and team access to them. This document covers the [permissions required for several common use cases involving API actions](#api-connector-and-credential-permissions-matrix), as well as how to:

* [View](#view-organization-api-connectors) and [request access to](#request-access-to-an-api-connector) API connectors
* [Approve or deny access requests](#approve-or-deny-an-api-connector-access-request)
* [Grant access to API connectors](#grant-access-to-a-connector) and [API credentials](#grant-access-to-api-credentials)

## User requirements

* To view all API connectors in an organization, you must be assigned an account type with at least one of the **Manage API connectors**, **Create API actions**, or **Trigger API actions** permissions enabled.
* To request access to an API connector, you must be assigned an account type with at least one of the **Manage API connectors**, **Create API actions**, or **Trigger API actions** permissions enabled.
* To approve or deny access requests for an API connector, you must be the owner of the connector, an admin, or a user with the **Manage API connectors** account type permission enabled and **Can edit** access to that specific API connector.
* To manage API connector and credential access, you must be an admin, the owner of the connector or credential, or a user with the **Manage API connectors** account type permission enabled and **Can edit** access to that specific API connector/credential.

## About granting access to API connectors

There are several ways users can access API connectors:

* When [viewing API connectors](#view-organization-api-connectors) in their organization, they can [request access](#request-access-to-an-api-connector) to a specific API connector. Their request is then [approved or denied](#approve-or-deny-an-api-connector-access-request) by a user with the appropriate [permissions](#system-and-user-requirements).

* Admins or users with [appropriate permissions](#user-requirements) can edit the API connector directly to provide access without a request being sent.

Admins or users with [appropriate permissions](#user-requirements) enabled can also edit [API credentials](#grant-access-to-api-credentials) to provide users and teams with access to the credential.

## API connector and credential access matrix

The following table details the minimum document access and account, connector, and credential permissions required for several common use cases involving API actions. For example, to trigger an action sequence with a **Call API** action, a user must have **Can view** access to the workbook with the action sequence, an account type with the **Trigger API actions** permission enabled, and **Can use** access to the connector.

<table>
  <thead>
    <tr>
      <th>
        Use case
      </th>

      <th class="alt-bg-1">
        Document permission
      </th>

      <th class="alt-bg-1">
        Account permission
      </th>

      <th class="alt-bg-1">
        Connector permission
      </th>

      <th class="alt-bg-1">
        Credential permission
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Trigger an action sequence with a Call API action
      </td>

      <td>
        Can view
      </td>

      <td>
        Trigger API actions
      </td>

      <td>
        Can use
      </td>

      <td>
        None
      </td>
    </tr>

    <tr>
      <td>
        Edit a Call API action
      </td>

      <td>
        Can explore
      </td>

      <td>
        Create API actions
      </td>

      <td>
        Can use
      </td>

      <td>
        None
      </td>
    </tr>

    <tr>
      <td>
        Create a Call API action
      </td>

      <td>
        Can explore
      </td>

      <td>
        Create API actions
      </td>

      <td>
        Can use
      </td>

      <td>
        None
      </td>
    </tr>

    <tr>
      <td>
        View details of an API credential
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        None
      </td>

      <td>
        Can use
      </td>
    </tr>

    <tr>
      <td>
        View details of an API connector
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        Can use
      </td>

      <td>
        None
      </td>
    </tr>

    <tr>
      <td>
        Edit an API connector
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        Can edit
      </td>

      <td>
        Can use

        1
      </td>
    </tr>

    <tr>
      <td>
        Edit an API credential
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        None
      </td>

      <td>
        Can edit
      </td>
    </tr>

    <tr>
      <td>
        Create a new API connector
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        None
      </td>

      <td>
        Can use

        1
      </td>
    </tr>

    <tr>
      <td>
        Create a new API credential
      </td>

      <td>
        None
      </td>

      <td>
        Manage API connectors
      </td>

      <td>
        None
      </td>

      <td>
        None
      </td>
    </tr>
  </tbody>
</table>

1 To manage the use of the credential in a connector, **Can use** access to the credential is required. However, **Can use** access to the credential is not required to edit other details of a connector.

## View organization API connectors

To view all API connectors in your organization:

1. From the Sigma header, select your user avatar to open the user menu, then select **Profile**.
2. From the side panel, select **API connectors**. A list of all API connectors you have access to is displayed. Only the **Name** and **Description** of each connector are displayed.
3. (Optional) To see API connectors you do not have access to, clear the **Can use** filter in the search bar, and select the **No access** filter instead. Any connectors you do not have access to appear in gray text. You can [request access to API connectors](#request-access-to-api-connectors).

Admins can access all listed API connectors.

4. (Optional) For users with the **Manage API connectors** permission enabled, select **Manage API connectors** to view and edit full API connector details.

## Request access to an API connector

To request access to an API connector:

1. From the Sigma header, select your user avatar to open the user menu, then select **Profile**.
2. From the side panel, select **API connectors**.
3. Select ![](https://sigma-docs-screenshots.s3.us-west-2.amazonaws.com/Icons/filter.svg) **Filters** and select the **No access** filter to view API connectors you do not have access to.
4. On your desired API connector, select ![](https://sigma-docs-screenshots.s3.us-west-2.amazonaws.com/Icons/more.svg) **More**, then select **Request access**. When your request is sent, a confirmation message is shown.

An admin or the owner of the API connector can [approve or deny the request](#approve-or-deny-an-api-connector-access-request).

## Approve or deny an API connector access request

There are several ways to approve or deny an API connector access request:

* (*For the owner of the API connector only*) [From **Notifications** in Sigma](#from-notifications-in-sigma)
* (*For the owner of the API connector only*) [From an email notification](#from-an-email-notification)
* [From the Administration portal](#from-the-administration-portal)

### From notifications in Sigma

If you are the owner of an API connector and a user requests access to that connector, you receive a notification in Sigma. To approve or deny the request:

1. From the Sigma header, select **Notifications**.
2. On the access request, select **Approve** or **Deny**. Approving an access request grants the user **Can use** access to the connector. To grant a different level of access, approve the access request from the [Administration portal](#from-the-administration-portal) or from the [email notification](#from-an-email-notification).

### From an email notification

If you are the owner of an API connector and a user requests access to that connector, you receive an email notifying you of the request. To approve or deny the request:

* From the email, select **Respond to request**. The **Grant access** modal opens in Sigma:
  * To approve the request, from the dropdown, select your desired access level for the user, then select **Approve**.
  * To deny the request, select **Deny**.

### From the Administration portal

Even if you are not the owner of a specific API connector, organization admins or users with **Can edit** access to that specific API connector can approve or deny access requests from the Administration portal:

1. Go to **Administration** > **API connectors**.
2. Select the **Connectors** tab.
3. Select the connector you want to approve or deny an access request for.
4. Select **+ Grant access**.
5. In the **Grant access to** modal, you can view and respond to pending access requests:
   * To approve a request, from the dropdown, select your desired access level for the user, then select **Approve**.
   * To deny a request, select **Deny**.

## Grant access to an API connector

You can grant access to an API connector without users having to request access by editing the API connector access in the Administration portal.

To grant users and teams access to an API connector:

1. Go to **Administration** > **API connectors**:
   1. From the Sigma header, select your user avatar to open the user menu.
   2. Select **Administration** to open the **Administration** portal.
   3. From the side panel, select **API connectors**.
2. Select the **Connectors** tab.
3. Select the connector you want to manage.
4. Select **+ Grant access**.
5. In the **Grant access to** modal, search for and select the users or teams to grant access to.
6. Under **Access**, select the access to grant to each user or team.
7. (Optional) To notify users when granting access, select the **Send email** checkbox.
8. (Optional) If you checked the **Send email** checkbox, enter a message in the **Add a message** field.
9. (Optional) To provide users with **Can edit** permission on that API connector with automatic **Can use** access on the associated API credential, turn on the **Grant 'Can edit' users to have 'Can use' access to credentials** toggle.
10. Select **Share**.

## Grant access to API credentials

To grant users and teams access to an API credential:

1. Go to **Administration** > **API connectors**:
   1. From the Sigma header, select your user avatar to open the user menu.
   2. Select **Administration** to open the **Administration** portal.
   3. From the side panel, select **API connectors**.
2. Select the **Credentials** tab.
3. Select the credential you want to manage.
4. Select **+ Grant access**.
5. In the **Grant access to** modal, search for and select the users or teams to grant access to.
6. Under **Access**, select the access to grant to each user or team.
7. (Optional) To notify users when granting access, select the **Send email** checkbox.
8. (Optional) If you checked the **Send email** checkbox, enter a message in the **Add a message** field.
9. Click **Share**.

## Related resources

* [Configure API credentials and connectors in Sigma](/docs/configure-api-credentials-and-connectors-in-sigma)
* [Configure mutual transport layer security (mTLS) for API connectors in Sigma](/docs/configure-mutual-transport-layer-security-for-api-connectors-in-sigma)
* [Create actions that call API endpoints](/docs/create-actions-that-call-api-endpoints)