# Publish to travelers

After creating your guidebook, the final step is to publish it to your travelers. In GUIBO, this is done through the release system, which creates personalized access for your travelers.

## Understanding releases

A release is a traveler-specific instance of your guidebook that:

* Provides access to your content for a specific time period
* Contains personalized information tailored to a specific booking (like booked hotels,...)
* Offers multiple delivery channels (app, PDF roadbook, GPX files, push notifications)
* Is accessed through a unique download code

## Step 1: Prepare your guidebook for publishing

1. Navigate to your guidebook
2. Verify that all content is complete and accurate
3. Change the status from "In preparation" to "Approved"
   * Only guidebooks with "Approved" status can be published to travelers
   * This status change prevents incomplete content from reaching travelers

## Step 2: Access the release dashboard

1. From the main navigation, go to the **Release Dashboard**
2. This is your central hub for managing all traveler-specific releases

## Step 3: Create a new release

1. Click the orange **+** button to create a new release
2. Enter the required information:
   * **Set download code:** Unique identifier travelers will use to access their content in the app, typically matching your booking reference.
   * **Select Guidebook**: Select which approved guidebook to publish for this specific booking.
   * **Set traveller's language**: Define the language for the PDF roadbook/booklet and release page interface.
   * **Set number of smartphone devices:** Specify how many devices can use this download code (usually matches number of travelers).
   * **Define release period:** Set the timeframe during which travelers can access the content.
   * **Define Seller (Optional):** Select an agency to rebrand the travel docs to the agency's look and feel.
3. Save the release

## Step 4: Personalize the release (optional)

If needed, you can personalize the release with booking-specific information:

1. Select the release on the left side.
2. Choose from the following options to personalize your release:
   1. **Documents**\
      Add any PDF document to the release. These are then available via the release page and via the tour guide app.
   2. **Accommodation**\
      Add specific hotels to this release. After adding the hotel you can specify arrival and departure dates.
   3. **Add content**\
      Click Actions ➔ Add content to add any POI, route or text page to this specific release.
   4. **Modify guidebook content**\
      Click Actions ➔ Modify guibdeook content to edit any content for this specific release.

## Step 5: Preview and share with travelers

1. Click the **"Traveller's page" link** to preview the release page as single point of access for travelers
2. **Share this link** (e.g. via E-Mail) with your travelers to provide all travel docs with a single link

## Next Steps

You now have an understanding about the most important GUIBO. Now you can:

* Create more comprehensive content
* Build additional guidebooks
* Explore advanced features like [B2B Network](/publishing/b2b-network.md), [External Content Integration](/content-management/integrate-external-content.md) or our [Developer Overview](/developers/overview.md).

***

**Tip**: Test your releases before sending them to travelers. Download the GUIBO (or White Lapel) App on your test device and open the release using the traveler’s download code to experience the guidebook exactly as your travelers will see it.

You can use the customer’s release code on a test device without affecting the release:

* The download does not count toward the maximum number of devices
* No traveler fee will be charged for the test download


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.guibo.travel/get-started/getting-started/publish-to-travelers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.