> ## 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.

# Overview

> Invite a single customer to a published Hosted journey from the GBG Go platform, without writing code or calling the API.

No-code is the delivery method that lets you invite a single customer to a published Hosted journey from the GBG Go platform. You send them a verification link, they complete the journey, and you review the result. You write no code and call no API.

To send your first invite, see the [No-code quickstart](/docs/go-v2/get-started/quickstart/quickstart-invite-a-customer).

## What No-code does

An invite opens the same platform-hosted pages that a Low-code journey uses. Only the way the journey starts differs, so your journey configuration, modules, and outcomes behave identically.

Your organisation's branding therefore applies to a No-code journey exactly as it does to a Low-code one. Branding covers the logo, colours, and theme on the hosted screens, and you configure it on the journey rather than per invite. To learn more, see [Branding](/docs/go-v2/platform/branding).

No-code suits customer-facing teams who verify one customer on request, such as support agents onboarding a new client or compliance staff running an ad hoc check. It also suits organisations evaluating GBG Go who want to test a journey end-to-end before building an interface.

## How No-code works

You build and publish the journey once, and then send an invite for each customer you want to verify.

<Steps>
  <Step title="Create and publish a Hosted journey">
    Build the journey in the Journey builder with the modules your check needs, and then publish it to an environment. Select **Preview** while you test, and **Production** when you go live.
  </Step>

  <Step title="Invite your customer">
    Open the journey, click the **Actions** list, and then click **Invite a customer**. Enter an email address, a mobile number, or both.
  </Step>

  <Step title="The platform sends the link">
    The GBG Go platform sends your customer a verification link. An invite is valid for one customer, and by default it expires after seven days.
  </Step>

  <Step title="Your customer completes the journey">
    Your customer opens the link and submits their details on each hosted screen. The platform then processes the data through the modules in your journey.
  </Step>

  <Step title="Review the outcome">
    Review the result and the decision in [Investigation](/docs/go-v2/platform/investigate/overview) once your customer completes the journey.
  </Step>
</Steps>

The **Invite a customer** action is unavailable when the journey isn't published, when the journey collects information before it starts, or when your organisation has no licence and credentials for the User Invite module. See [When the invite action is unavailable](/docs/go-v2/get-started/quickstart/quickstart-invite-a-customer#when-the-invite-action-is-unavailable).

## Check which modules work with No-code

An invite carries no data, so every input a module requires must be collected from your customer on a hosted screen. Inputs marked **Pre-filled** are supplied through the API at journey start, which No-code can't do.

To check a module before you invite a customer:

1. Open your journey in the Journey builder.
2. Click the module you want to check.
3. Select the **Data** tab.
4. Review the **Source** column of the **Inputs** table. Confirm that every required input names an interaction group rather than **Pre-filled**.

If an input shows **Pre-filled**, then add it back to an interaction group. To learn more, see [View interaction groups](/docs/go-v2/low-code-builder/interactions/explore-interactions).

Two other conditions affect whether a module is available to you:

* The module and variant must be enabled in your contract. Modules and variants marked with an orange warning icon require activation by the GBG team.
* Some module variants aren't supported by hosted screens yet. Any input without a hosted card moves to pre-fill.

To compare modules and their inputs, see [Modules](/docs/go-v2/platform/modules/overview).

## Guides

The following guides show you how to invite a customer to a journey built for a specific verification task:

* [PEPs and Sanctions screening](/docs/go-v2/low-code-builder/no-code/guides/peps-and-sanctions-screening)
* [Identity document verification](/docs/go-v2/low-code-builder/no-code/guides/identity-document-verification)
* [Biometric verification](/docs/go-v2/low-code-builder/no-code/guides/biometric-verification)
* [Collection of supporting documents](/docs/go-v2/low-code-builder/no-code/guides/supporting-documents)
* [UK data sources](/docs/go-v2/low-code-builder/no-code/guides/uk-data-sources)