> 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/integrations/identity-verification/okta-identity-verification-for-account-management/configuring-verification-flow-and-workflow-in-1kosmos.md).

# Configuring verification flow & workflow in 1Kosmos

You will need to configure the identity verification steps that you want the end user to go through. To do this, you must configure a verification flow and a workflow.

### Verification flow

The verification flow configuration is used during the ID proofing session to compare incoming claims from the Epic request with the data extracted from the identity document. 

This ensures that the claims requested by Epic match the verified information obtained during document verification. For more information, see [Configuring Verification Flows.](/identity-verification/configurations.md)

### Workflow

You must configure a workflow in 1Kosmos that the end user will use to verify their identity. The workflow uses the verification flow configuration to determine which claims to verify. For more information, see [Workflow Builder.](https://docs.1kosmos.com/workflow-builder/)<br>

{% hint style="info" %}
You must copy and save the Access Code for your workflow. This will be used in Okta to direct users to the correct workflow.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1kosmos.com/integrations/identity-verification/okta-identity-verification-for-account-management/configuring-verification-flow-and-workflow-in-1kosmos.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.