> ## 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.
# PEPs and Sanctions screening
> Invite a customer to a No-code journey that screens them against PEPs and sanctions lists.
This guide shows you how to screen a single customer against politically exposed persons and sanctions lists. You build a Hosted journey, invite one customer by email or text message, and then review the screening result in Investigation. You **don't** write any code or call the API.
By the end of this guide, you can see whether your customer matched a politically exposed person (PEP), sanctions, or adverse media record. You can also see the decision that the GBG Go platform reached.
The **Invite a customer** action is only available for published Hosted journeys. If your journey collects information before it starts, then the action is unavailable. See [When the invite action is unavailable](/docs/go-v2/get-started/quickstart/quickstart-invite-a-customer#when-the-invite-action-is-unavailable).
## Before you begin
Ensure you have the following:
* A GBG Go platform account with a customer admin role. This role lets you review the result in Investigation. If you don't have this role, then contact your GBG account manager.
* The PEPs and Sanctions module enabled in your contract.
* A licence and credentials for the User Invite module set up for your organisation.
* An email address or mobile number that you can receive the invite on, so that you can complete the journey as your customer.
## Step 1: Create a Hosted journey
1. Click on the **Create a new journey** list.
2. Select **API + hosted (latest)**. This opens the Journey builder, allowing you to design Hosted journey workflows.
3. Click the edit icon on the journey name at the top of the editor.
4. Enter a meaningful name, for example, "PEPs and Sanctions Screening - New Customers."
5. Click outside the name field to save it.
## Step 2: Select a screening variant
You select a variant as part of adding the module. The Standard variants screen a customer in a single check and return candidate scores for PEP and sanctions matches.
1. Go to **Browse and add modules** in the right sidebar.
2. Use the search bar to find **PEPs and Sanctions**.
3. Click the module. This opens the module configuration panel, which lists the available variants.
4. Select one of the following variants:
| Variant | What it does |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **PEPs and Sanctions Standard with Adverse Media** | Screens against PEP databases, sanctions watchlists, and adverse media. Recommended for this guide. |
| **PEPs and Sanctions Standard** | Screens against PEP databases and sanctions watchlists. |
| **PEPs and Sanctions Standard OGM Push** | Registers the customer for Ongoing Monitoring. It runs no screening of its own. |
This guide uses **PEPs and Sanctions Standard with Adverse Media**. It covers the widest set of lists, so it gives you the most complete result to review in Investigation.
Every PEPs and Sanctions variant requires the customer's full name. Date of birth, gender, and current address are optional, but they improve match accuracy and reduce false positives.
To compare the variants in detail, see [PEPs and Sanctions](/docs/go-v2/platform/modules/compliance-screening/peps-and-sanctions).
**PEPs and Sanctions Standard OGM Push** performs no PEP, sanctions, or adverse media check. Add it after a screening variant to enrol customers for continuous re-screening. Used on its own, it returns no screening result.
Modules and variants marked with an orange warning icon require activation by the GBG team. If the variant you need is marked, then contact your account manager to enable it for your organisation.
## Step 3: Add the module to your journey
1. Click **Add to journey** to insert the module into the flow.
2. Click the module inside the Journey builder to open its configuration panel.
3. Click **Close** to apply your configuration.
The configuration panel is where you tailor the module to your own use case. It gives you the following options:
| Option | What you can do |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Settings** | Select the datasets to screen against. Choose PEP, sanctions, adverse media, or any combination. For example, select only the adverse media dataset to run an adverse media check. |
| **Configure outcomes** | Define what happens for each screening result, and route customers accordingly. You do this in [Step 4](#optional-step-4-configure-the-outcomes). |
For the purpose of this guide, you don't need to change any settings. The variant you selected in [Step 2](#step-2-select-a-screening-variant) screens against all three datasets by default. This gives you the most complete result to review at the end.
To learn more about module settings, see [How to configure module settings in Go](/docs/go-v2/guides/product-guides/configure-module-settings).
## (Optional) Step 4: Configure the outcomes
The outcomes decide what happens when the screening returns a match and when it returns no match.
The module arrives pre-configured with the following default outcomes, so you can skip this step and go to [Step 5](#step-5-publish-the-journey):
| Outcome | Condition | Description |
| ---------- | --------------------------------- | -------------------------------------------------------------------------- |
| `MATCH` | The screening result is `hit`. | The customer matched one or more PEP, sanctions, or adverse media records. |
| `NO MATCH` | The screening result is `no_hit`. | The customer matched no records, and the journey can proceed. |
| `ERROR` | No condition matched. | The screening couldn't be completed. |
To change what each outcome does:
1. Click the module inside the Journey builder.
2. Click **Configure outcomes**.
3. Define what happens for each outcome. Route `MATCH` to a manual review, and let `NO MATCH` continue the journey. To learn more about routing outcomes, see [Set up evaluation](/docs/go-v2/platform/journey-builder/set-up-evaluation).
4. Click **Close** to apply your configuration.
Screening a customer against watchlists can produce false positives. Route a `MATCH` to manual review rather than to an automatic rejection, so that a reviewer can confirm the match in Investigation.
To learn more about outcome decisions, see [How to configure module outcomes in Go](/docs/go-v2/guides/product-guides/configure-outcome-decisions).
## Step 5: Publish the journey
Click **Publish to Preview** in the Journey builder. GBG Go displays a confirmation message.
Next, click **Dashboard** to see:
* Environment (Preview)
* Version number
* Resource ID
* Last published
* Actions list
Your journey is now available for testing in the preview environment.
## Step 6: Invite your customer
1. Click the **Actions** list.
2. Click **Invite a customer**. A dialog box appears.
3. Select the options for your use case, and then enter an email address, a mobile number, or both. The dialog box contains the following options:
| Option | Description |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Region** | The region that the journey runs in. Select **EU**, **US**, or **AU**. Your organisation may only be set up in some regions. |
| **Environment** | The environment that the journey runs in. Select **Production** or **Preview**. If you can't select an environment, then the journey isn't published there yet. |
| **Send invite to** | Enter an email address, a mobile number, or both. |
| **Advanced settings** | The link expiry and session behaviour that the invite uses. Expand this to review the current values, which come from the [link settings](/docs/go-v2/platform/link-settings) on the journey. |
The GBG Go platform presets the region and environment based on the journey that you selected. Select **Preview** while you test the journey. Change the region only if your organisation runs journeys in more than one region, because the region controls where your customer's data is processed and stored.
4. Click **Invite**. A message appears at the top right of the screen confirming that the invite started.
An invite is valid for one customer. By default it expires after seven days, and your customer can return to the journey if they close it before they finish. To change either default, see [Link settings](/docs/go-v2/platform/link-settings).
## Step 7: Complete the journey as your customer
Your customer receives a verification link by email or text message.
1. Open the link from the invite.
2. Enter the customer details that the journey collects, including the full name.
3. Submit the details.
Watch this demo to see the journey as your customer experiences it.
The GBG Go platform screens the details against the lists that your variant covers. It then reaches a decision based on the module's outcomes.
## Step 8: Review the screening result
Screening results are available in Investigation once your customer completes the journey.
1. Click **Investigation** on the left navigation menu. The Investigation dashboard opens.
2. Select the environment that you sent the invite to. If you are testing, then click the **Preview Environment** tab.
3. Select the region that you sent the invite to, using the region list in the top-right corner.
4. Find your customer's session in the list. If the list is long, then click **Add Filter** to search by name or email address.
5. Click the session ID. The session details page opens.
6. Find the PEPs and Sanctions module in the list. The outcome appears on the right of the module name, for example, **MATCH**.
7. Review the screening detail on the following tabs:
| Tab | What it shows |
| ----------------- | ------------------------------------------------------------------ |
| **Results** | The module results and the Advice fields, including each hit type. |
| **Sanctions** | The sanctions records that the customer matched. |
| **PEPs** | The PEP records that the customer matched. |
| **Adverse Media** | The adverse media coverage found for the customer's name. |
| **Raw Response** | The full response that the screening service returned. |
| **Outcome Rules** | The rules that produced the outcome. |
You have now screened a customer against PEPs, sanctions, and adverse media lists, and reviewed the result.
When the screening returns a match, the Advice fields on the **Results** tab tell you how strong that match is:
| Result | What it tells you |
| -------------------------- | ------------------------------------------------------------------------------------------------- |
| PEPs and Sanctions Results | The overall screening outcome, for example, PEPs and Sanctions Hit. |
| Sanctions Hit Type | Which identity elements matched a sanctions record, for example, the full name and date of birth. |
| PEPs Hit Type | Which identity elements matched a PEP record. |
| Adverse Media Hit Type | Whether negative media coverage was found for the customer's name. |
A hit type shows **Not available** when that list returned no match.
The module also returns a candidate score for the top PEP match and the top sanctions match. Each score runs from 0 to 100, where a higher score means greater confidence. A score of 0 means no match was found on that list.
Read the hit type before you confirm or reject a match. A match against a known alternate identity alias, or against the full name alone, is weaker than a match on the full name and date of birth.
## Next steps
* Change the decision on a session after your review: [Change decisions](/docs/go-v2/platform/investigate/change-decisions).
* See everything a session records: [View details of a journey session](/docs/go-v2/platform/investigate/view-journey-details).
* Understand the result codes the module returns: [PEPs and Sanctions](/docs/go-v2/platform/modules/compliance-screening/peps-and-sanctions).
* Configure and test the module in depth: [Understanding the PEPs and Sanctions module](/docs/go-v2/guides/product-guides/peps-and-sanctions).
* Invite a customer to a journey built for another verification task: [No-code guides](/docs/go-v2/low-code-builder/no-code/overview#guides).