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

# Workday - Identity Verification for New Hires

This topic explains how to connect 1Kosmos with Workday for new hire identity verification.

Identity Verification by 1Kosmos integrates with Workday to verify new hires automatically during onboarding. Using document authentication, facial biometrics, and liveness and deepfake detection, 1Kosmos confirms that the person completing onboarding is the person who was hired, with minimal friction to the employee experience.

This page is an architecture and functional overview. For the configuration values, Workday Studio package, and step-by-step setup specific to your tenant, contact your 1Kosmos team.

#### Overview

1Kosmos provides a pre-built Workday Studio integration package, delivered as a `.clar` file, that connects Workday to the 1Kosmos identity verification platform. The integration is triggered from your Hire Business Process (BP) and is built from three components:

* **A custom report** that sources new hire data for each hire event.
* **A Studio integration** that calls the 1Kosmos APIs to start verification and notify the employee.
* **A custom object** that stores verification results back on the worker record.

1Kosmos also maintains Workday-specific verification Workflows that you can use as a starting point and customize to match your branding, journey steps, or other requirements.

#### Integration pattern

`Workday` → `Workday Studio` → `1Kosmos REST APIs` → `Workday Studio` → `Workday custom object`

This page is an overview. For the Studio package, configuration values, and step-by-step setup specific to your tenant, contact your 1Kosmos team.<br>


---

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