Key Concepts & Glossary

Every other article in this Help Center links back here when it uses a REDA term for the first time. This is the anchor: it defines REDA's core vocabulary and, more importantly, teaches the three mental models that make the whole product click — the property hierarchy, the idea that the Opportunity is the deal, and the rule that tickets drive lifecycles (so you rarely edit a stage by hand). No prior REDA or Salesforce knowledge is assumed. Read it top to bottom for a guided grounding, or jump to the A–Z glossary at the end to look up a single word.

The property hierarchy

A Property is the master record everything else in REDA hangs off — every lease, sale, acquisition, booking, work order, and invoice points back to a property. Properties nest into a hierarchy using a Parent Property link, so a unit can belong to a building or a community. A property whose type is flagged as a building/community cannot itself have a parent:

Community or Building → Unit or other non-container child

What decides whether a property is a community, a building, or a leasable unit is its Property Type — the property's classification, which carries an "Is Building/Community" flag. There are no separate record kinds on a property; its Property Type is its kind. Buildings and communities behave a little differently from units: in the Platform edition they need a Property Code; in both editions they cannot have a parent property, and they're left out of property-level rent-inflation runs. REDA enforces the first two with plain messages — try to save a building without a code and you'll see "Property Code is required for Buildings/Communities.", and try to give one a parent and you'll see "Parent property cannot be provided for building or communities."

Regions

A Region is an operating geography — think of it as a market you do business in. A region sets the currency for records under it, supplies the default leasing rule, controls who can see the records, drives resident-portal setup, and provides the showing calendar. Because regions matter so widely, REDA stamps a short Region Code onto many records automatically. You'll see region codes in a lot of places; they're written for you, not something you fill in.

The deal hub: the Opportunity is the deal

An Opportunity is REDA's single deal record. Rather than a different record for each business line, one Opportunity takes on the shape of whichever line it serves — a lease, a property sale, an acquisition, a loan, or a management engagement — and five of these shapes are active today. For leasing, the Opportunity is the lease: it carries the lease dates, the term, month-to-month and late-fee settings, the tenant, and the links between parent and child leases.

Because a lease lives on the deal record, its Stage names describe where the lease is, not where a sale is — for example Occupied - No Notice means an occupied lease with no notice to leave on file. And here's the model that trips up newcomers: many stage changes happen automatically when you complete a ticket. So you drive the lease by working its tickets, not by dragging the stage yourself.

Tickets: how things happen

A Ticket is a short, controlled checklist attached to a deal or a property, representing one step in its life — a Move In, a Move Out, a Renewal, a Lease Agreement, and so on. A ticket has its own status track — a Path of its own, distinct from the deal's stage — and finishing it moves the parent record forward. Three things about tickets are worth knowing up front:

Money: charges and invoices

Two records carry the money side, and the difference between them is the single most common point of confusion. An Opportunity Charge is the contracted charge line on a deal — either a recurring template (monthly rent) or a one-time item (a deposit). An Opp Invoice is the actual billed instance the tenant owes. In short: a charge is the plan, an invoice is the bill.

Billing is opt-in twice. A charge only produces invoices if it's flagged for invoicing and the lease is accounting-active. The vocabulary that routes and groups a charge — where it posts, how it groups, whether it's a pass-through, its grace days — comes from a Charge Code. And note the division of labor: REDA computes the charges and raises the invoices, while the accounting product (REDA Financials AI) owns tax, receipts, and the general ledger.

The unit Meridian Court #101 — its Parent Property field points up to the building Meridian Court, and the Opportunities related list shows the lease that lives on it. This parent/child chain is how the property hierarchy is made visible.

A Leasing Opportunity with the Path across the top — the lease-flavoured stages, here highlighted at Occupied - No Notice, with the Ledger Summary band just below.

A Ticket record with its status Path (Received → Handed Over) — the ticket's status is what drives this piece of the lifecycle forward.

The lease's Accounting tab, open on the Opp Invoices list — each invoice carries its charge code, billing and due dates, and amount. The Opportunity Charges (the recurring source) sit alongside in the Related List Quick Links, showing the charge-versus-invoice distinction.

Glossary A–Z

Every term uses REDA's exact on-screen label. Follow the link in each row for the full treatment.

Where to go next

1. Understanding Properties — the hub everything else hangs off.
2. Understanding Opportunities — the one deal record, in depth.
3. Understanding Tickets — the process engine behind every lifecycle.
4. Leasing Rules — the policy engine that cascades onto leases.
5. How Billing Works — charges, invoices, and what bills when.
6. Getting Around: the REDA & REDA Admin Apps — find where each of these records lives.

Frequently asked questions