> 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/overview.md).

# Overview

1Kosmos identity verification integrations extend IAL2-compliant identity proofing into the platforms and workflows where access decisions already happen.

***

The integrations follow a consistent pattern: a verification trigger initiates a 1Kosmos proofing session, the user completes document verification and biometric liveness check via email or SMS link, and the pass/fail result is returned to the originating platform to drive the next workflow step. Common use cases across all integrations include new employee and contractor onboarding, self-service password reset and account recovery, and privileged or risk-based re-verification, ensuring that identity is confirmed at every critical access event without requiring users to leave their existing environment.

#### Identity verification integrations:

* [Okta](/integrations/identity-verification/okta-identity-verification-for-account-management.md)
* [Epic](/integrations/identity-verification/epic-identity-verification-in-mychart-and-epiccare-link.md)
* [Microsoft](/integrations/identity-verification/microsoft-entra-vid-partner.md)
* [Sailpoint](/integrations/identity-verification/sailpoint-identity-verification-for-workflows.md)
* [Saviynt](/integrations/identity-verification/sailpoint-identity-verification-for-workflows.md)
* [ServiceNow](/integrations/identity-verification/servicenow-identity-verification-for-account-management.md)


---

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