Legacy IDs are the link between a record in BrokerBridge and its corresponding record in one of the three legacy systems (DLC, MCC, or MA). The link works for every user type: franchise, team, and person. Why Legacy IDs matter The legacy systems do not disappear the moment BrokerBridge launches. They continue to hold history, records, and reference data that other systems read from. Legacy IDs make sure that the same person, team, or franchise in BrokerBridge is recognized as

New articles, walkthroughs, and short videos are on the way. Bookmark this page and check back. Material will be published here as each piece is ready, starting with content for Owners and Team Leads.

New articles, walkthroughs, and short videos are on the way. Bookmark this page and check back. Material will be published here as each piece is ready, starting with content for Owners and Team Leads.

By this point in the series, you have worked through what Broker Bridge is, how to navigate it, and how the hierarchy is structured. You have also walked through the workflows for creating Persons, Franchises, Teams, and Sub-teams, and for transferring people between franchises. You have seen how the platform behaves across each of those workflows. This article pulls back from the individual workflows and distills the rules that govern all of them. These rules are not feature

Transfers happen for a range of reasons. A broker leaves one franchise and joins another. A person takes on a new role that requires a different team association. A correction needs to be made to where someone sits in the network structure. The reason changes, the workflow does not. Before You Start Broker Bridge surfaces a reminder at every step of the transfer flow, and it is worth taking seriously. The person being transferred should have already consulted with their curre

A Team in Broker Bridge is the structural container that holds people inside a franchise. Every franchise must have at least one team. A franchise cannot directly hold people. Even a brokerage with a single broker and no formal organizational structure needs a team record. This is a hard rule built into the platform. Sub-teams are an optional layer. A team uses sub-teams when it needs internal divisions, often by physical location, specialty, or reporting line. A person can s

A Franchise in Broker Bridge represents a brokerage that operates under one of the three DLCG networks: DLC, MA, or MCC. The franchise record is the structural container that holds Teams, Sub-Teams, and the people who work inside them. It carries the brokerage's licence information, contract details, and the network applications and communications the franchise participates in. Franchise creation is restricted to Admin users. Unlike Person creation, which is available to broa

A Person record in BrokerBridge represents an individual inside the DLCG network. This includes licensed mortgage agents, brokers, principal brokers, broker owners, administrators, assistants, and any other staff member who needs to exist in the platform. Creating a Person is foundational. Until a Person record exists, they cannot be associated with a franchise. Many other BrokerBridge workflows depend on Person records already being in place, including franchise creation its

The first article in this series explained what Broker Bridge is. The second covered how to move around the platform. This third document covers the structure that everything in Broker Bridge sits on top of: the hierarchy. For Ops, this is the most important concept in the platform. Every record you create, status change you make, or support question you answer comes back to hierarchy. If you understand how the structure works, you can answer almost any "where does this perso

Broker Bridge looks busy at first, but the layout repeats across every page. The same elements sit in the same places whether you are on Manage Franchise, Manage Team, or Manage Person. The platform also has two built-in learning features that explain every clickable element to you on the fly. Once you know those exist, navigating the rest is mostly recognition. This article covers the layout, the two learning features, and the three main record pages where Ops spends most of