> 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/saviynt-identity-verification-for-workflows.md). # Saviynt - Identity Verification for Workflows This topic explains how to connect 1Kosmos with Saviynt to initiate identity verification from within Saviynt Workflows. The 1Kosmos integration on Saviynt Exchange enables organizations to embed identity proofing directly into Saviynt Identity Cloud workflows, strengthening identity assurance at critical access lifecycle events. By completing this integration, organizations close the "trust on first use" gap in IGA by ensuring that only verified individuals are onboarded or granted elevated access. The setup involves configuring both a 1Kosmos tenant with IDV enabled and the Saviynt Universal Web Login (UWL) interface. Once configured, users are guided through a verification process whenever identity checks are required, initiated via an email or SMS link and completed using a government-issued ID and biometric selfie with liveness detection. #### Use cases: 1. **New Employee Onboarding** Organizations can verify new employees' identities as part of the Saviynt onboarding workflow. Users receive an email prompting them to verify their identity, complete document verification, and complete a liveness check through 1Kosmos, and are automatically approved in Saviynt upon success. 2. **Contractor and Third-Party Onboarding** Using Saviynt's Third-Party Access Governance (TPAG) module, organizations can verify contractors, vendors, and partners before granting access to protected applications. The Saviynt workflow initiates a 1Kosmos proofing session, and access provisioning proceeds only after successful verification. 3. **Risk-Based Re-Verification** Organizations can require users to re-verify their identity when risk conditions change, such as role escalation, privileged access requests, or flagged anomalous activity. Because 1Kosmos stores the initial identity record, re-verification does not require re-enrollment, reducing friction for legitimate users while maintaining assurance. --- # 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/saviynt-identity-verification-for-workflows.md?ask=&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.