This is the same guide agents use inside REALM.Get REALMLog in
The Complete Guide

The REALM Guide

Everything Realm does, and how to use it. The full handbook: every feature, with step-by-step instructions. Use the contents on the left to jump to a chapter.

97Chapters
15Product areas

Compliance overview

Compliance in Realm is about making sure each Realm has the right documents, signatures, and approvals — and, where your brokerage runs its own compliance, that a broker signs off before things move forward.

A key idea: compliance is attachable, not assumed. How much Realm enforces depends on how your Workspace is governed. For a solo agent it's light and informational; for a brokerage that owns compliance, it's a full review-and-approval flow.

Governance types — who has compliance authority

Every Workspace has a governance type that sets the tone:

  • Self — you run your own compliance (a solo independent agent). Requirements are informational — Realm tracks them, nothing hard- blocks.
  • External — compliance lives with an outside brokerage or system (for example, a team at a national brand). Requirements show as an advisory checklist. EVE can nudge, but Realm doesn't hard-stop the transaction.
  • Native — your brokerage owns compliance inside Realm. This is full enforcement: blocking requirements gate stage changes and closing, and a broker reviews and approves documents.

Governance type, your Workspace type, and which compliance system you use are three separate things. A team can be "external" governance even inside a brokerage Workspace. If you're unsure which applies to you, ask your broker or admin.

Advisory vs enforced

The same requirement behaves differently depending on governance:

GovernanceWhat a blocking requirement does
SelfInformational only
ExternalAdvisory checklist; EVE may nudge
NativeHard-gates the stage / closing until satisfied

This is why a Transaction Template can mark a requirement as "blocks progress" and have it gate a native brokerage's transaction while staying advisory elsewhere — the Transaction Template describes intent, governance decides enforcement.

The Compliance surface

Brokers and team leads get a Compliance entry point regardless of governance type — having the nav doesn't mean enforcement is on. The surface adapts:

  • Native shows the full broker review queue and document approval flow.
  • External shows the advisory checklist.
  • Self shows minimal state.

The broker review queue lives in the workspace shell (Realms in compliance mode); the admin tools — packs, rules, certifications, activity feed, archived Realms — live under Brokerage Settings.

In this section