{/* This one's a little weird. Notion AI says it's a Workforce control. I can't see it in Dashboard > Workflows, but I do see it enabled in Provisioning. It's definitely a module, but is some of the information below only applicable to the Workforce control? */}
The Claims Matching module verifies an employee's identity by comparing data from their Session against trusted reference data from one or more connected directories. Sessions that fail are routed to manual evaluation.
Integrations
:x: Web | :white_check_mark: iOS | :white_check_mark: Android
{/* TODO: Confirm SDK support with PM - above info is from NotionAI */}
How It Works
Claims Matching runs after identity verification has produced a set of claims—attributes like name, date of birth, country, city, and region extracted from the captured ID. It then retrieves reference attributes from one or more configured directory sources (Okta, Entra ID, LDAP, CSV, or a no-directory candidate record flow) and evaluates whether those attributes agree, claim by claim, according to the matching policy defined in the project settings.
Each claim in the policy is evaluated independently with two configurable dimensions:
- Match type controls how strictly the values are compared. Exact matching requires the values to be identical. Fuzzy matching applies a looser comparison algorithm, which varies by claim type: for example, name matching behaves differently from date-of-birth matching.
- Presence rule controls what happens when a claim is absent. If a claim is marked Required and is missing on either side—not present in the verification Session output or not present in the directory record—the claim fails. If a claim is marked Optional and is absent, it is skipped.
All required claims must pass for the Session to be auto-approved. If any required claim fails or is missing, the Session is routed to Claims Match Review as a single consolidated review item. Reviewers approve or reject the full set of claims together; review is not done field by field.
When multiple directories are connected, the system attempts matching against each one. If any directory satisfies the policy, the result is treated as a pass.
Use Claims Matching
For instructions on configuring Claims Matching in Dashboard, see: