> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/workflow-builder/launch-and-monitor-verification-sessions.md).

# Launch and Monitor Verification Sessions

***

{% hint style="warning" %}
Launching verification session instances from workflows is a **beta** feature.&#x20;
{% endhint %}

After creating a workflow, you can launch a verification session instance from it.

### Launch a verification session

{% stepper %}
{% step %}

#### Open Workflows

Log in to your tenant as a community administrator and navigate to **Workflows**.&#x20;
{% endstep %}

{% step %}

#### Create a new instance

Under the **Actions** column, click the **+** icon next to the workflow for which you want to create a verification session. The **Create a new instance** window appears.
{% endstep %}

{% step %}

#### Enter user details

Enter the **First Name** and **Last Name** for the user whose verification session needs to be initiated, and click **Continue**.&#x20;
{% endstep %}

{% step %}

#### Choose how to send the link

Select the mode in which the verification session link should be sent to the user.

| If you select               | The UI allows you to                                                                        |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| Scan the QR code            | Use the 1Kosmos mobile application to scan the QR code and continue on another device.      |
| Send a link to phone number | Enter a phone number and send a verification link via SMS to continue on the mobile device. |
| Send a link to email        | Send a verification link to the registered email address to continue.                       |
| Copy link                   | Copy the verification link and open it on another device to continue.                       |
| Continue on this device     | Proceed on the current device without switching.                                            |
| {% endstep %}               |                                                                                             |

{% step %}

### Continue verification

After selecting a mode, continue the verification process as defined in the configured workflow.&#x20;
{% endstep %}
{% endstepper %}

### Monitor verification instances

When a verification session is launched from a workflow, a corresponding instance is created. Administrators can track the progress and status of these instances from the Instances page, which provides a consolidated view of all workflow instances and their execution status.

To view workflow instances, log in to the AdminX interface, navigate to **Workflows**, and click **Instances**. The Instances page displays all verification sessions initiated through workflows.

#### Search and filter instances

| Option                | Description                                                                                         |
| --------------------- | --------------------------------------------------------------------------------------------------- |
| Search by Instance ID | Search for a specific instance using its unique Instance ID.                                        |
| Date Filters          | Filter by predefined ranges such as Today, This Week, or Last Month, or select a custom date range. |
| Filters               | Apply additional filters to narrow down the displayed instances.                                    |

#### Instance Summary

Selecting an instance displays detailed information in the **Instance Summary** section:

| Field         | Description                                                   |
| ------------- | ------------------------------------------------------------- |
| Workflow Name | Name of the workflow used to create the verification session. |
| Workflow ID   | Unique identifier of the workflow.                            |
| Created At    | Date and time when the instance was created.                  |
| Expires At    | Date and time when the instance will expire.                  |

#### Nodes Executed

The Nodes Executed section shows the sequence of workflow nodes executed during verification. Each node represents a specific step, such as document verification, form submission, identity validation, or a failure or success outcome. Selecting a node displays its execution details.

#### Node Output

The Node Output panel displays detailed output data generated during execution of the selected node, including Node ID, Workflow ID, Instance ID, node status, timestamp details, and result data. This helps administrators troubleshoot verification issues and analyze workflow execution results.

#### Instance status

Each instance displays a status indicating its current progress:

| Status    | Description                                                            |
| --------- | ---------------------------------------------------------------------- |
| Started   | The workflow instance has been initiated and is currently in progress. |
| Completed | The workflow instance has finished execution.                          |
| Failed    | The verification process failed at a particular workflow node.         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/workflow-builder/launch-and-monitor-verification-sessions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
