The REDA Admin Console

If you're setting REDA up, this is where you start. The REDA Admin Console is the administrator's control tower — one screen with two areas: scheduling REDA's background jobs, and REDA's application-wide settings. This article is the tour of the whole Administration section: it shows you the two REDA apps, the console and its two areas, and a map of which setup tab configures which part of the product, with a link to the detailed article for each. It maps the territory; the deeper articles walk it. No prior REDA experience is assumed.

What the REDA Admin Console is

The REDA Admin Console is a single tool inside the REDA Admin app, and it does exactly two things:

• Scheduled Jobs — schedule and abort the background jobs that produce REDA's recurring invoices, late fees, inflation adjustments, and more.
• Global App Settings — REDA's application-wide settings.

It's important to see what the console is not. The console sits first in the REDA Admin app's navigation, beside the ordinary setup tabs — Regions, Charge Codes, Leasing Rules, and so on. Those tabs are not "inside" the console; they're their own tabs. The console covers jobs and app settings only. We'll map every setup tab below.

The two apps, one minute

The REDA Admin app — where you configure rather than operate. The navigation bar is the tell: Regions, Property Types, Property Lists, Leasing Rules and Charge Codes are the master-data tabs, with the Console sitting alongside them. Below the nav, the Console looks the same from either app.

REDA ships as two apps, and knowing which is which saves confusion on day one:

You do the actual property work in REDA. You configure the product in REDA Admin. The Properties tab appears in both apps — it's the same tab with a second home, so you can reach properties whether you're operating or configuring; there's only one set of property records behind it.

The two console areas

Open the REDA Admin Console and you'll see two tabs inside it.

Scheduled Jobs

This is where you schedule and abort REDA's background jobs. It matters more than it sounds: a fresh REDA org ships with none of its billing jobs scheduled, so scheduling them here is a mandatory go-live step. When you abort a job, REDA confirms with "Abort this scheduled job? Future runs will stop immediately. In-flight executions complete normally." The full catalog of jobs, sensible times, and what breaks if you skip one are covered in Scheduling Background Jobs — read it before go-live.

Global App Settings

This area holds REDA's application-wide settings. See Global App Settings for what it controls, including the batch-size settings the scheduled jobs read.

Where every setup tab lives

The REDA Admin app's navigation lists the console first, then the setup tabs. Here's what each one configures, who can touch it, and the article that covers it in depth. As a rule, each setup object is documented where users actually feel it — Leasing Rules in Leasing, Charge Codes in Billing, inspection setup in Property Management — so this table is the map, and those articles are the territory.

A couple of notes from the map. Settlement Codes is the one setup catalog an operational role (Acquisition) can edit; every other setup tab is Master Data Admin's to change. And Email Templates, Reports, and Dashboards are granted by your Salesforce administrator outside REDA's own permission sets — no REDA set includes the ability to run reports at runtime.

The access model, briefly

Two permission sets frame the whole Administration section:

• REDA - Master Data - Admin — the administrator's set. It's the only set that includes the console, and it's the set that can change master data across the product.
• REDA - Master Data - Read Only — the auditor's twin. It can view the master-data tabs but not change them, and it does not get the console.

REDA has no packaged bundles that pre-group these into named "roles," so persona bundles are an implementation decision. When asking for access, say "please assign me REDA - Master Data - Admin," not "my role should include it."

A first walk through REDA Admin

A newly assigned administrator at Meridian Properties is given the REDA - Master Data - Admin set and opens REDA Admin for the first time. They walk the navigation top to bottom: the REDA Admin Console first (seeing its two tabs, but scheduling nothing yet), then confirm the master data is in place in the order the rest of the product depends on it — Regions, then Charge Codes, then Leasing Rules, then Property Types and Amenity Codes, then Properties. With that foundation confirmed, they return to the console to schedule the background jobs before go-live.

The App Launcher open and searched to "REDA": the REDA apps are listed together — including REDA Admin — alongside the REDA Admin Console and REDA Async Logs items.

The REDA Admin app navigation bar — the REDA Admin Console is the first item, ahead of the master-data tabs.

The REDA Admin Console, open on Global App Settings — its two internal tabs (Global App Settings and Scheduled Jobs) sit under the console header, which warns that changes apply across the org.

Where to go next

1. Scheduling Background Jobs — the go-live-critical area; schedule these or billing silently won't run.
2. Global App Settings — the application-wide settings, including batch sizes.
3. REDA Async Logs — how to monitor what the jobs did each night.
4. Setup Roadmap — the order to configure master data in.
5. Go-Live Checklist — everything to confirm before you switch on.

Frequently asked questions