Getting Around: the REDA & REDA Admin Apps

REDA installs two apps, and knowing which one holds what saves you a lot of hunting. REDA is where day-to-day work happens — leases, properties, inquiries, invoices, tickets. REDA Admin is where setup and master data live — regions, charge codes, leasing rules, inspection templates. This article is the full tour: every tab on each app's nav bar with a one-line reminder of what it's for, a look at the four big record pages you'll spend the most time on, and the single most important habit in REDA — that most business operations are buttons on records, not menu items. No prior REDA experience is assumed; if you just need the raw mechanics of moving around, start with Navigation Basics and come back here for the map.

Opening the apps

Both apps open the same way: click the App Launcher — the grid icon at the top-left — and pick the one you want. REDA describes itself as "Real Estate Design & Administration"; REDA Admin as "Admin and Master Data setup for REDA." Both run on desktop and on mobile.

The REDA app opens on the Home tab, which shows the REDA Home page: an embedded dashboard alongside Today's Tasks, Pending Approvals, Recent Records, and Today's Events — a working summary of what needs your attention.

The REDA app tour

The REDA app's nav bar carries twenty-six tabs. If they don't all fit on screen, the overflow lives under a More dropdown at the end. Rather than reading them as a flat list, it helps to group them by the job they do. Here's the full set in nav-bar order, with a one-line reminder of each:

You don't need to hold all twenty-six in your head. The pattern to notice is that they run roughly from people and prospects (Inquiries, Contacts) through the assets and deals (Properties, Opportunities), into money (Opp Invoices, Commissions) and operations (Service Requests, Work Orders, Inspections, Bookings), and finish with analytics (Reports, Dashboards).

The REDA Admin app tour

The REDA Admin app carries nineteen tabs. This is where master data — the reference records everything else depends on — is created and maintained. Most leasing and sales agents rarely open it; it's home base for administrators and master-data managers. In nav-bar order:

The REDA Admin Console

The first tab in REDA Admin, the REDA Admin Console, opens a dedicated tool rather than a list of records. Inside it are two areas: Global App Settings, which holds the switches that shape how REDA behaves, and Scheduled Jobs, where recurring background jobs — the ones that produce ongoing invoices and the like — are set to run.

Anatomy of the big four record pages

Four record pages carry the bulk of REDA work — the lease, the property, the inquiry, and the ticket. Each is covered in depth in Anatomy of a REDA Record Page; here is the map of the tabs on each, with labels quoted exactly:

Buttons do the work

Here's the habit that makes REDA click: most operations are buttons on records, not menu items. You don't go to a menu to convert an inquiry or set up charges — you open the record and press the button. Two consequences follow.

First, the standard New button is replaced by a custom dialog on Inquiries and Opportunities, so creating one of those looks different from creating other records — that's expected. Second, records carry quick actions that do the real work. REDA ships thirty-three of them; a few you'll meet early:

The global create button (the + in the header) offers a few actions from anywhere too — including New Ticket, New Package / Parcel, and Request Visitor Access. And every inquiry, opportunity, ticket, booking, service request, and work order is driven along its lifecycle by a Path — thirty-one of them ship in all. Because the exact placement of a button depends on your org's layout, this article says "on the record page" rather than pointing to a corner of the screen.

What's not part of REDA

A few REDA-branded things are separate products, not tabs in these two apps — worth knowing so you don't go looking for them here:

Find it in ten seconds

The proof that you know the map is being able to reach anything in a couple of clicks. Three common jobs, traced through the nav for a team at Meridian Properties:

The App Launcher, filtered to REDA. The REDA app family appears together — REDA (the leasing app), REDA Admin, plus REDA Financials AI, REDA Financials AI - Admin, and REDA Services — along with items such as REDA Admin Console and REDA Async Logs.

The REDA Admin app's navigation bar — REDA Admin Console, then the master-data tabs: Regions, Property Types, Properties, Property Lists, Leasing Rules and Charge Codes.

The REDA Home page — a leasing dashboard in the main region, with Recent Records, Items to Approve, Today's Tasks, and Today's Events alongside. The full REDA nav bar sits across the top, with Home highlighted.

A Leasing Opportunity with its Accounting tab open — the Opp Invoices list shows the active charges, each with its charge code, billing and due dates and amount.

A Property record page — the tab set carries Leasing | PM | Booking and Sales | Acquisition tabs that gather the property's operational sub-records in one place.

An Inquiry record page — the Path runs across the top (New → Contacted → Showing Scheduled → … → Converted) and the Potential Duplicates card sits on the left (here reporting no matches found).

The REDA Admin Console, open on the Scheduled Jobs tab — the background-job catalog grouped by area, each job showing its recommended run time.

Where to go next

1. Navigation Basics in the REDA App — the App Launcher, tab bar, and search mechanics.
2. Anatomy of a REDA Record Page — reading the four zones of any record.
3. How Access Works in REDA — why you see the tabs you see.
4. REDA Permission Sets — the sets behind each role.
5. Understanding Tickets — the process engine behind so many buttons.
6. Understanding Opportunities — deals and leases in depth.

Frequently asked questions