Enterprises leverage CLEAR to verify their global workforce to ensure employees are who they say they are. Workforce use cases are traditionally embedded across a suite of software systems such as:
Identity and Access Management (IAM)
Human Resources Information Systems (HRIS)
Applicant Tracking Systems (ATS)
Customer Relationship Management Tools (CRM)
Security Information and Event Management (SIEM)
Below are a list of use cases and our implementation recommendation:
💡
Tip: CLEAR recommends following the defaults above for fastest deployment. You can always customize each step if your systems have unique requirements.
Employee Verification
Verify your workforce to ensure all employees are who they say they are. Mitigate any potential fraudsters posing as employees
Select Integration Method
1A. Select Integration Method
Recommended: Standard Integration Other Options:
OAuth 2.0 and OIDC (works with SSO, federated identity)
Out-of-the-Box (fastest to deploy, minimal engineering effort)
Match or Create Users
1B. Match or Create Users
Recommended: Account Binding Other Options:
CLEAR Biographic Matching API
Custom matching (if you maintain your own identifiers)
Data Storage
1C. Store Data
Recommended:
UserID / PSUID (persistent identifier)
VerificationID (session reference for re-checks)
Optional:
PII (only if required for compliance or to populate non-IAM systems)
Employee Onboarding
Verify users during the application process and on their first day of employment. Ensure the user who completed the interview and accepted the job is the same person showing up on day 1.
Select Integration Method
1A. Select Integration Method
Recommended: Standard Integration Other Options:
OAuth 2.0 and OIDC (works with SSO, federated identity)
Out-of-the-Box (fastest to deploy, minimal engineering effort)
Match or Create Users
1B. Match or Create Users
Recommended: Account Binding Other Options:
CLEAR Biographic Matching API
Custom matching (if you maintain your own identifiers)
Data Storage
1C. Store Data
Recommended:
UserID / PSUID (persistent identifier)
VerificationID (session reference for re-checks)
Optional:
PII (only if required for compliance or to populate non-IAM systems)
Employee Account Recovery
Enable your employees to self service reset their password, or gain access to systems
Select Integration Method
1A. Select Integration Method
Recommended: Standard Integration Other Options:
OAuth 2.0 and OIDC (works with SSO, federated identity)
Out-of-the-Box (fastest to deploy, minimal engineering effort)
Match or Create Users
1B. Match or Create Users
Recommended: Custom matching (if you maintain your own identifiers)
Other Options:
CLEAR Biographic Matching API
Account Binding
Data Storage
1C. Store Data
Recommended:
UserID / PSUID (persistent identifier)
VerificationID (session reference for re-checks)
Optional:
PII (only if required for compliance or to populate non-IAM systems)
Conditional Access
Trigger a CLEAR verification when users attempt to access privileged applications
Select Integration Method
1A. Select Integration Method
Recommended: OAuth 2.0 and OIDC (works with SSO, federated identity) Other Options:
Standard Integration\
Out-of-the-Box (fastest to deploy, minimal engineering effort)
Match or Create Users
1B. Match or Create Users
Recommended: Custom matching via CLEAR userID (if you maintain your own identifiers)
Other Options:
CLEAR Biographic Matching API
Account Binding
Data Storage
1C. Store Data
Recommended:
UserID / PSUID (persistent identifier)
VerificationID (session reference for re-checks)
Optional:
PII (only if required for compliance or to populate non-IAM systems)
Physical Access
Invoke a CLEAR verification when a user needs to physically access a building
Select Integration Method
1A. Select Integration Method
Recommended: Standard Integration Other Options:
OAuth 2.0 and OIDC (works with SSO, federated identity)
Out-of-the-Box (fastest to deploy, minimal engineering effort)
Match or Create Users
1B. Match or Create Users
Recommended: Custom matching via CLEAR userID (if you maintain your own identifiers)
Other Options:
CLEAR Biographic Matching API
Account Binding
Data Storage
1C. Store Data
Recommended:
UserID / PSUID (persistent identifier)
VerificationID (session reference for re-checks)
Optional:
PII (only if required for compliance or to populate non-IAM systems)
