Who can do what: permission sets
A permission set is a bundle of access rights in Salesforce: which records a person can see or change, which tabs and apps they get, and which buttons work for them. REDA Pay ships seven permission sets, one per role. You give each person the ones their job needs; a person can hold several, and their access is the sum of all of them.
This article lists what each set allows, which set each REDA Pay button needs, and how to assign them.
The seven permission sets
| Permission set | For | What it allows |
|---|---|---|
| REDA Pay - Admin User | Administrators | Everything: create, read, edit and delete every REDA Pay record; all setup buttons (encryption key, API token, processing-account sync, webhooks); all record buttons |
| REDA Pay - User | Staff who take payments | Create and edit Pay Customers, Pay Methods and Pay Orders; create Pay Transactions through the payment screen; read setup records (Pay Profiles, Processing Accounts, Fee Setups, logs). Uses the payment and save-a-method screens |
| REDA Pay - Transaction Manager | A refunds desk | Full access to Pay Transactions; read Pay Orders and Statement Activities. Uses Void Transaction, Refund Transaction and Sync Transaction |
| REDA Pay - Reconciliation Manager | Finance | Create and edit Statement Activities, Transaction Activities and Pay Transactions; read Pay Orders. Uses Reprocess on a Statement Activity |
| REDA Pay - Read Only User | Auditors and viewers | Read every REDA Pay record; change nothing |
| REDA Pay - Community User | Customers who log in to your Experience Cloud portal | Create and edit their own Pay Customer and Pay Methods; read their Pay Orders and Pay Transactions; read active Pay Profiles, Processing Accounts and Fee Setups. Uses the payment and save-a-method screens in the portal |
| REDA Pay - Public Site User | The guest user of your public payment-link site | Read the Pay Order behind an active link, create the single-use Pay Method and the Pay Transaction for that payment. Uses the public payment screen |
The first five give access to the REDA Pay app. The last two are for Experience Cloud users and do not.
Which button needs which permission set
| Button or screen | Where | Needs |
|---|---|---|
| New Pay Order (the payment screen), Add New Payment Method | Records, quick actions, Pay button | User (or Admin User) |
| Generate Key, Sync Failed Pay Order Transactions toggle | REDA Pay Admin tab | Admin User |
| Update API Token, Sync Processing Accounts, Setup Webhooks | Pay Profile | Admin User |
| Create Payload Customer | Pay Customer | Admin User |
| Process Pay Method, Delete Pay Method | Pay Method | Admin User |
| Process Pay Order | Pay Order | Admin User |
| Sync Transaction | Pay Order and Pay Transaction | Transaction Manager (or Admin User) |
| Void Transaction, Refund Transaction | Pay Transaction | Transaction Manager (or Admin User) |
| Reprocess | Statement Activity | Reconciliation Manager (or Admin User) |
When someone presses a button their permission sets do not cover, the dialog closes and an error message appears instead of the action running. A user who cannot see the record at all gets the message "Insufficient Access".
Recommended combinations
| Role | Assign |
|---|---|
| Administrator | REDA Pay - Admin User |
| Leasing agent or front-office staff taking payments | REDA Pay - User |
| Refunds desk | REDA Pay - User + REDA Pay - Transaction Manager |
| Finance / reconciliation | REDA Pay - Read Only User + REDA Pay - Reconciliation Manager |
| Auditor or manager who only views | REDA Pay - Read Only User |
| Portal customer | REDA Pay - Community User (see Let customers pay in your portal) |
| Public site guest user | REDA Pay - Public Site User (see Set up the public payment-link site) |
Finance gets Read Only User as well because Reconciliation Manager alone does not include read access to Pay Customers, Pay Methods, Pay Profiles and Processing Accounts, which finance opens when tracing a payment.
Assign a permission set
- Open Setup (the gear icon at the top right) and type Permission Sets in the Quick Find box.
- Click Permission Sets, then the name of the set, for example REDA Pay - User.
- Click Manage Assignments, then Add Assignment.
- Tick the users, click Next, then Assign.
The user gets the access the next time they load a page.
The seven REDA Pay permission sets, as they appear in Setup after installation.
Licences
Open Setup → Installed Packages and look at the REDA Pay row. If Allowed Licenses reads Unlimited, every user in the org is licensed and there is nothing to assign. If it shows a number, click Manage Licenses and add the users who will use REDA Pay before assigning permission sets.
Two switches on the user record
Permission sets decide what a person can open. Two checkboxes on the User record decide which direction of payment they may make:
| Field | Default | Effect |
|---|---|---|
| REDA Pay - Enable Disbursements | Off | Tick it to let this user send disbursements (pay money out). Nobody can disburse until you tick it |
| REDA Pay - Disable Receipts | Off | Tick it to stop this user taking receipts (money in) |
To change them: Setup → Users → Users, click the user's name, Edit, tick the box, Save. If the fields are not on your User page layout, add them in Setup → Object Manager → User → Page Layouts.
If a user allowed only receipts opens the payment screen with a disbursement requested, REDA Pay shows "No transfers are allowed. [Transfer Type]" instead of the payment form.
Mistakes to avoid
| Mistake | Symptom | Fix |
|---|---|---|
| Giving staff only Transaction Manager | They cannot open the REDA Pay payment screen | Add REDA Pay - User |
| Expecting the User set to cover Process Pay Order or Delete Pay Method | The dialog closes with an error | Those buttons need Admin User |
| Assigning Community User to internal staff | It is meant for portal licences and lacks the app | Use REDA Pay - User |
| Forgetting Enable Disbursements | "No transfers are allowed. [Transfer Type]" when sending a payout | Tick REDA Pay - Enable Disbursements on the user |
| Testing access as an administrator | Admins see everything, so a missing permission goes unnoticed | Test as a user who holds only the set you are checking |
FAQ
Yes. Access adds up, so a refunds desk user holds both REDA Pay - User and REDA Pay - Transaction Manager.
Process Pay Order sends an existing order for processing from the record page, which is an administrator action. Staff process payments through the payment screen, where the Pay button does the same job.
They need REDA Pay - Community User and the portal set-up described in Let customers pay in your portal; check Installed Packages for the licence model as described above.
Where to go next
- Setup roadmap — the full order of setup steps.
- Generate the encryption key — the first setup step, which needs REDA Pay - Admin User.