The compliance hub is where you check obligations across every deal and your own program in one page, rather than opening a file to find out. Four sections sit behind one pill row: Deal state, Checks, Setup and Exports. Picking a section lands you on its first view, and a section holding only one screen skips the second row of tabs entirely rather than opening a submenu with nothing to choose between.
When You'd Use This
Open the hub whenever a question is about the whole book rather than one file - which deals still owe something, what's sitting in a review queue, what your program requires, or the record you'd hand a regulator. A single deal's own compliance tab still covers that one file in full; the hub is where the same questions get asked across everything at once.
Deal State
This section holds the cross-deal queue: every active file plotted against what it still owes across identity, consent, disclosures, and suitability. See Where Every File Stands covers working it in depth.
Checks
Four queues live here: AML screening, identity verification, disclosures, and suitability. Each is narrower than the Deal state roll-up - not "does this file owe something" but "what needs a person to look at it and decide." Identity review surfaces verifications flagged for review and lets a reviewer approve or reject them. Disclosures runs the same evaluator that blocks a transmit, checked against a deal's real facts - when the lender was selected, when a commitment came in, the expected signing date - so what you see here can't disagree with what actually stops a file moving.
Setup
This is where the program's standing configuration lives: the disclosure rulebook (turn a requirement on or off, override its waiting period), custom brokerage or team requirements, lender-specific disclosure profiles, the prepared-document and evidence-document catalogs, and closing-package templates. What a team can add to its own library, versus what the brokerage owns outright and locks, is marked on every row - see Add Your Own Compliance Requirement.
Exports
Exports sits apart from Setup on purpose: a compliance export is something you go do on a schedule, not a setting you configure once. Build a stamped, hash-verified export scoped to one file, one client, or the whole book, and watch its status while a book-wide build runs in the background.
What To Watch Out For
- Deal state shows no second row of tabs - it's the one section holding a single screen, so the section pill is the whole navigation there.
- Links elsewhere in the product that point at a specific view (like
?tab=amlfrom a task or an alert) still land correctly. The view names didn't change when sections were introduced; only what the URL parameter now belongs to did.
What to Do Next
- See Where Every File Stands to work the cross-deal queue.
- Check What a File Will Owe to preview obligations before a deal exists.
- Add Your Own Compliance Requirement to add a firm-wide rule.
- Review Compliance Across the Brokerage for the brokerage-wide console this hub feeds into.