Permission Sets & Personas
This is the administrator's map of REDA access. Whether you're planning who gets what at implementation, or answering a "why can't Priya edit invoices?" ticket, this article gives you the whole picture: the 31 permission sets REDA ships, the naming pattern that makes them predictable, which set each of the common roles receives, and — just as important — the access REDA deliberately does not grant, so you know what to set up separately. It's the model-first companion to What Access Do I Need?: this article answers "what does this set grant?"; that one answers "what do I need for this task?". Same verified facts, indexed both ways.
Access you'll need. Assigning permission sets is a system-administration task in your organization — it is not itself a REDA permission set. You need administrator rights in your org to make assignments.
How REDA access works
Everything is a permission set — a named bundle of rights an administrator assigns to a user. There are no packaged "role" bundles that combine several sets for you: REDA ships the individual sets, and you decide which combination each person gets. That means you always phrase access as an assignment — "assign this person the REDA - Property Leasing User set" — never as something a role automatically includes.
No REDA set grants blanket "view all" or "modify all" rights over its records. Access is scoped to the records the set is for. And because personas are your decision, not a shipped feature, the role recommendations later in this article are exactly that — recommendations you adapt to how your team is organized.
Sets add up. When you assign someone more than one set, their access is the sum of every set — the widest grant wins on each record. So a person who holds both REDA - Booking Admin and REDA - Property Leasing User gets the full booking desk and the leasing operations, not a blend or a conflict. This is why the personas below are built by stacking small, single-purpose sets rather than reaching for one broad set: give each person exactly the sets their job needs, and nothing more.
The naming pattern
Every set follows the shape REDA - [Domain] - [Tier], and once you see the pattern you can predict most of them:
A few domains break the twin pattern on purpose. The field-work sets — REDA - Work Order User and REDA - Inspection User — grant the work directly and have no Read Only twin, and REDA - Inspection Manager is the setup-and-execution set for inspections rather than a view-only version of the User set.
The 31 permission sets
Here is the full set, with a one-line scope summary and its view-only twin where one exists. Labels are exact — assign by the label shown.
| Permission set | What it grants | View-only twin |
|---|---|---|
| REDA - Master Data - Admin | The administrator set: all master data and operations, and the only set with REDA Admin Console access | REDA - Master Data - Read Only |
| REDA - Master Data - Read Only | View all master data (the auditor set) | — (is the twin) |
| REDA - Property Leasing User | The broadest operational set: lease lifecycle, charges, invoices and batches, visitor logs, work orders | — |
| REDA - Property Sales User | Sales pipeline plus payment plans, milestones, and schedules | — |
| REDA - Property Acquisition User | Acquisition pipeline; may also edit Settlement Codes | — |
| REDA - Property Management User | Property-management operations; includes the Property Search - Leasing tab | — |
| REDA - Property Lending User | Loan servicing (loan payments) | — |
| REDA - Invoice Management Admin | Full invoicing: invoices, batches, and charges | REDA - Invoice Management Read Only |
| REDA - Invoice Management Read Only | View invoicing | — (is the twin) |
| REDA - Booking Admin | Full booking desk | REDA - Booking Read Only |
| REDA - Booking Read Only | View bookings | — (is the twin) |
| REDA - Service Request Admin | Manage service requests | REDA - Service Request Read Only |
| REDA - Service Request Read Only | View service requests | — (is the twin) |
| REDA - Work Order User | Field maintenance: work orders | — |
| REDA - Inspection Manager | Inspection setup and execution: templates, masters, locations, inspections | — |
| REDA - Inspection User | Perform inspections; view-only on the setup catalog | — |
| REDA - Commission Manager | Manage commissions and commission rules | REDA - Commission User Read Only |
| REDA - Commission User | Work your own commissions; view rules | — |
| REDA - Commission User Read Only | View all commission data | — (is the twin) |
| REDA - Portfolio Management Admin | Investor portfolios, full access | REDA - Portfolio Management Read Only |
| REDA - Portfolio Management Read Only | View portfolios | — (is the twin) |
| REDA - Council Management Admin | Full HOA / council management | REDA - Council Management Read Only |
| REDA - Council Management Read Only | View council data | — (is the twin) |
| REDA - Expense Reconciliation Admin | Run CAM / expense reconciliation | REDA - Expense Reconciliation Read Only |
| REDA - Expense Reconciliation Read Only | View reconciliation | — (is the twin) |
| REDA - Inflation Adjustment User | Run inflation adjustments and update rent setups; view rules but cannot edit them | — |
| REDA - Property Analytics | Straight-line schedules and reconciliation snapshots | — |
| REDA - Content Plus - User | End-user access to the Content Plus app (upload and manage files and tag them as Content Plus) | — |
| REDA - Duplicate Management User | Review and manage duplicate records | — |
| REDA - Ads Integration | The Google & Meta ads connector: the Ad Account object and its fields, the connect/disconnect and conversion-target Apex, the Ad Accounts tab, and read access to the inquiry's ad-attribution fields. Assign it to whoever runs the connector. | — |
| REDA - Email Integration | The inbound email router: the email-service Apex, the Omni Inbox contact fields, and the Unmatched Email triage object and tab. Assign it to the Email Service run-as user and to email administrators. | — |
The two special sets
Two sets sit apart from the domain pattern. REDA - Master Data - Admin is the administrator set: it grants full access across REDA's master data and operational records — properties, opportunities, regions, charge and amenity and settlement codes, leasing, commission, and inflation rules, payment plans, invoices, promotions, property types and lists, rent setups, snapshots, straight-line schedules — and it is the only set that opens the REDA Admin Console. Anyone without it who tries to use the console sees:
Its mirror is REDA - Master Data - Read Only — the same breadth, view-only. That's the set for an auditor or analyst who needs to see everything and change nothing.
Personas: who gets what
Because REDA doesn't ship role bundles, here is a recommended starting point for the common roles. Treat these as a template you adapt — assign the set (or sets) that match what each person actually does.
| Role | Recommended set(s) |
|---|---|
| Leasing agent / leasing office | REDA - Property Leasing User |
| Sales agent (unit or property sales) | REDA - Property Sales User |
| Acquisition analyst | REDA - Property Acquisition User |
| Lending / loan officer | REDA - Property Lending User |
| Property manager | REDA - Property Management User (add REDA - Service Request Admin if they triage requests) |
| Accountant / billing clerk | REDA - Invoice Management Admin (or Read Only) + REDA - Expense Reconciliation Admin + REDA - Property Analytics as needed |
| Inspector / inspection supervisor | REDA - Inspection User or REDA - Inspection Manager |
| Maintenance tech / dispatcher | REDA - Work Order User + REDA - Service Request Admin |
| Front desk / booking coordinator | REDA - Booking Admin (or Read Only); add REDA - Property Leasing User for packages and visitors |
| Commission administrator / broker | REDA - Commission Manager, Commission User, or Commission User Read Only |
| HOA / council manager | REDA - Council Management Admin (or Read Only) |
| Portfolio / investment manager | REDA - Portfolio Management Admin (or Read Only) |
| REDA system administrator | REDA - Master Data - Admin |
| Auditor / analyst (read-only) | REDA - Master Data - Read Only |
| Add-on capabilities | REDA - Content Plus - User, REDA - Duplicate Management User, REDA - Inflation Adjustment User |
What REDA does not grant
This is the part administrators miss most often. Some access is deliberately outside the REDA sets, and you grant it separately:
The practical takeaway: a REDA set is only ever part of a working setup. Alongside it, plan the person's Account and Contact access, their report access, and — for anyone who runs the guided-action buttons — the organization-side run access those buttons need. A leasing agent with REDA - Property Leasing User and nothing else can open the lease but not the tenant's contact record; that is expected, and it is the organization-side grant that closes the gap.
Create, edit, and delete at a glance
A summary of who can do what to the core records. V = view, E = create and edit, F = full including delete.
| Record | Master Data Admin | Leasing User | Sales / Acq / PM / Lending Users | Invoice Mgmt Admin | Read-Only twins |
|---|---|---|---|---|---|
| Opportunity (deal / lease) | F | F | E | V | V |
| Property | F | V | E | — | V |
| Inquiry / Ticket | — | E | E | — | — |
| Opportunity Charge | F | F | E (Acq / PM / Lending) | F | V |
| Opp Invoice & Batch | F | F | — | F | V |
| Booking | — | — | — | — | V (Booking Read Only) |
| Service Request | — | — | — | — | V (Service Request Read Only) |
| Work Order | — | F | — | — | — |
| Inspection (and items) | — | — | — | — | — |
| Commission | — | — | — | — | V (Commission Read Only) |
| Portfolio | — | — | — | — | V (Portfolio Read Only) |
| Master data (regions, codes, rules) | F | V (Leasing Rules only) | E (Settlement Codes, Acquisition only) | — | V (Master Data Read Only) |
A few headline rules are worth stating flat: Opportunity delete belongs to REDA - Master Data - Admin and REDA - Property Leasing User only; Property delete is Master Data Admin only; invoices and batches can't be deleted by anyone once posted ("This Opp Invoice cannot be deleted."); tickets have no delete for anyone; Settlement Codes are the one setup record an operational set (Acquisition) can edit; and leasing agents can read Leasing Rules while only Master Data Admin changes them.
Worked example: staffing a demo company
Meridian Properties is bringing six people onto REDA. Here's the assignment plan — and the reminder that each person also needs organization-side access to Accounts, Contacts, and reports granted separately.
| Person | Role | Sets assigned |
|---|---|---|
| A | Leasing agent | REDA - Property Leasing User |
| B | Property manager | REDA - Property Management User (+ REDA - Service Request Admin if triaging) |
| C | Maintenance tech | REDA - Work Order User + REDA - Inspection User |
| D | Accountant | REDA - Invoice Management Admin + REDA - Expense Reconciliation Admin |
| E | Front desk | REDA - Booking Admin (+ REDA - Property Leasing User for packages and visitors) |
| F | REDA administrator | REDA - Master Data - Admin |
Where to go next
- What Access Do I Need? — the task-first lookup users send you when they're blocked.
- Getting Around: the REDA & REDA Admin Apps — where each set's tabs live.
- The REDA Admin Console — the console only Master Data Admin can open.
- REDA Editions: Platform vs Sales Cloud — how the set list differs between editions.
Frequently asked questions
The message "Insufficient Access" means their assigned sets don't cover what they attempted. Ask what they were trying to do, look it up in What Access Do I Need?, and assign the matching set.
Standard-object access isn't part of any REDA set — grant Accounts and Contacts from your organization's profiles or your own permission sets, alongside the REDA set.
Invoice deletion is blocked by design for everyone: "This Opp Invoice cannot be deleted." This protects the billing record once it exists — there's no set that overrides it.
REDA - Master Data - Admin is the widest — all master data and operations, plus the Admin Console. Even so, standard objects, reports, and the guided-action buttons still need organization-side grants.
Only REDA - Master Data - Admin. Anyone else sees "You do not have permission to perform this action in the REDA Admin Console."
The labels are identical. The main difference is that some sets are specific to the platform edition — see REDA Editions: Platform vs Sales Cloud for what varies by edition.
Was this article helpful?