Regions

The Region is REDA's geographic backbone — the record that decides currency, defaults and visibility for everything inside it. This article is for administrators setting one up. After reading, you'll be able to create a region with the right code and currency, attach a default leasing rule, understand why the region's code shows up on records everywhere, know why currency is a choose-once decision, and recognise which save errors come from core REDA versus the website-listing add-on. No prior REDA experience is assumed.

What a Region does

A region is small but influential. It sets the currency for everything within it, it helps decide who can see which records, it can supply a default leasing rule for its properties, and it holds settings for the resident portal and showing calendar. Sitting at the top of the master-data tree, a region has neighbourhoods, property types, amenity codes, inflation rules, property lists and profit & holding rules all pointing up to it. Set the region up well and the rest of your master data has a solid foundation.

The region is also the first thing you set on a property, and for a practical reason: it filters the choices you get afterwards. Once a property's Region is set, its Neighbourhood and Leasing Rule pickers only offer records that belong to that same region — so picking the region up front is what makes the rest of the property fill in cleanly. This is why the path to putting a unit up for lease always starts with the region: no region, and the neighbourhood and rule you need aren't selectable yet. In short, the region is the gate every leasable property passes through first.

Creating a region

A region record has a short set of fields:

The region code travels everywhere

There are two things called "code" here, and it's worth keeping them straight. The Region Unique Code is the short code you type on the region itself. The Region Code is what REDA stamps from it onto the records underneath — and that stamped copy is set automatically and read-only.

When you save a property (or many other records), REDA copies the region's code onto it automatically and keeps it in step. You'll see this Region Code across roughly a dozen record types throughout the app — properties, neighbourhoods, leasing rules, portfolio memberships and more. The important habit: these copies are maintained for you and shouldn't be edited by hand (the field is filled in for you and marked not to be edited). If a Region Code ever looks wrong on a record, don't touch the code — fix the Region lookup on that record and the code re-stamps itself to match.

Currency: choose once, carefully

The region's currency is the source for the currency shown across its records. Note that its full effect only comes into play when multi-currency is switched on for your org — an org-level setting. Where multi-currency is off, the currency you pick still matters for setup, but it isn't actively converting record values.

Default Leasing Rule

A Leasing Rule is the leasing and billing policy applied to a property. A region can name a Default Leasing Rule that any of its properties fall back on when they don't specify one of their own. There's one guardrail: the rule you choose must belong to this region. Pick a rule from a different region and REDA stops you: "Invalid leasing rule. The selected leasing rule can only be assigned to the region provided on leasing rule."

Resident portal & showing calendar

Two operational settings live on the region. Turning on Resident Portal Active switches on resident-portal provisioning for the region — but you must also supply a Resident Portal User Profile Id, or REDA blocks the save: "Resident Portal User Profile Id must be provided if the region has a active resident portal." The Showing Calendar Id points to the calendar used when a showing is booked from property search. The wider mechanics of portal provisioning are covered in the administration section.

If you see "publish the region to web" errors

Worked example: the Harbour District region

Meridian Properties sets up its primary region. They create Harbour District, give it the unique code HRBD and set its currency to USD. They attach the Default Leasing Rule "Harbour District Standard" — a rule that belongs to this region, so it's accepted.

Now, when they create the unit Meridian Court #101 in this region, REDA stamps its Region Code as HRBD automatically. Later, when someone tries to switch the region's currency to another value, REDA refuses — properties already depend on it, so the currency is locked in.

The New Region form — the Information block holds Region Name and Region Unique Code, Region Currency sits on the right, and the Leasing Defaults block below carries the Default Leasing Rule lookup that new properties in the region inherit.

The Harbour District region record — its unique code (HRBD), currency, and default leasing rule, with the properties that belong to it.

Reference: region fields at a glance

Where to go next

1. Property Types — the asset kinds that sit under your regions.
2. Creating & Editing Properties — create properties in your new region.
3. Making a Property Available for Leasing — where the region and its default rule come into play.

Frequently asked questions