RegiSentinel Workbench — User Guide

RegiSentinel Workbench — User Guide (v2)

Audience: Compliance officers, BSA/AML analysts, regulatory affairs, legal, and risk teams using the signed-in workbench.
Last updated: July 2026
How to read this: We describe why each part of the product exists, how screens connect, and when a compliance professional would choose one path over another. This is not a click-by-click instruction sheet — you already know how to use a browser. When we mention a control, it is because the choice matters for your work, not because we are training you on buttons.

In the app: After sign-in, open User guide in the header for this document (with a table of contents), Features for a shorter overview, or Sources map for an illustrative map of supervisory families your deployment may ingest.

Important: RegiSentinel supports research and operations. It is not legal advice. Structured extractions and Ask answers point to sources — your judgment and internal policy still govern decisions.

1. How compliance teams use RegiSentinel

Most compliance work alternates between two modes:

Understanding — What changed? What applies to us? How do regulators in different jurisdictions treat the same topic? You need curated publications, structured extractions (obligations, enforcement, impact), and a map of themes across regulators — not a raw document dump.

Operating — Who owns the follow-up? What is the status? What evidence did we rely on? You need Cases, assignments, and an audit trail tied to regulatory signals.

RegiSentinel separates those modes on purpose, but keeps them connected. You can read a FinCEN publication in your AML & sanctions Domain Pack, assign yourself a Case from Needs Attention, and later manage that Case on the Cases desk — without re-entering context. You can also start from Search when you already know the keyword or docket, or from Saved Searches when you monitor the same query every week.

A useful mental model:

Home          → orient · search the full catalog · pick a Domain Pack
Domain Pack   → understand · monitor · compare regulators · read sources
Search        → investigate · narrow the full catalog · attach docs to Ask or Cases
Cases         → operate · assign · progress · journal · team queue
Saved Searches → monitor · return to the same catalog query

The Ask & Verify dock stays on the right on most screens. It answers from retrieved material in your current scope and shows numbered sources. Scope changes as you move — full catalog on Home and Search, pack-scoped in a Domain Pack, case-scoped on Cases — which is why navigation choice matters before you ask a question.

2. Home — where you land and what it is for

After sign-in you usually land on Home (/). Think of Home as the foyer: it does not try to be your daily monitoring dashboard. It orients you, exposes the size of the corpus, and offers two front doors — search everything or open a discipline workspace.

What Home is for

Home answers: Where should I go next? It is the right starting point when you have not yet chosen a regulatory discipline, when you want the widest catalog search, or when you are returning after a few days away and need to see which Domain Packs you can open.

It is not the best place for day-to-day “what changed in AML this week?” That work lives inside the AML & sanctions (or other) Domain Pack Overview tab, where publications, extractions, and Needs Attention are scoped to your pack’s regulators and themes.

What you see on Home

Intro strip — A short headline: search and ask across the catalog, or open a Domain Pack for discipline-scoped work. This mirrors how teams actually split responsibilities: enterprise search versus pack owners who live in one domain.

Corpus scale (when shown) — Document count, regulator count, and jurisdiction count. Useful when explaining to leadership how much material the platform ingests, or when you wonder whether an empty result is “nothing exists” versus “wrong scope.”

Catalog search — A single search box that takes you to the Search workspace with your query. This searches the full Data Catalog (titles, regulators, URLs, metadata) — not limited to one Domain Pack. Compliance teams use this when the question is organizational (“find everything mentioning beneficial ownership certification”) rather than pack-scoped (“what’s new in our AML pack this month”).

Saved Searches picker — Opens queries you saved earlier. If your team runs the same monitor weekly (e.g. “OFAC + treasury press releases + sanction”), starting from a Saved Search avoids rebuilding filters.

Domain Packs grid — Cards for each discipline workspace your account is licensed to open (for example AML & sanctions, Securities & markets, Consumer protection). Cards you cannot open may appear as roadmap previews depending on deployment. Each openable pack is a subscription boundary: regulators, Knowledge Graph, and default Ask scope are configured for that discipline.

How Home relates to other screens

From Home you go to…	You get…
Search (Enter in catalog search)	Full-catalog investigation with Documents and Structured Extractions tabs
Domain Pack (click a card)	Discipline workspace with Overview and Coverage tabs
Saved Searches (picker or nav)	Monitor lane for recurring catalog queries
Cases (header nav)	Cross-pack work queue — not launched from the grid, but always one click away

Home keeps the Ask & Verify dock available on the right. On Home, Ask uses full-catalog scope unless you have narrowed regulators or document types elsewhere. That is powerful for ad hoc questions but slower and broader than asking inside a Domain Pack after you have already filtered to AML regulators.

Example — Monday morning, enterprise search

Maria is a compliance generalist supporting multiple lines of business. She does not know yet whether today’s question belongs in AML or Securities. She starts on Home, runs “beneficial ownership rulemaking” into catalog search, and lands in Search. She scans matching documents, adds two to Ask scope, and verifies an answer against numbered sources. Only later does she open AML & sanctions to see how the pack’s Overview and Coverage treat beneficial ownership as a theme across FinCEN, OCC, and FATF-style sources.

If she had opened AML & sanctions first, her search and Ask would have been pack-scoped — faster for AML-only monitoring, wrong tool for a cross-discipline first pass.

Example — AML officer, pack-first

James owns the BSA/AML programme. His week starts in AML & sanctions (from Home card or Domain Packs in the header), on Overview: Needs Attention, recent publications, structured obligation extractions. He only returns to Home when he needs full-catalog search or to open a second pack (e.g. Payments & MSB).

The header is the same on Home, Domain Pack, Search, and Cases. It is worth learning once.

Home · Search · Saved Searches · Cases · Domain Packs ▾ · Firm Systems ▾ · Resources ▾ · (account)

Each item is a workspace, not a settings page. The rule of thumb: pick the workspace that matches whether you are orienting, understanding (pack or search), monitoring (saved search), or operating (cases).

Home

When to use: Landing, corpus orientation, opening any licensed Domain Pack, launching full-catalog search without picking a pack first.

When to skip: Daily discipline monitoring, theme-level regulator comparison, or Case management — use Domain Pack or Cases instead.

Search

When to use: You have a specific query (keywords, docket, instrument name, regulator + topic). You need the widest catalog slice, Documents and Structured Extractions side by side, or you are building evidence before you know which pack owns the issue.

How it differs from Home: Home’s search box is an entry point; Search (/search) is the dedicated workspace with filters, result lists, and room to work. Search is where you spend time refining — not a single hop.

Relation to Domain Pack: Search is cross-pack by default. Inside a Domain Pack, catalog narrowing and publications are pre-scoped to pack regulators — better for recurring monitoring, weaker for “I don’t know which pack yet.”

Saved Searches

When to use: Recurring monitors — same keywords and facets weekly or after major ingest. Compliance teams use this for “show me anything new that matches our LIBOR transition query” or standing sanction keyword watches.

Relation to Search: A Saved Search reopens a defined catalog query. Saved Searches (/saved-searches) is the management lane: list, open, delete, see alert-style hits when your deployment enables notifications.

Relation to Domain Pack Overview: Overview shows pack-scoped recent publications and extractions without you defining a query. Saved Search is your persistent query across the catalog (subject to license and facets).

Cases

When to use: Operating work — assign, status, due dates, review, team queue, case journal. Anything that must survive beyond “I read it once in Overview.”

How it differs from Needs Attention in a Domain Pack: Needs Attention on Overview is an in-context slice — see signal, open source, assign to yourself, jump to Cases. Cases (/workflow) is the system of record for workflow: My Cases, All Cases (team-visible queue), Teams tab for roster and pack envelope.

When compliance users live here: End of day triage, weekly stand-up, audit prep (“show me open items for this rulemaking”), handoff to a colleague (team model and linked copies when enabled).

Relation to Domain Pack: Domain Pack is where you discover and read; Cases is where you run the programme. Bridges like Assign to me, Open in Cases, Track as Case from Ask, and Add to Cases from catalog exist so you do not re-type context.

When to use: Fast entry when you already know the discipline — one click to AML & sanctions without scrolling Home. The menu lists licensed packs; “Browse all on Home” returns to the grid.

When to use Home grid instead: When you want corpus stats, catalog search, and pack cards in one visual breath — onboarding a new team member, or choosing between packs you rarely open.

When to use: Paid add-on surfaces — policies & controls, GRC connectors, surveillance, TMS — when your organization licenses Firm Systems. This is your internal policy and control fabric mapped against regulatory library context, not the same as Domain Pack publications.

When to skip: Pure regulatory horizon scanning with no internal policy import yet. If menu items are disabled, your tenant has not purchased the SKU.

Help, account, and administration

Resources (header menu) — User guide (/help/workbench, this document), Sources map (/help/official-sources), and Send feedback (opens a modal — there is no separate feedback page). A shorter Features overview still exists at /help/features if your deployment links it; it is not in the Resources menu on all builds.

Account (avatar menu) — Display name, email, and Sign out.

Regulatory scope comes from licensed Domain Packs, administrator entitlements, and your current screen (pack, Search facets, case selection). Email alert preferences and Ask usage limits are handled by your operator — contact them if you need digest email or token limits changed.

Administration (staff only) — Operators with admin access see a separate Admin menu: users, ingestion jobs, schedules, Ingestion health (seven-day ingest popover), Ask request log, and similar. Patron compliance users normally do not use this menu.

4. Choosing a path — scenarios

These are typical navigation choices, not procedural steps.

“Something new landed — is it material?”

Start in the relevant Domain Pack → Overview. Publications shelf and structured extractions are tuned for “what changed recently in our discipline.” Use Needs Attention when the platform has elevated a signal. If it warrants follow-up, assign or open Cases; if you only need to read and cite, stay in Overview publications master/detail.

Use Search instead if the item might sit outside pack regulators (e.g. cross-cutting DOJ press) or you are unsure which pack owns it.

“How do we compare to peer regulators on this theme?”

Domain Pack → Coverage tab. This is the Regulatory Knowledge Graph workspace: theme × regulator matrix, gaps, compare, firm view when licensed. Overview tells you what happened; Coverage tells you how supervisory expectations line up across the pack’s regulator set.

Search and Ask alone cannot replace Coverage for cross-regulator structural comparison — they answer questions; Coverage shows the map.

“I need the exact filing / rule text”

Search with regulator and document-type facets, or Domain Pack → Overview → Publications when you already know it is in-pack. Add documents to Ask scope for Q&A with numbered citations, or Add to Cases if the research becomes tracked work.

“Same hunt every Monday”

Saved Searches — save from Search once, reopen from Home picker or Saved Searches nav. Complements pack Overview (editorial recent feed) with your query definition.

“What is assigned to me / the team?”

Cases → My Cases or All Cases. Do not rely on Overview alone for status — Overview is read-first; Cases is operate-first.

“General counsel asked an ad hoc cross-domain question”

Home → Search → Ask with full catalog scope. Open specific packs only after you identify which discipline owns the answer.

5. Ask & Verify on every screen

The Ask & Verify dock (right side) travels with you. Its behavior depends on scope:

Where you are	Typical Ask scope
Home	Full catalog (unless you set catalog facet filters)
Search	Full catalog + your search/facets + any documents you attached
Domain Pack	Pack regulators and themes; tighter when you pick a theme or document
Cases	Selected case and linked regulatory sources

Clear chat starts a new conversation thread and clears scope. Clear scope (when shown) drops document/batch focus but keeps chat history. Use Clear chat when the topic changes; use Clear scope when you only want to widen or reset retrieval focus.

Questions that ask for “latest” or “most recent” may take longer because the system prioritizes recency across more material. Questions with a specific year or rule citation are usually faster.

Full Ask guidance (history limits, verification habits) stays in product help; later chapters tie Ask to Overview publications and Coverage theme selection.

6. Domain Pack workspace — two tabs, one discipline

When you open a Domain Pack — from Home, the Domain Packs menu, or a deep link — you enter a discipline workspace. Examples: AML & sanctions, Securities & markets, Consumer protection. Each pack is a licensed slice of the regulatory library: a defined set of regulators, themes, and structured extractions that match how compliance teams organize ownership (BSA/AML desk versus markets surveillance versus UDAAP).

The pack workspace is not a second copy of Search. Search is intentionally wide; the pack is intentionally deep. Publications, extractions, Needs Attention, and the Knowledge Graph are pre-filtered so you are not re-selecting FinCEN, OFAC, and SEC every morning.

Two tabs — Overview and Coverage

At the top of the pack workspace you will see two tabs:

Tab	Purpose
Overview	What is happening — recent publications, structured extractions, impact and attention signals, reading room
Coverage	How the discipline maps — themes across regulators, gaps, compare, firm alignment when licensed

Older product versions treated “updates” as a separate tab; that flow is now folded into Overview. If a bookmark still says Updates, you land on Overview.

Default: Opening a pack shows Overview. That matches how most compliance users start the day: scan what changed, then drill.

When to switch to Coverage: When the question is structural — “Do we have equivalent SAR guidance across FinCEN and FCA?” — not “What published yesterday?” Coverage is the moat for cross-regulator ontology; Overview is the moat for timely situational awareness.

Ask scope inside a pack

While you are in a Domain Pack, Ask & Verify defaults to pack regulators and themes. That makes questions faster and more relevant than asking from Home. If you select a theme on Overview’s left rail or a cell in Coverage, Ask can narrow further. Change domain (breadcrumb or home) returns you to pack selection and resets pack scope.

Some deployments show an internal coverage strip when Firm Systems data exists — policy and control counts mapped to this pack. That bridges external regulation (pack) with internal documentation (policies & controls). It is optional and depends on Firm Systems licensing and imports.

Example — pack as the “office” for AML

An AML programme treats AML & sanctions as their office. Overview is the morning newspaper; Coverage is the map on the wall showing which themes have strong FinCEN versus EU versus FATF-style coverage. Search is the library downtown when they need something outside the usual regulators; Cases is the task system where SAR programme updates and examination findings live.

7. Overview — your daily monitoring surface

Overview answers: What should we care about right now in this discipline? It combines executive context, a short dashboard, structured regulatory intelligence, and a publications reading room in one scroll — so you are not jumping between disconnected widgets.

Executive strip

At the top, a compact scorecard summarizes pack scale: themes in scope, regulators mapped, obligations and enforcement counts where available. This is leadership-ready context (“what does this pack contain?”) without opening Coverage.

Below that, short intel lines may highlight trend or entity context depending on ingest. The strip is deliberately shallow — a few seconds to orient, not a report.

Dashboard row — Most Impacted and Needs Attention

The next band splits Most Impacted and Needs Attention side by side.

Most Impacted surfaces business-type or cohort lines that are carrying disproportionate regulatory impact in this pack — useful when your institution serves multiple customer segments (MSB, correspondent banking, private banking) and impact is not uniform.

Needs Attention is an in-context queue, not a replacement for Cases. Each row is a regulatory signal the platform elevated: enforcement action, high-severity impact, deadline-bearing rulemaking, or similar. You can open the source, read summary context, assign to me, or open in Cases when the item needs ownership and status tracking.

Compliance benefit: Needs Attention stops “I saw something in a feed” from dying in email. It ties the signal to pack context. Cases is where the signal becomes work with audit trail; Overview is where you notice it.

Theme rail (left)

On wider screens, Overview includes a left theme rail — the same theme vocabulary as Coverage, but tuned for filtering the center panel. Each theme shows counts (publications, structured rows, obligations where mapped). Search in the rail header narrows long theme lists.

Selecting a theme filters Overview content to that topic — publications shelf, extraction highlights, and rail selection stay aligned. This is how you run a theme stand-up (“everything on beneficial ownership this week”) without building a Saved Search.

Status chips (covered / gap) echo Coverage semantics so you see weak areas even while staying on Overview.

Structured Extractions

The hero section of Overview is structured regulatory intelligence — obligations, enforcement, and impact rows extracted from source documents. These are not keyword hits; they are LLM-structured artifacts you can cite in programme documentation, gap assessments, and examination prep.

Facet tabs let you emphasize obligations versus enforcement versus impact. Rows use card layout: title, metadata pills, optional citation expand, actions to open source or Ask. Caps keep the hero scannable (roughly a dozen obligation rows visible in the hero band); the full set may be larger in Coverage or Search extractions.

Why compliance teams care: Extractions turn a 200-page guidance into discrete duties you can map to controls. Overview gives you the latest structured rows in-pack without running Search.

Publications shelf

Below extractions, Publications is a reading room for recent in-pack documents. Filters may include severity, high-priority toggle, and sort (newest, oldest, severity) so you can match your team’s triage style.

Master/detail layout: select a publication in the list, read summary and metadata in the detail pane, open the official source, or Ask about the document. This is where programme owners read — distinct from Search’s forensic narrowing.

When the pack has nothing recent in scope, a compact empty-scope banner explains that (for example no publications in the recency window) without hiding the rest of Overview.

Overview versus Search — when to stay put

Stay on Overview when regulators are already in-pack and you want editorial recency — what the pack’s ingest surfaced lately. Move to Search when you need arbitrary keywords, cross-pack regulators, or docket-style hunt across the full catalog.

Example — examination prep week

A BSA officer spends Monday on Overview filtered to suspicious activity reporting via the theme rail. Publications shelf shows FinCEN and FFIEC items from the last 30 days; Structured Extractions lists obligation rows with citation expand for policy mapping. Two Needs Attention rows get assigned to me and appear in Cases for the weekly compliance meeting. Coverage wait until Tuesday when the committee asks how SAR themes compare across US and UK regulators.

8. Coverage — the Regulatory Knowledge Graph

Coverage answers: How does this discipline map across regulators and themes? This is the product’s cross-regulator ontology view — the structural story prospects care about when they buy a Domain Pack.

Stats bar

Across the top, counts for themes, regulators, mappings, obligations, enforcement, and gaps anchor the view. Gaps are first-class: weak or missing implementation for a theme in a regulator column is visible, not buried in search results.

Views inside Coverage

Coverage is one tab but several sub-views (toggle in the panel):

Sub-view	Best for
By theme (default)	Theme-first analysis — scorecard, overlap, evidence, compare
All regulators	Matrix heatmap — every theme × every pack regulator
Firm	Internal policy/control mappings and pack-scoped gaps (Firm Systems)
Advanced	Power filters and grouping

Most compliance strategists live in By theme or the matrix.

Theme rail and selection

The left rail lists pack themes with search, status (covered / gap), and short labels (full names on hover). Selecting a theme drives the center panel: scorecard, implementation list, overlap buckets, and actions.

Gaps only filter hides well-covered themes so committee packs focus on remediation.

Coverage matrix (All regulators)

The matrix plots themes as rows and regulators as columns. Cell glyphs show full alignment, partial overlap, or no equivalent. Row and column totals help you see concentration risk — for example one theme only implemented under FinCEN but not OFAC.

Selecting a cell opens detail: evidence cards, counts, links to catalog filtered by theme, Ask placeholder scoped to theme, and navigation that can switch you to Overview with the same theme selected.

Compliance benefit: In a single screen you defend programme breadth to audit or board — “here is our map, here are the holes” — without building a spreadsheet from scratch.

Compare regulators

Within a theme, Compare regulators picks two columns (for example SEC and ESMA) and shows side-by-side implementations, sample obligations, and overlap buckets (common, partial, unique, no equivalent). Ask to compare prefills a structured cross-regulator question.

This supports second-line and policy teams justifying harmonized procedures — or documenting intentional differences.

Firm view

When Firm Systems is licensed and populated, Firm shows pack-scoped policy mappings and gaps tables — external regulation mapped to internal controls. This connects Coverage’s external ontology to your control library.

Coverage versus Ask

Ask answers natural-language questions with citations. Coverage shows persistent structure you can screenshot, filter, and revisit. Use Ask for ad hoc nuance; use Coverage for repeatable supervisory narrative.

Example — board slide in one sitting

A head of compliance opens AML & sanctions → Coverage, enables Gaps only, walks the theme rail for sanctions screening and travel rule, screenshots matrix cells for US versus EU coverage, and uses Compare for FinCEN versus HM Treasury implementations. Overview supplied the weekly “what changed”; Coverage supplies the “how we’re built” story.

9. Search — investigating the full catalog

Search (/search) is the forensic workspace — the widest lens on the Data Catalog. Use it when the pack is too narrow or the question precedes pack choice.

Layout

Search uses a familiar three-zone layout: Data Catalog facets on the left, results in the center, Ask & Verify on the right. On Home you only get the search box; here you get filters, scrolling match lists, and Structured Extractions tab parallel to Documents.

Regulator and document-type lists behave as session filters: they narrow Matching documents and simultaneously narrow Ask retrieval (shown under Data Catalog filters in the Ask Context strip). Multiple regulators OR together; regulators AND document types AND together.

Facets are not saved to your account unless you save a Saved Search. Reloading the page clears them unless your deployment restores session state.

Recent (catalog header) shows roughly the last 24 hours across all regulators — a lightning check before you type keywords.

Documents versus Structured Extractions

The center panel toggles between Documents (catalog rows — title, metadata, links) and Structured Extractions (obligation, enforcement, impact artifacts matching your query/facets). Investigations often alternate: find the filing in Documents, pivot to Extractions to see what the platform already structured.

Rows may offer Add to Ask & Verify and Add to Cases — bridges to Q&A and tracked work without re-finding the document later.

When Search beats Overview

Situation	Why Search
Cross-pack hunt	Pack not chosen yet or issue spans AML + Securities
Exact identifier	Docket, rule number, known URL fragment
Ad hoc keyword	Not aligned to a pack theme slug
Building a Saved Search	You need a reusable query definition

When Search beats Overview: rarely for “what’s new in our AML pack” — that is Overview’s recency model.

Example — enforcement counsel trace

Counsel remembers a CFTC advisory mentioning digital asset self-custody but not the date. They open Search, facet CFTC, type self-custody, scan Documents, open the PDF link, add to Ask, and verify one paragraph against numbered sources. If the research becomes a formal review, they Add to Cases with a title and pack assignment.

10. Cases — operating regulatory work

Cases (/workflow) is the operate workspace. Regulatory programmes fail when reading and task tracking live in different tools; Cases keeps assignment, status, and evidence on the same platform as the library.

Tabs — My Cases, All Cases, Teams

Tab	Who it serves
My Cases	Your assigned queue — daily driver
All Cases	Team-visible open work for the active team — managers and coverage reviewers
Teams	Roster, create team, invite, pack envelope (single pack vs all licensed packs)

The team switcher in the toolbar sets active team context across tabs. Personal team exists by default; shared teams support handoffs.

Queue and detail

Left rail: queue slices and search. Center/right: case detail — scorecard metrics, regulatory context, process stage, due date, owner, source links, journal entries when enabled.

This is the only place patrons get the full transition model (status changes, review steps) — not on Overview Needs Attention rows.

How Cases connect back to packs

Bridge	Meaning
Assign to me / Open in Cases (Overview)	Signal → owned work item
Track as Case (Ask)	Q&A thread anchored to a case
Add to Cases (Search/catalog)	Document set becomes a case
Create Case (Cases toolbar)	Manual intake — link, note, file

Every case carries a Domain Pack — required for licensing and filters. Cross-pack operators still see one queue; pack label tells you which programme owns the work.

Ask on Cases

Selecting a case scopes the Ask dock to that case’s linked sources and signal_id. Useful in case conference: read journal, ask “what changed in the underlying rule,” cite sources in the same pane.

Example — weekly compliance meeting

The team lead opens All Cases, filters open items for AML & sanctions, walks status on three FinCEN-related cases, assigns one to an analyst, copies a linked case to a second team’s queue (when team copy is enabled), and exports journal notes for audit. Overview was how items entered the system; Cases is how they finish.

11. Account, resources, and administration

What patrons have today

Location	What you can do
Resources → User guide	This manual in the browser
Resources → Sources map	Illustrative regulator / feed map
Resources → Send feedback	Product ideas and issues (modal)
Account (avatar) → Sign out	End session

What moved to administrators

Pack licensing, user access, saved-search alert delivery, Ask token caps, and ingest operations are operator concerns — typically /admin/users and related admin surfaces, not something compliance analysts configure themselves.

If Ask returns a monthly cap error, the message may still say “contact your administrator” — there is no self-serve usage page in the Ask dock today (usage display is disabled in the patron UI).

Ingestion health

Ingestion health (seven-day ingest summary) lives under the Admin menu for staff. If publications or Search look empty, ask your platform owner whether ingest is running — patrons do not get the admin health popover in the standard header.

Appendix — quick reference

I need to…	Start here
Orient or pick a pack	Home
Daily discipline monitoring	Domain Pack → Overview
Theme × regulator map	Domain Pack → Coverage
Keyword / cross-pack hunt	Search
Recurring query	Saved Searches
Assign and track work	Cases
Ad hoc Q&A with citations	Ask (scope follows your screen)

RegiSentinel Workbench — User Guide v2.