> 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/workday-identity-verification-for-new-hires/1kosmos-configuration.md).

# 1Kosmos Configuration

The identity verification journey the employee completes is built and managed in 1Kosmos. 1Kosmos manages the verification session directly with the employee, and Workday stores only a reference ID and result status.

1Kosmos maintains Workday-specific verification Workflows that can be provided as a starting point and customized to match branding, journey steps, or other requirements. The journey typically includes a document scan, a selfie, and a liveness check.

1Kosmos provides API documentation, test credentials, and subject matter experts to support the customer's team through setup and testing. Before cutover to production, the full path from hire to verified result is validated in a lower (non-production) Workday environment.

**Note:** Contact your 1Kosmos team to configure the verification journey for your use case and to receive the setup and testing details for your tenant.


---

# 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/workday-identity-verification-for-new-hires/1kosmos-configuration.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.
