Vapi is the Voice AI platform for developers.

Vapi AI

Hi Vapi team,
We added a GCS integration, but now it seems all call recordings are defaulting to GCS. We want to keep the integration for specific HIPAA calls, but route regular calls to Vapi’s default storage so we can still hear them in the dashboard.

Is there an org-level or dashboard setting to turn off recordingUseCustomStorageEnabled globally by default, so we only trigger GCS via assistantOverrides when needed?

Thanks!

<@1233640756548206643>

Hi,

Thank you for reaching out.

**Root Cause:** This behavior is expected. The field `recordingUseCustomStorageEnabled` defaults to `true`, so once a **GCS integration** is added, recordings are automatically routed to GCS unless explicitly disabled.

**Immediate Workaround (available now):**

You can set `recordingUseCustomStorageEnabled: false` on assistants where you want recordings to use Vapi’s default storage instead of GCS.

**Option 1 — Update the assistant via API**

```
{
  "artifactPlan": {
    "recordingUseCustomStorageEnabled": false
  }
}
```

**Option 2 — Override per call**

```
{
  "assistantOverrides": {
    "artifactPlan": {
      "recordingUseCustomStorageEnabled": false
    }
  }
}
```

For **HIPAA-related calls**, where you want recordings stored in GCS, you can simply leave the field **unset (default: true)** or explicitly set it to **true**.

Regarding an **organization-level default toggle**, this option is not currently available. If helpful, we can submit a **feature request** for an org-level setting such as `recordingUseCustomStorageEnabledDefault`.

Please let us know if you'd like us to file this request.

Best regards,
**Oshi Raghav**
Customer Support
Vapi