# General Translation Integrations: Configuring Storyblok
URL: https://generaltranslation.com/en-GB/docs/integrations/storyblok/guides/configuring-storyblok.mdx
---
title: Configuring Storyblok
description: "How to connect a Storyblok space to General Translation: this guide covers adding credentials and enabling translatable fields."
related:
  links:
    - /docs/integrations/storyblok/guides/translating-content
    - /docs/integrations/storyblok/guides/managing-translations
    - /docs/integrations/storyblok/guides/using-translated-content

---

Connect a Storyblok space to General Translation and prepare it so stories can be translated. Storyblok is a Dashboard-managed integration — you connect it with credentials, not an npm package.

## Before you begin [#before-start]

Connecting Storyblok requires:

* `project:write` permission on the Project. Without it, the **Connect** action is unavailable.
* A plan that includes the `project_integrations` feature. Without it, the Dashboard shows an upgrade prompt instead of the integrations catalogue, so you cannot connect a space.

## Configure languages in Storyblok [#configure-languages]

In Storyblok, open your space and go to **Settings > Languages**. Add each language you want as a translation target.

Target locales you can pick in the Dashboard come from this list, so configure them here first. A language is only offered when it also maps to a supported General Translation locale. See [Locales](/docs/integrations/storyblok/reference/locales).

## Create a personal access token [#create-token]

The integration authenticates to the Storyblok Management API with a personal access token.

In Storyblok, go to **My account > Personal access tokens** and create a token. Also make a note of your **Space ID** (**Settings > General**) and the **Region** your space is hosted in.

## Connect the space [#connect-space]

In the Dashboard, go to **Project > Integrations**, open the catalogue, find **Storyblok**, and click **Connect**. Provide:

* **Space ID** — the numeric space ID. A leading `#` is stripped automatically.
* **Region** — one of **EU**, **US**, **CA**, **AP**, or **CN**.
* **Personal access token** — your Management API token.

Credentials are stored on the Project. Once connected, you're taken to the integration's management page.

For the full list of connection settings and where they are stored, see [Connection settings](/docs/integrations/storyblok/reference/connection).

## Enable translatable fields [#enable-fields]

Storyblok only accepts a field-level translation when that field is marked `translatable: true` in its component schema. General Translation skips supported fields that are not translatable, so enable them before you translate.

You have two options.

a) **Auto-enable from the Dashboard.** On the management page, tick **Auto-enable supported fields** before you run **Sync and apply**. General Translation updates your Storyblok component schemas so supported `text`, `textarea`, `markdown`, `richtext`, and `table` fields become `translatable: true`. Fields already marked translatable are left unchanged, and the results summary reports how many fields and components were updated.

b) **Edit the schema in Storyblok.** In Storyblok's Block Library, open a component, select a field, and enable its translatable option. Repeat for each field you want translated.

*Note: Auto-enable writes to every component in the space, not just the ones in the stories you selected.*

## Manage or disconnect [#manage-disconnect]

Reopen the integration from **Project > Integrations** to run more translations. Connection credentials remain on the Project until the integration is removed. Disconnect it from the same Integrations area when you no longer want General Translation to access the space.
## Next steps

- /docs/integrations/storyblok/guides/translating-content
- /docs/integrations/storyblok/guides/managing-translations
- /docs/integrations/storyblok/guides/using-translated-content