Skip to main content
Alphabetical definitions of the terms used across TruU IDV. Each links to the page with the full treatment.

A

Activity: The console page with two tabs: Audit for configuration changes and Events for verification activity and sign-ins. See Activity and export. Admin: A seat that configures factors, flows, use cases, the directory, connectors, storage, the team and API clients. See Team and roles. Agent: A seat for help desk staff who send verifications and watch them in the help desk app. See Agent guide. API client: A credential for your own system to call the TruU IDV API, with scopes that limit what it can do. See API quickstart. Attribute coverage: The share of people in your directory who have a value for an attribute. It decides who can use factors that depend on it. See Connect your directory. Attempts per run: How many tries a person gets at one factor in a single run. See Retries.

B

Badge: A factor where the person taps their badge on a reader attached to the device. See Badge.

C

Catch All Flow: The flow every workspace starts with, used for Everyone on the built-in use cases until you change it. See Flows and templates. Column: One complete way to pass inside a flow, labeled Primary, Fallback 1, Fallback 2. Every factor in a column must pass. See Flows and templates. Column strength: The Strong, Fair or Weak rating the flow builder shows on each column. See Column strength. Connection: Where your data lives: your directory and your storage. See How integrations fit together. Connector: An integration under Settings → Connectors that either starts verifications (ServiceNow, Microsoft Teams) or acts after one succeeds (TruU Passwordless, Windows TAP, PingOne MFA). See How integrations fit together. Credential health: The settings page that checks every credential TruU depends on, daily and on demand. See Credential health.

D

Directory: Your Microsoft Entra ID or Okta organization, read live and read-only. One per workspace. See Connect your directory.

E

Email: A factor that sends a one-time code to the address on file. See Email. Enterprise SSO: Signing in to the console through your identity provider over OpenID Connect. See Sign-in, SSO and passkeys. Everyone else: The last rule on every use case, matching anyone the rules above didn’t. It can also be set to Can’t use this. See How use cases work.

F

Face: A factor that matches a live selfie, with a liveness check, against a reference photo. See Face. Factor: One method of proving identity: Face, Proofing, SMS, Email, Knowledge or Badge. See How factors work. Fallback: A column after Primary, tried when the person can’t use an earlier one. See Flows and templates. Flow: Factors arranged into columns with fallbacks. Use cases decide who gets which flow. See Flows and templates.

H

Help desk app: Where agents send verifications and watch them complete. See Agent guide.

J

Just-in-time provisioning: Creating members automatically on their first enterprise SSO sign-in, as Agents. See Sign-in, SSO and passkeys.

K

Knowledge: A factor that asks for a fact from the person’s directory record. The weakest factor; never use it alone. See Knowledge.

L

Liveness detection: The check that a real person is in front of the camera, not a photo, screen or mask.

O

Outcome: What happens after a verification passes, set on each use case: Report only, Issue a Temporary Access Pass, or Ping re-enrollment. See How use cases work. Owner: The seat with full control of the workspace, including deleting it. See Team and roles.

P

Passkey: A phishing-resistant sign-in using a fingerprint, face, device PIN or security key. Owners’ passkeys also act as recovery when SSO fails. See Sign-in, SSO and passkeys. Proofing: A factor that checks a government ID and a matching selfie through a proofing vendor (Didit, PingOne Verify, Persona or Entrust). See Proofing. Proofing photo: The selfie from a passed proofing check, kept as the person’s Face reference. See Proofing.

R

Rule: A line in a use case that sends one or more directory groups to a flow. Rules are checked top to bottom and the first match wins. See How use cases work. Run: One pass at a verification, from Begin until it ends without success. Each link allows a set number of runs. See Retries.

S

Sample mode: A new workspace’s state before a directory is connected: fictional employees, so you can try everything safely. See Quickstart. Self-service portal: A public page where employees request their own verification link. It uses the Credential reset use case. See Self-service portal. Short code: Your workspace’s identifier at sign-in and in the self-service portal address. Shown in Settings → General. SMS: A factor that texts a one-time code to the mobile number on file, which must be in E.164 format. See SMS. Store: A place verification files are kept: the TruU managed store, or your own Amazon S3 bucket or Azure Blob container. See Storage.

T

Template: A ready-made flow, such as Standard Corporate or Shared Devices, that turns on the factors it needs. See Templates. Try another way: The option on the verification page to move to the next column. See When a factor is offered.

U

Use case: A situation that needs verification, such as Onboarding, Credential reset or Helpdesk. It sets what the person is told, which flow each group gets, and what happens after. See How use cases work.

V

Verification link: The time-limited link that opens a person’s verification. Its lifetime depends on the use case. See Verification requests and links. Verification page: Where the person completes their verification, usually on a phone. See What to expect. Verification request: The record of one verification: who, which use case and flow, each factor’s outcome, and the result. See Verification requests and links.

W

Workspace: One organization’s TruU IDV environment, with its own directory, settings and team. One account can belong to several. See Workspaces.