Introducing Prembly New Dashboard

Overview

The new Prembly dashboard replaces a product- and endpoint-based menu with navigation organized around the key tasks customers come to the platform to do. Rather than asking customers to understand Prembly’s internal structure, the new layout follows their mental model: onboard people and businesses, verify them, screen them, detect fraud, resolve cases that need human attention, stay compliant, and understand performance. Each area has a clear purpose, owns its own history and reporting, and connects to a unified Customer 360 profile that makes Prembly a connected platform rather than a collection of endpoints. The result is a simpler, more scalable experience that can adapt to each customer and each role.

From Features to Tasks

The old Prembly navigation was organized mostly around products, endpoints, and technical modules. As the platform grew, that created a menu that felt cluttered and made it hard for customers to figure out where a capability belonged or what they should use it for.

So, what we did was shift from feature-based navigation to task-based navigation, organizing everything around the work customers come to the platform to do.

Overview Page: The Customer’s Operational Home

The new structure starts with Overview, which we turned into the customer’s operational home. Instead of a generic dashboard, it now provides a customizable view of what matters most to that specific customer.

Customer 360

We elevated Customer 360 to a top-level destination because it represents the accumulated value of the platform. Every verification, screening, fraud signal, onboarding activity, and case contributes information to a customer profile. That’s what transforms Prembly from a collection of endpoints into a connected platform.

Onboarding/Workflows

Onboarding/Workflows became the place where customers design and understand their onboarding journeys. We moved SDK Setup here because SDKs are really just one part of a larger onboarding process that can combine verification, screening, fraud detection, and decision rules. Flows, sessions, drop-offs, and eventually automated decisions now all live together around the actual job customers are trying to accomplish: getting people and businesses onboarded successfully.

Core Capabilities

For the core capabilities, we followed a simple sequence of questions. Verification answers, “Is this person or business real?” Screening answers, “Does this person or business meet our compliance requirements?” Fraud answers, “Is there suspicious activity or behaviour?” And Cases answers, “What needs human attention or a decision?” That gives each major capability a clear reason to exist and makes the navigation much easier to understand without requiring customers to know Prembly’s internal product structure.

Module-Level History and Reporting

We also made sure each module owns its own operational history and reporting rather than sending customers to one global reports section. That keeps information close to the action that generated it and makes the system more scalable as Prembly adds capabilities.

Cases

Cases got elevated because it represents work that needs to be done, not just information to be viewed. Alerts and signals from verification, screening, fraud, and compliance now become queue items when human intervention is required. So My Queue, All Cases, workflows, and escalations are all part of a proper operational workspace rather than treating important decisions as disposable notifications.

Compliance

For Compliance, we brought together the ongoing obligations of the organization, including the Compliance Lens, obligations, filings, signals, and calendar.

Analytics

Analytics sits above the individual modules as the place to understand patterns across the entire platform, generate reports, answer business questions, and schedule recurring insights.

Developers and Settings

Developers groups everything required to build and operate integrations with Prembly, while Settings stays focused on organization-level configuration. We moved technical utilities like webhook URLs and logs into Developers rather than hiding them inside general settings.

Guiding Principle

The overall principle was simple: the navigation should represent the customer’s mental model, not Prembly’s internal architecture. Customers should be able to look at the navigation and immediately understand what each area is for without knowing which API or product module powers it.

What’s Next: Role-Based Activation and Global Utilities

From there, role-based activation can make the experience even more relevant by highlighting the workspace most useful to the person logged in, while notifications and system status remain lightweight global utilities rather than competing with the primary navigation.

Priority Modules

• Verification (KYC, KYB, Background check)
• Customer 360
• Transaction monitoring & AML Screening
• Workflows (Customer, business & Vendor onboarding)
• API Integrations

What changed

1. SDK widget setup now lives in Workflows
2. You can now see detailed systems analytics in one place
3. Everything developer related (SDK setup, MCP, API integration & logs) are now in one place (developers)
4. Security settings (including IP whitelisting is now under developers)
5. Vendor data is now under customer360

Check out our new dashboard today - https://app.prembly.com/