Skip to content
Go to Dashboard

Cases: Layout Resource Modules

Overview

When you build a layout for a Case or an Account in Persona, you’re assembling it from modules. Modules are self-contained building blocks that can be configured to display whatever you want to show. A Resource module is a pre-configured module optimized to display a specific type of commonly used data. Resource modules typically display objects related to the current record you’re viewing.

Available Resource Modules

Every Resource module is configured to represent a specific type of information. For example, if you drag an Inquiry Resource module into a case layout, the module automatically finds and loads all associated inquiries tied to the current Case. You can use Smart Input to modify what data appears, such as applying filters.

The available data connections are:

  • Inquiries
  • Verifications
  • Reports and Report Runs
  • Transactions
  • Accounts
  • Cases
  • Documents
  • Assignee History

Because each module is scoped to a specific data type, a layout typically contains multiple Resource modules side by side — one for each type of related record you want reviewers to see.

View Options

Most Resource modules offer two view options: List and Table. List view displays each object’s information in a separate collapsible section, stacked consecutively. Table view displays data in a table format powered by the Data Table Module.

Resource modules are designed for readable, scannable presentation:

  • Collapsible sections. Each module renders as its own section with a heading. You choose whether it starts open or collapsed — useful for keeping frequently accessed data visible while tucking away secondary information.
  • List or table view. Present related records as a list of cards or as a table, whichever best fits your data.
  • Configurable fields and columns. Choose which attributes display, so reviewers see the fields relevant to their workflow without unnecessary clutter.
  • Sorting, filtering, and actions (in the modern version of the module). Reviewers can sort and filter related records and, in some cases, take actions on them without leaving the page.

The goal is to give reviewers a complete, organized view of everything connected to a record in one place — eliminating the need to navigate to each related object individually.

The individual Resource modules at a glance

ModuleWhat it connects toTypical use
InquiriesThe identity verification sessions tied to this recordView every verification attempt a person has completed — for example, all ID checks run on this account
VerificationsIndividual verification results (ID, selfie, database, etc.)View the specific checks and their outcomes that comprise an inquiry
ReportsScreening or background reports linked to the recordReview sanctions/watchlist, adverse media, or other reports attached to a case
Report RunsIndividual report executionsTrack each time a report was run and compare results over time
TransactionsTransaction records linked to the account or caseReview a person's transaction activity when investigating fraud or monitoring behavior
AccountsRelated end-user accountsView accounts connected to this case or group related accounts together
CasesOther cases related to this oneSurface linked or duplicate investigations so a reviewer has full context
DocumentsCollected or uploaded documentsView the IDs, proofs, and supporting files gathered for this subject
Assignee HistoryList of users that have been assigned to the caseChecking which users have been assigned to a case.

Putting it together

A well-designed Case layout might include a Verifications module (to confirm identity checks passed), a Documents module (to view uploaded IDs), a Transactions module (to review activity), and a Related Cases module (to check for connected investigations) — each a separate Resource module pulling in its own slice of connected data. The result is a single, holistic review interface where trust-and-safety or operations teams can view everything related to a subject without leaving the page.

Was this article helpful?
Thanks for the feedback. It helps us improve these docs.