Migration Vocabulary Reference
Naming and terminology shifts between the legacy admin console and new admin console, version 2.0. The underlying capability exists in both versions; the language now better reflects what the platform does.
| Old term | New term | Definition |
|---|---|---|
| Acquired Attributes | Acquired Data | The data points a Checker returns, such as a name or address on file in the identity record or a device signal. Acquired Data can be used in custom policy rules and is now visible in the transaction report. |
| AXN Admin | Admin Console | The web application where you build, configure, deploy, and monitor workflows. Admin 2.0 is the redesigned version. |
| Visualization | Builder | The interactive workspace for building workflows on a visual canvas. Click a step to configure it or add steps right from the canvas. Replaces the old read-only visualization. |
| Attribute Providers (APs) | Checkers | The individual data-source connections that power the ID Dataweb platform. Each Checker connects to a specific provider or a set of redundant providers and returns acquired data and checks that feed the Policy Manager's decision logic. |
| Assertions | Checks | The pass or fail tests a Checker runs, such as a match tests and link tests. Policy rules evaluate Checks to reach a decision. |
| AXN Manage | Continuous Re-Authentication | The ongoing authentication layer for users who are already verified, confirming it is still them on each return or sensitive action. |
| Theming | Design Studio | One place to brand and style the Gateway screens your users see. Replaces the separate Theming, Document Capture, Attribute Labels, and Translation areas. |
| Copy Link + Send Verification Link | Generate verification link | An agent path that walks through the agent inputs, then sends the user a link by SMS or email, or copies it to share. Once the user receives the link, they complete the verification. Consolidates the old Send Verification Link and Copy Link actions. |
| BioGovID | Government ID and Selfie Match | Confirms identity by capturing and authenticating a government-issued ID, then biometrically matching a selfie to the ID photo with liveness detection. |
| Components | Groups | Reusable condition bundles. Define a set of checks once as a named Group, then reference it across rules instead of rebuilding it each time. |
| Human Identity / Relationships / Environmental | Identity / Risk / Possession | The three Checker categories. Identity confirms who someone is against authoritative records, Possession confirms what they control such as a device or phone, and Risk weighs how the session itself is behaving. These are the parent categories for subcategories such as Gov ID and PII. |
| (User) Attributes | Inputs | What the end user provides during a transaction, or what your system pre-fills for them. Renamed from User Attributes for clarity. |
| Transaction Events | Logs | The event log for a transaction, renamed from Transaction Events. In the new Transaction lookup report, Logs shows every event recorded during the transaction. |
| MobileMatch | PII Validation | This step cross-checks provided PII (name, address, phone, etc.) against authoritative carrier and identity records, and weighs phone line risk. A match indicates the identity is real and that the phone line is not compromised. |
| FastTap MFA | SMS Link | Confirms control of an affiliated phone number by texting a one-time link the user taps to continue. A lightweight possession check, often used for re-authentication or to enroll a number in MFA. |
| Try Now | Start verification session | An agent-driven path where the agent enters a user's information directly to run a verification on their behalf. |
| Services | Steps | The building blocks of a workflow. Each Step is a single moment in a user's journey where one or more Checkers run and a Policy evaluates the results to produce a decision: approve, deny, or step up to the next Step. |
| Relying Party | Subtenant | How you separate workflows, reporting, billing, and admin access by use case, team, or customer. Each subtenant has its own workflows and its own access scope; a user with subtenant-level access sees only that subtenant's workflows and data. |
| Template list | Template Gallery | The browsable library of workflow templates, shown with descriptions and previews so you can find the right starting point by use case. Replaces the old drop-down list. |
| Transaction (report) | Transaction lookup | The search console for finding past transactions to inspect, including the Checks that ran, the Acquired Data, and which rule decided the outcome. |
| AXN Verify | User Onboarding | Establishes a verified identity for users entirely new to your system, with no prior account or existing data. This is the Unknown to Verified transition in the Trust Progression Model. |

