> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Cloud Storage

## Overview

Stigg's integration with Google Cloud Storage (GCS) allows you to export your product catalog, customer, and subscription data to a GCS bucket as structured files — useful for data lake pipelines, custom ETL workflows, or archival.

<Note>
  Stigg's native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg's pricing for more details.
</Note>

<Card title="View the full entity schema" icon="sitemap" href="./schema">
  See every table and column exported to your destination, organized by entity group.
</Card>

## Setting up the integration

### Prerequisites

* A Google Cloud project with permission to create service accounts and edit IAM policies.
* The service account principal shown in the Stigg connect form (in the form `some-name@some-project.iam.gserviceaccount.com`) — you'll grant it access below.

<Note>
  By default, GCS authentication uses role-based access via service account impersonation, so no key file or long-lived secret leaves your project. If your organization's policy rules this out, see the HMAC alternative in the last step below.
</Note>

<Steps>
  <Step title="Create a service account and grant access">
    In the [GCP console](https://console.cloud.google.com/iam-admin/serviceaccounts) under **IAM & Admin → Service Accounts**, create a service account and give it a recognizable name. Skip granting it any project-level roles at this stage. Note its email address — you'll need it later.

    Open the service account's **Permissions** tab, locate the principal shown in the Stigg connect form, click the edit (pencil) icon next to it, add the **Service Account Token Creator** role, and save.
  </Step>

  <Step title="Create the GCS bucket">
    In [Cloud Storage](https://console.cloud.google.com/storage/browser), click **Create**, enter a bucket name, and select a region. Enable **Enforce public access prevention**, then complete the remaining defaults and create the bucket.

    On the bucket's **Permissions** tab, grant the service account created in the previous step the **Storage Legacy Bucket Writer** role.
  </Step>

  <Step title="Connect Stigg with GCS">
    In [Stigg](https://app.stigg.io/), navigate to **Integrations > Apps > Google Cloud Storage**.

    Enter the following information in the connection form:

    | Field                 | Description                                                  |
    | --------------------- | ------------------------------------------------------------ |
    | Bucket name           | The name of your GCS bucket                                  |
    | Folder name           | The folder path within the bucket where data will be written |
    | Service account email | The email address of the service account created above       |

    Click **Test & connect**.

    <Note>
      To use an HMAC access key instead of impersonation, go to **Cloud Storage → Settings → Interoperability**, click **Create a key for a Service Account**, select the service account created above, and click **Create key**. Note the generated **Access key** and **Secret** — you'll enter these in place of impersonation in the connect form.
    </Note>
  </Step>

  <Step title="Select entities to export">
    After entering your connection details, expand the **Entities to export** section to choose which entity groups to include in the sync. All groups are selected by default.

    See [Exported entities](./overview#exported-entities) for a description of each group.
  </Step>
</Steps>


## Related topics

- [Exported entities](/documentation/importing-and-exporting-data/export/overview.md#exported-entities)
- [Sync process, schedule, manual sync, and sync history](/documentation/importing-and-exporting-data/export/overview.md#sync-process)