Keep Skipper from changing prices without approval
There are two layers, and you control the second.
Layer one: Skipper only proposes
Section titled “Layer one: Skipper only proposes”Skipper can read prices on its own. Any change to a price becomes a proposal. It is applied only when a person presses Approve, with that person’s permissions: someone without permission to edit prices can’t apply it. You see the old and the new price before you decide. See Approve or reject Skipper’s changes.
Skipper also can’t create price lists or change a price list’s rules.
Layer two: require a reviewer
Section titled “Layer two: require a reviewer”An approval policy adds a second person. When a policy is on, a price change from anyone, including an approved Skipper proposal, waits in the approvals queue until a reviewer decides it. The price doesn’t change while it waits.
- Open Settings → Approval policies.
- Find the operation and switch it to Needs approval:
- Product price change covers a product’s base price.
- Price list rule change covers repricing a whole list.
- Customer price list assignment covers putting a customer on a list.
- Choose the Reviewer role that decides.
A new workspace starts with product price changes on; check the policy and change it if you want something different. The other two start off.
A person who holds the permission to approve applies changes directly, because they are the reviewer. If you want every price change reviewed, make sure the people who edit prices and the people who approve them aren’t the same.
Reviewers decide in Finance & team → Approvals. Someone who can’t see prices sees that a price changes, but not the amount.
An assistant you connect yourself
Section titled “An assistant you connect yourself”A Claude or ChatGPT connected through MCP follows the same policies. By default it can’t decide an approval request, and it can’t apply a change on the approval list. See Limit and revoke a connected assistant.