Over the past year, we realized that the ID Dataweb admin console had outgrown its original design. Configuring workflows required too many clicks across disconnected screens, policy logic was difficult to read and troubleshoot without support, and investigating the ‘what happened and why’ behind a denied transaction often required too much manual effort.

We took both customer and internal feedback seriously, and the all-new ID Dataweb admin console, or Admin 2.0 for short, is the result: a complete redesign of the ID Dataweb admin console, built around how teams actually work.

Here’s a look at the biggest changes.

A template gallery grounded in identity fraud intelligence

When new customers onboarded to the ID Dataweb platform, we noticed a consistent pattern: they’d open the console, see a dropdown full of complex-sounding workflows, and immediately ask their implementation contact,  “Which template is best for [insert identity lifecycle stage]?” These were teams with deep domain expertise, but they lacked an intuitive starting point. The customers who deployed fastest typically had one thing in common: they had seen a strong configuration elsewhere and adapted it to their own requirements. That insight shaped the new Template Galleries. 

Template Galleries bring curated, best-practice workflow and step templates directly into the admin console. Each template reflects current identity fraud intelligence and includes a description of its purpose, along with a visual preview you can explore before deploying. Whether you’re implementing a standard identity proofing flow or layering document verification onto an existing workflow, you can now start from a foundation designed by identity experts rather than a blank canvas. Over the coming months, we’ll continue expanding these previews with deeper insights and recommendations – so stay tuned!

Teams can deploy a template as-is or customize individual steps to align with their own risk thresholds and compliance requirements. The goal is simple: shorten the distance between opening the admin console and launching an effective workflow.

Visualize, build, and configure workflows in context

In the previous ID Dataweb admin console, workflow structure and workflow configuration were separated from step configuration. Teams would define the overall flow and end user experience in one set of screens, then navigate to separate pages for each step to configure inputs, checks, policy rules, and UI settings. That separation didn’t match how people naturally think about building workflows. It’s far more intuitive to see how policy logic relates to what comes before and after it.

The new Workflow Builder is a visual, interactive canvas where teams can assemble and configure workflows — including all individual steps — from a single screen. Selecting a step opens its configuration in a side panel adjacent to the workflow, preserving context while you work. The Policy Manager, accessible from any step, introduces an IF/THEN rule builder with nested conditions, pre-built group templates, custom rule creation, and inline retry configuration. Real-time validation flags errors and provides clear resolution guidance before deployment.

We were intentional about keeping configuration panels adjacent to the workflow rather than hiding them behind overlays or separate pages. A full-screen modal would remove the workflow context entirely, while separate screens would recreate the original problem. The side-panel approach preserves visibility into the overall flow while allowing teams to edit the details of a specific step, making it easier to stay oriented during configuration.

Clearer transaction reports for faster investigations

Configuration is only part of the challenge. Troubleshooting and investigation are equally critical — and for many teams, even more urgent.

In the previous transaction view, call center agents and identity fraud analysts investigating denied or suspicious transactions often had to mentally reconstruct the flow: which steps executed, in what order, and which rule triggered the outcome. Rebuilding that context made live support more difficult for call center agents and slowed investigations for identity fraud analysts who needed to piece together data before they could begin meaningful analysis.

The new Transaction Details Report surfaces the last completed step for every transaction, allowing teams to immediately identify where a user dropped off. Transactions are now presented within the workflow visualization itself rather than as disconnected steps on a flat page. Selecting a step reveals the exact rule that drove the outcome, along with input and output data, pass/fail status, and event-level logs. A transaction is fundamentally a path through a workflow, so the reporting experience now reflects that reality. Instead of forcing identity fraud analysts to mentally map log data back to a workflow structure, the interface performs that contextual work visually, allowing teams to focus on understanding the decision logic itself.

For call center agents, operations teams, and identity fraud analysts, this means faster investigations and less guesswork when transactions are denied or flagged. For compliance teams, it provides audit trails that map directly to the policy logic behind each decision.

Customize branding and theming from a single workspace

In the original ID Dataweb admin console, theming and branding settings were spread across more than 10 subtabs. The new Design Studio consolidates all visual customization into a single workspace with a live preview. Teams can configure fonts, colors, branding, and page layouts for the end user identity proofing experience while immediately seeing the results. Every setting that affects appearance now lives in one place, with no hidden overrides elsewhere in the console.

Streamlined verification tools for live call center agents

Call center agents interact with the admin console differently than operations or security teams. Their workflows are narrower, more repetitive, and often time-sensitive, which makes simplicity and speed especially important.  Previously, the admin console exposed three separate actions for verification: Send Verification Link, Copy Link, and Try Now. We simplified the experience by focusing on the call center agent’s actual objective: either generating a verification link or starting a verification session.

ID Dataweb admin console 2.0 replaces the previous actions with two streamlined workflows: Generate Verification Link and Start Verification Session. Generate Verification Link consolidates SMS, email, and copy-link delivery methods into a single guided flow. Advanced fields that call center agents rarely need are hidden by default, reducing input errors and keeping the interface focused on the task at hand.

No disruption, just better tools

ID Dataweb admin console 2.0 is live now for all customers. Existing workflows, policies, and configurations carry over automatically. This is an upgrade to the console experience, not a change to the underlying platform functionality. The current ID Dataweb admin console remains available through a toggle, allowing teams to transition at their own pace. We’re also providing in-app walkthroughs, updated documentation, and a live webinar on June 10 to help teams get familiar with the new experience. And as always, our support team is available to answer questions and gather feedback as customers explore the new admin console.