What Access Do I Need?

This is the fast lookup for REDA access. You have a specific job to do — schedule a work order, edit a lease's charges, post a reconciliation batch — and you need to know the exact permission set to ask your administrator for. Find your task or screen in the tables below, read off the set name, and send it in your request. This article is the task-first companion to Permission Sets & Personas: that article explains the model set-by-set ("what does this set grant?"); this one indexes it the other way ("what do I need for this task?"). The verified facts are the same in both — only the direction of lookup differs.

How to read the tables

Every table names the full permission-set label exactly as your administrator sees it — for example REDA - Property Leasing User — including the spaces around the dashes. Send that label verbatim and there's no ambiguity about which set you mean.

Most feature areas ship in three tiers. An Admin or User set lets you create and edit; a Read Only "twin" lets a colleague view the same records without changing them. So if a viewer on your team only needs to look, ask for the Read Only twin rather than the full set. Not every set has a twin — the field-work sets (Work Order, Inspection) grant the work directly and have no view-only version. Deleting is rarer than editing by design: on the core records, the operational sets let you create and edit but not delete, and delete is reserved for administrators.

You can hold more than one set, and they simply add together — your access is everything all your sets grant, combined. If your job spans two areas (say you both schedule work orders and run inspections), you ask for both sets rather than looking for a single set that covers both. So when the tables below point one task at one set and another task at a different set, that's your answer: request each set that a task you do lands on.

Lookup: the REDA app

These are the day-to-day operational screens — the tabs you reach through App Launcher → REDA. Find the screen, read across to the set that grants what you want to do.

Lookup: the REDA Admin app

These are the setup and master-data screens — reached through App Launcher → REDA Admin. Almost everything here is maintained by administrators; most operational sets can view but not change it.

The Inflation Adjustment User set is worth calling out: it can run inflation adjustments and update rent setups, but it cannot edit the Inflation Rules themselves — only REDA - Master Data - Admin can.

Lookup: common buttons and actions

Most work in REDA happens through a button on a record — Convert Inquiry, New Booking, Post/Unpost Batch. Here are the most-asked actions and the access each one needs. Where a row is marked (action), the button is one your administrator additionally enables at the organization level — having the REDA set alone is not always enough (see the note that follows the table).

Access your administrator grants separately

Some things are deliberately not part of any REDA permission set, and no REDA set will ever grant them. Your administrator sets these up separately, alongside your REDA access:

When you're blocked

REDA has two messages you'll meet when access is the problem. Learn to recognize them — the message plus your task is exactly what your administrator needs to fix it.

This is REDA's most common access block. It means your assigned sets don't cover the record or action you attempted. Find your task in the tables above, and send your administrator the set label plus what you were trying to do.

This one usually means a screen component is misconfigured or a required privilege is missing behind a button. Retry once; if it persists, send the exact wording to your administrator.

Worked example: Priya's field-work access

Priya handles maintenance for Meridian Properties: she schedules and completes work orders and runs move-in inspections. Working down the tables, her tasks land on two sets:

Her manager only reviews the work and never changes anything, so the instinct is to hand the manager a view-only twin. Here's the nuance: the Work Order and Inspection sets are field-work sets with no Read Only twin. To give the manager a look without edit rights, your administrator uses the organization's own view-only sharing rather than a REDA twin. Twins exist for many domains — Master Data, Invoice Management, Booking, Service Request, Portfolio, Council Management, Expense Reconciliation, and Commission — just not for the doer sets.

Where to go next

1. Permission Sets & Personas — the full model, every set explained, and role bundles.
2. Getting Around: the REDA & REDA Admin Apps — where each screen actually lives.
3. The REDA Admin Console — the Master Data Admin's setup and jobs surface.
4. Key Concepts & Glossary — the vocabulary behind every table here.

Frequently asked questions