Reviewing user permissions for price adjustments

Test pricing permissions by attempting a change with the accounts that create, approve and send quotes. Separate permission to maintain catalogue prices or pricing rules from permission to edit a single customer quote. Then check whether an unauthorised adjustment can reach the customer through another send path.

Define the people and actions

Build a small permissions matrix for a sales author, pricing administrator, approver and viewer. For each role, state whether they may change a product's standard price, edit a price rule, apply a line discount, change a quote total, approve an exception and send the result. A single “can edit quotes” setting may be too broad for that policy.

Use one fictional quote at its standard price and a second with an exception. Sign in as each test role and attempt every action in the matrix. Record the visible controls and the final saved result. A hidden field is not adequate evidence of control if a user can change the price elsewhere.

Look beyond role names

Zoho CRM documents separate CPQ permissions for viewing, creating, editing and deleting product-configuration and price rules. Those settings govern rule maintenance; they do not by themselves establish who can alter every price on an individual quote.

CRM profile permissions also cover module actions such as viewing, creating, editing and deleting records. The approval-process documentation describes what an approval process is, who can be an approver and how processes are ordered, so test the exact discount field and send action under your own configuration.

PandaDoc documents that only account owners and users with a Manager or Admin role can add a quote builder block, and lists quote builder permissions as a topic. Its column-locking controls matter to a price review. Check them in the editor and in any CRM-driven document creation route your team uses. Options shown to the recipient are a separate question from staff permission to change a unit price.

Zoho FSM documents a single Estimates permission required to work with estimates, and notes that an estimate can be accepted or rejected. If your configuration lets a staff member edit and resend an estimate, check what happens to the earlier customer acceptance and who may issue the replacement.

Make approval meaningful

Set a sample exception that should require review. Have the author request approval, the approver reject it, the author correct it and the approver accept the final version. At each step, try to send or convert the quote from every available route. Record the approved version, then repeat after changing the price again.

Keep controls proportionate. A small team may use a documented manual sign-off if the product cannot enforce its exact price policy. Whatever the method, the reviewer should see the final amount and scope, and the team should be able to show which version was approved before it was sent.

Manual vs Automated Approval Controls in Pricing