Home/HighLevel/Features/Payments/How to assign user permissions for payment modules in HighLevel

Payments and Sales

How to assign user permissions for payment modules in HighLevel

In short

User permissions for payments in HighLevel are divided into six modules, Orders, Subscriptions, Transactions, Taxes, Products and Payment Settings. Each module offers toggles for view, create, update, delete, export and configure actions, letting admins grant precise access to staff while built in safeguards enforce required dependencies.

AreaPayments · Getting Started with Payments
Used forDigital marketing agency, Online retailer, Subscription based service
Setup steps6 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners can limit team members from issuing refunds or altering subscription details.
  • SaaS Founders can allow product managers to create and bulk manage items without exposing payment configuration settings.
  • Accounting teams can view and export transaction records while preventing changes to order collection processes.

02Payment permissions, explained

The permission system splits payment related rights into six distinct sections. For each section, admins can turn on or off actions such as view, create, update, delete, export and configure. This granularity replaces the previous single Payments block.

When a permission that another action relies on is missing, the platform automatically disables the dependent option. For example, bulk product actions are unavailable unless the Create/Edit toggle is active. The new layout works together with any existing generic Payments permissions.

All settings are located under Settings > My Staff. After choosing a staff member and clicking the Edit icon, the Roles & Permissions screen displays the six payment modules where the toggles can be adjusted.

03How businesses use payment permissions

  • Digital marketing agency. The agency can give media buyers permission to collect payments on orders while restricting them from editing tax settings or processing refunds. This is done by enabling view and collect actions in the Orders module and leaving other modules unchecked.
  • Online retailer. A retailer can let inventory staff create and edit products, duplicate listings and run bulk updates, but only after granting the Create/Edit permission in the Products module. The staff member’s access is set by checking the appropriate boxes in the Products section.
  • Subscription based service. The service can assign support agents the ability to pause, resume or cancel subscriptions without allowing them to change payment gateway settings. Agents receive the needed rights by selecting the relevant actions in the Subscriptions module while leaving Payment Settings untouched.

04Before you start

  • Permission to edit staff roles in Settings > My Staff must be granted.
  • A clear plan for which staff members will handle each payment module is required.
  • At least one staff member or role must exist to receive the new permissions.

05How to set up and use payment permissions in HighLevel

Assign payment permissions to a staff member

  1. Navigate to Settings > My Staff.
  2. Click the Edit icon beside the staff member you wish to modify.
  3. Open the Roles & Permissions panel.
  4. In each payment module, tick the actions the staff member should have.
  5. Ensure any required base permissions are enabled for bulk actions.
  6. Click Save to apply the changes.

06What it looks like in HighLevel

07Settings that matter

  • Orders. Controls rights to view, export, import and collect payments, including partial payments.
  • Subscriptions. Manages abilities to create, modify, pause, resume, cancel, export and update payment methods.
  • Transactions. Sets permissions for viewing, refunding, exporting, importing and downloading receipts.
  • Taxes. Allows viewing and configuring tax settings, adding or deleting manual rates, and toggling automatic tax calculation.
  • Products. Governs viewing, creating, editing, importing, duplicating, bulk managing and deleting product records.
  • Payment Settings. Enables configuration of receipts, subscription defaults and other platform payment options.

08Things to know before you rely on it

  • Former generic Payments permissions have been reorganized into the six new modules.
  • Dependent actions are automatically disabled when required base permissions are missing.
  • Bulk product management cannot be used without granting Create/Edit permission.

09If something goes wrong

  • Bulk Manage Products remains disabled after being selected.. Enable the Create/Edit permission for the Products module; the bulk option will then become available.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

If you are wondering whether splitting payment permissions into six sections makes sense, it lets you keep high risk actions such as refunds, tax tweaks and product changes limited to the right people while allowing sales staff to handle routine work.

I’d start by giving front line team members just Orders view and collect payment rights, and keep Subscriptions and Payment Settings for senior staff, so day to day flow stays smooth and high risk actions stay locked down.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about payment permissions.

What happens if I enable Bulk Manage Products without Create/Edit permission?

The platform automatically disables the bulk option until the Create/Edit permission is granted.

Where can I find the new payment permission sections?

Open Settings > My Staff, edit a staff member, and select Roles & Permissions to see the six payment modules.

Can I apply Assigned Data only permissions to payment modules?

Yes, the interface allows you to set Assigned Data only permissions alongside the payment actions.

Do the original Payments permissions still work after this redesign?

The new modules exist alongside the primary Payments permissions, so existing settings remain active.

How are dependent actions handled when a required permission is missing?

The system automatically disables any action that relies on a missing base permission.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.