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

# Publish journey

> Publish your GBG GO journey to Preview for testing or to Production for live customer use.

export const VersionWarningBanner = () => {
  const [latestUrl, setLatestUrl] = useState(null);
  useEffect(() => {
    if (typeof window === "undefined") return;
    const {pathname, hash, search} = window.location;
    if (!pathname.includes("/go-v1/")) return;
    setLatestUrl(`${pathname.replace("/go-v1/", "/go-v2/")}${search}${hash}`);
  }, []);
  if (!latestUrl) return null;
  return <div className="not-prose my-6 rounded-xl border border-amber-500/30 bg-amber-500/10 px-4 py-3 text-sm text-gray-800 dark:text-gray-100">
      ⚠️ You are viewing the <strong>GBG GO v1</strong> documentation.
      <a href={latestUrl} className="ml-2 font-medium underline text-amber-700 dark:text-amber-400 hover:text-amber-800 dark:hover:text-amber-300">
        View the latest version (v2) →
      </a>
    </div>;
};

<VersionWarningBanner />

Once your journey is fully configured, the next step is to publish it. Publishing a journey makes it available for use in different environments.

GBG GO allows you to publish journeys in two environments:

| **Option**     | **Purpose**                                                                                     |
| -------------- | ----------------------------------------------------------------------------------------------- |
| **Preview**    | Allows testing before going live. Generates a schema for API integration.                       |
| **Production** | Deploys the journey live for real users. Once published, the journey cannot be edited directly. |

Publishing to Preview allows the development team to test API calls and verify that the journey is functioning as expected.

## Publish to Preview

Publishing to preview allows you to test your journey before making it live.

To publish to Preview:

1. Click **Publish to Preview** in the journey editor.
2. A confirmation message appears: *Delivery deployed successfully*.
3. Click on **Dashboard** to see:
   * Environment (Preview)
   * Version number
   * Resource ID
   * Last published date
   * Schema
4. The schema for your journey is automatically generated.

### Understanding the schema

The schema defines what information is required for the modules in your journey.

* If a new module is added, new fields may be included in the schema.
* If a field is already used, it will be shared between modules, for example, an address field used in multiple verification steps.
* Developers can copy the schema and use it for API integration with Postman or other tools.

<Warning>
  Ensure your journey is fully tested in Preview before publishing to
  Production. Any changes will require creating a new version.
</Warning>

## Publish to Production

Once testing is complete, you can publish the journey to **Production**. This makes it available for real users.

To publish to Production:

1. Click the **Actions** list in the Dashboard.
2. Select **Publish to Production** from the menu.
3. Confirm the action in the dialog box by selecting the checkbox.
4. Click **Publish to production**.

The journey is now live. You can now use the Resource ID and schema for API integration in your production environment.

## Important considerations:

* Once a journey is published to Production, it cannot be edited directly.
* If changes are needed, you must **create a new version** of the journey.
* You will have two Resource IDs (one for **Preview** and one for **Production**).

## Example use case

A business user creates a journey and publishes it to Preview:

* The developer retrieves the schema, integrates it with their system, and runs tests.
* After successful API testing, the business user publishes the journey to Production.
* The journey is now live and can be used by real customers.

## What’s next?

After publishing, the journey is ready for integration with your system.

* **[API integration guides](/docs/go-v1/developer-integration/overview)** – Learn how to use the schema for API calls.