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

Teams

A Team is a named group of agents under a team lead. Teams make routing, reporting, and commission defaults easier to manage — instead of configuring every agent one by one, you set things up once for the team. Teams live in Brokerage Settings → Teams and are managed by brokers, admins, and team leads.

Creating a team

  1. Open Brokerage Settings and go to the Teams tab.
  2. Click Add team.
  3. Give it a name, optionally a description, and (optionally) pick a team lead.
  4. Save. The team appears in the list, ready for members.

Adding members & roles

Open a team to manage its roster:

  • Add a member — pick someone from your brokerage and add them.
  • Set a member's team role — within a team, a person is a lead or a member. Team-level roles describe their place on the team (team lead, agent, assistant, ISA, coordinator); they're separate from a person's brokerage role and from any single Realm's roles.
  • Remove a member — unassigns them from the team. Their Realm account isn't affected; they just leave the team.

Deleting a team unassigns its members — it never deletes anyone's account or their work. Members simply become team-less.

Applying defaults

A team can carry a default commission plan. The apply-defaults action pins that team's default plan to members who don't already have a commission assignment of their own.

It's deliberately non-destructive: apply-defaults never overwrites an agent's existing commission assignment. If an agent already has a plan or an override, they keep it; only members with nothing set inherit the team default. The canonical place to assign or override an individual's commission is still Commission plans.

Routing & pipeline visibility

A team carries a small Routing panel of toggles that control how it handles leads and what its members can see:

  • Team can receive leads — whether the team is eligible for routing at all. Turn it on before a routing rule can send leads here.
  • Round-robin — distribute incoming leads evenly across eligible members instead of piling them on one person.
  • Fallback assignee — the member who picks up any lead no one else takes.
  • Open pipeline visibility — when on, **every member sees the whole team's Pipeline board** (view-only on teammates' leads). Off — the default — keeps the team's Pipeline visible to the **team lead and brokers only**. Turn it on for a collaborative team where everyone should see the shared board; leave it off when agents should only see their own leads.

Why teams matter elsewhere

  • Routing — routing rules can send new leads to a whole team (e.g. round-robin across the team) rather than naming individuals. See Leads.
  • Reporting — production rolls up by team, so a team lead can see their group's numbers in one place.
  • Lead buckets — named lead groups can be assigned to teams as well as individuals.

Every team change is recorded in an append-only history, so brokers can always see who changed what and when.