Persona Workforce IDV helps organizations verify workers at important points in their lifecycle. These points are candidate screening, onboarding, account recovery, MFA reset, help-desk verification, and step-up before high-risk actions. This prevents unauthorized access to sensitive systems. It also automates processes, so IT and security teams have less work.
These FAQs answer frequent questions about Persona workforce solutions and integrations.
-
Which Identity and Access Management (IAM) platforms does Persona integrate with?
Persona has native integrations with:
- Okta — See Triggering Persona IDV within Okta and Configuring Okta via OIDC.
- Microsoft Entra ID — See Microsoft Entra integration overview.
- Cisco Duo — See Cisco Duo integration overview.
- OneLogin — See OneLogin integration overview.
Persona Authentications is our standards-based OpenID Connect (OIDC) identity provider. Through it, Persona can also be an identity-verification authenticator for all IAMs that support an external OIDC IdP, including Ping and Auth0.
We are developing more IAM integrations, based on customer needs. Contact your Account Team if you are interested in one of our current native integrations. Also contact them to request an integration with a platform that is not in this list.
-
Which Human Resources (HRIS/HCM) and Applicant Tracking (ATS) systems does Persona integrate with?
For employee (post-hire) verification, Persona integrates with your HR system of record. Persona uses the trusted worker data to fill in fields and to match:
- Workday HCM — See Workday HCM integration overview.
For candidate (pre-hire) verification, Persona integrates with leading ATS platforms. These integrations start identity verification at the correct stage of your hiring funnel:
- Workday Recruiting — See Workday Recruiting integration overview.
- Ashby — See Ashby integration overview.
- Greenhouse — See Greenhouse integration overview.
- Fountain — See Persona & Fountain integration.
We also support API-based custom integrations with all HRIS/HCM/ATS systems. Contact your Account Team if you are interested in our current native integrations. Also contact them to request an integration with a platform that is not in this list.
-
Which IT service management (ITSM) / help-desk systems does Persona integrate with?
Persona integrates with ServiceNow. Identity events in Persona (for example, a verification result or a flagged session) can then automatically open or update ServiceNow cases. This gives help-desk and IT teams the full result. Read ServiceNow integration overview.
-
How does Persona’s Okta integration work?
With the Okta integration, the Okta authentication and account-management policies can start Persona identity verification directly. The flow is:
- Okta administrators configure identity verification through the Okta Dashboard.
- When an event starts the verification (for example, a password reset, MFA change, or sign-in to a sensitive application), Okta sends workers to Persona for identity verification.
- Workers complete verification (Government ID + Selfie, etc.).
- Persona sends the results back to Okta to authorize the applicable access.
Persona supports Okta in two ways: as the native Okta “Persona IDV” account-management action, and as a standards-based OIDC IdP for application sign-in policies. For more information, read Triggering Persona IDV within Okta, Configuring Okta via OIDC, and Using Persona Workflows to manage Okta users & profiles.
-
How does Persona’s Cisco Duo integration work?
With the Persona Cisco Duo integration, Duo administrators can start Persona identity verification. The flow is:
- When necessary, Duo help-desk staff start identity verification from their console.
- Workers get a time-limited verification code.
- After workers enter the code, they complete Government ID and Selfie verification through Persona (Persona can do attribute comparison).
- Persona sends the results back to Duo. Admins can then continue with account actions.
For more information, read Cisco Duo integration overview.
-
How does Persona’s Microsoft Entra ID integration work?
With the Persona Microsoft Entra ID integration, organizations can give their workers secure self-service password resets, MFA resets, and Temporary Access Pass (TAP) issuance. The integration uses the Microsoft Graph API. The flow is:
- Organizations show the Persona flow to workers in different ways (for example, automatically from an internal support/help site, or manually created by help-desk staff).
- The employee then gets a Persona verification link.
- The worker uses Government ID and Selfie verification to verify their identity (Persona can also do attribute comparison).
- After a successful verification, the worker can set a temporary password, get a password that Entra generates, or get a Temporary Access Pass.
- The worker then signs in to Entra ID.
For more information, read Microsoft Entra integration overview and Using Persona Workflows to manage Microsoft Entra users & profiles. Persona can also issue a Microsoft Entra Verified ID credential after verification.
-
How does Persona’s OneLogin integration work?
Persona integrates with OneLogin through Persona Authentications, our OpenID Connect (OIDC) identity provider. During authentication flows, OneLogin calls Persona as an OIDC authenticator. For attribute comparison, Persona can also use the OneLogin REST API to find the OneLogin profile of the worker. For more information, read OneLogin integration overview.
-
How does Persona’s Workday integration work?
Persona offers two Workday integrations:
- Workday HCM (employee verification): Persona gets worker data from the Workday Get Worker endpoint. This data includes name, date of birth, email, job title, hire date, and other information. During verification, Persona compares Government ID details with this trusted Workday data. Read Workday HCM integration overview.
- Workday Recruiting (candidate verification): Persona automatically sends identity-verification links to candidates when events occur in your Workday hiring funnel. A recruiter does not have to start each one manually. Read Workday Recruiting integration overview.
-
How do Persona’s candidate (ATS) integrations work?
For pre-hire candidate verification, Persona connects to your ATS. Persona starts identity verification at the correct stage of the hiring funnel (for example, at the offer stage). Persona gets candidate/application data from the ATS and writes verification results back into the ATS record. For the specific trigger and write-back behavior of each platform, read the Ashby, Greenhouse, and Fountain integration overviews.
-
What are Persona’s recommended verification methods for Workforce IDV?
For most workforce use cases, we recommend:
- Government ID and Selfie verification with liveness detection.
- For US IDs, barcode verification for more security.
- For higher-risk scenarios, more verifications, for example Database Verification, AAMVA Verification, Email (2FA) Verification, and Phone Number Verification.
-
How does Persona handle worker/employee data privacy, especially in regions with strict regulations?
Persona gives several mechanisms to help you obey strict privacy regulations:
- Configurable redaction and data retention policies
- Region-specific consent flows
- Option to store only verification results without raw PII
- Support for GDPR right to be forgotten and data access requirements
- Option to encrypt sensitive data fields
For more information, read Security and Privacy Overview.
-
Can Persona do attribute comparison of verification data against our existing worker/employee records?
Yes. Persona can compare verification data with your current worker records and match on multiple attributes. For higher assurance, we recommend that you match on legal name and date of birth. You can import worker records from your IAM, HRIS, or ATS system through native integrations, API connections, or pre-fill options.
-
What happens if a worker / employee fails verification?
The Persona UI has automatic retry logic, real-time user guidance, and clear error messages. These decrease false failures. An employee or worker can use all retry attempts and get to a failure screen. For this condition, you can configure different next steps, including:
- Automatic step-up verifications
- Notifications to IT or other internal teams
- Custom workflows that start manual review processes in Persona (through Cases) or in external systems
-
My organization currently uses Persona for user / customer verification. Do we need to create a separate Persona Org for Workforce IDV?
Yes. If you use Persona for customer/user verification at this time, you must create a new Persona Org for your Workforce use case. For security, governance, and access control, it is very important to keep customer data separate from employee/candidate data. Only a separate environment is not sufficient.
- Data Security & Governance: When you keep customer verification data separate from worker/employee verification data, you follow security best practices and keep clear data boundaries.
- Access Control: With a dedicated org, you can manage permissions specifically for the persons who handle worker/employee data. This limits unnecessary access.
- Reporting & Analytics: Separate orgs give clearer reporting and analytics for each use case.
-
My organization is interested in using Persona for both Pre-Hire / candidate verification and Post-Hire worker/employee verification. Can these two use cases share the same Persona Org?
Yes. These two use cases can share the same Persona Org. You need a separate Persona Org only when you must keep candidate/employee data separate from customer/user data.
-
I’m an existing Persona customer. Do I need a separate Order Form for my Workforce use case?
Yes. If you use Persona for customer/user verification at this time, you need a separate order form for your workforce use case. This separation is necessary because different use cases have different compliance and legal requirements. Also, Post-Hire workforce use cases have a different pricing structure.
-
If I’m using Persona for both Pre-Hire and Post-Hire Workforce use cases, can these be on the same order form?
Yes. These two use cases can share the same order form. The document shows separate pricing structures for pre-hire and post-hire verifications.
Plans Explained
Workforce Integrations by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Workforce Integrations | Not Available | Not Available | Limited | Available |