Skip to main content

How do I use Elevate Permissions in Pavilion?

Learn how to temporarily grant higher access in Pavilion for actions that require manager approval, such as applying larger discounts, editing closed orders, processing refunds, or voiding receipts.

Elevate Permissions lets an authorized user temporarily approve actions that are outside another user’s normal access level.

This is useful when a team member needs approval for something like:

  • Applying a discount above their limit

  • Editing a closed order

  • Canceling an order

  • Processing a return or refund

  • Voiding a receipt

Instead of permanently changing a user’s role, a manager or authorized user can enter their PIN to temporarily grant the needed permission.

Set up a user PIN and maximum discount

Before users can grant or receive elevated permissions, a PIN must be configured for each manager or authorized user.

You can also set a Max Allowed Discount for each user.

  1. Open the App Launcher.

  2. Search for User Management.

  3. Open the User Management tool.

  4. Find the user you want to update.

  5. Click the dropdown icon next to the user’s name.

  6. Click Edit.

  7. Enter or update the following fields:

    • PIN: Used to authorize elevated permissions.

    • Max Allowed Discount: Sets the highest discount this user can apply.

  8. Click Save.

ℹ️ The Max Allowed Discount value is ignored if the user already has the Change Inventory Sale Price permission, since that permission allows unrestricted price changes.


Elevate permissions

Once PINs and permissions are configured, an authorized user can grant elevated access when needed.

  1. On a Pavilion page that supports elevation, press:

    • Ctrl+K on Windows

    • Cmd+K on Mac

  2. The Elevate Permissions window will open.

  3. Select the authorized user who will approve the action.

  4. Enter that user’s PIN.

  5. Click Authenticate.

  6. Select the permissions to temporarily enable.

  7. Set a Duration for how long the elevated access should remain active.

  8. Click Grant Permissions.

ℹ️ Elevated permissions work on the page where you activated them and in POS. Since POS is available everywhere, the same permissions will also apply there. If you refresh the page or the timer runs out, the permissions will be removed automatically.


Available permissions

The permissions available for elevation depend on your organization’s setup. Common elevated permissions include:

Permission

Description

Manage Inventory Adjustments

Edit or modify inventory adjustments.

Adjust Customer Balances

Manually update customer account balances and store credit.

Cancel Orders

Cancel sales, jobs, layaways, and special orders.

Change Inventory Sale Price

Set custom sale prices when adding inventory items to orders or POS.

Change Orders Associates

Modify assigned sales associates and commission shares on orders that already have receipts.

Change Tax

Select or change the tax group applied to line items and orders.

Do Giveaways and Donations

Mark sale line items as giveaways or donations.

Edit Closed Orders

Edit previously closed or finalized orders, including line items and shipping details.

Include Tax

Add the option to include tax in item or order pricing.

Process E-Commerce Refunds

Process automated refunds for e-commerce orders through payment gateways.

Process Returns

Process returns and refunds for sold items.

Return Expired Sales

Process returns for sales beyond the standard return period.

View Costs

View item cost details across inventory and sales screens.

Void Closed Orders Receipts

Void receipts for closed and finalized orders.

Void Receipts

Void receipts for open orders.


Permission combinations

Some actions require more than one permission. If only one permission is granted, Pavilion may still block the action.

Common examples include:

Action

May also require

Process e-commerce refunds

Process Returns

Cancel orders

Edit Closed Orders, depending on the order status

Void closed order receipts

Void Receipts

⚠️ Always ensure that dependent permissions are granted together when performing these actions, otherwise the system may block the operation.

Did this answer your question?