Overview
An approval process is a structured workflow that reviews and authorizes an action before it takes effect. When a user does something that falls inside the rules you set, the action is held as a request until someone with the authority to decide approves or rejects it.
It exists so that self-service does not mean losing control of what your customers buy.
Why use it
Governance
You decide in advance which actions need a second pair of eyes, above what value, and for which roles. The rules are explicit and configured per customer, so a large account can move freely while a new one is held to tighter limits. Nothing depends on remembering to check.
Oversight
Every request carries the full picture: who asked, in which role, for which subscription, at what price, and when. Decisions are recorded with an optional comment back to the requester, so there is a trail of what was allowed and why. Requests that were cancelled or rejected stay visible alongside the approved ones.
Oversight also works inward. Triggers apply to your own staff as readily as to customers, so Key Account Managers and Sales Agents can be held to the same guardrails, and can be set to review each other's actions without ever approving their own.
Self-service confidence
The point of a guardrail is to let people move. With an approval process in place you can open the catalogue to your customers and let them buy, change and cancel on their own, because anything that matters comes back to you first. Everything below the threshold goes straight through, so the review effort lands only where the value justifies it.
What can trigger an approval request
|
Trigger |
Actions it covers |
|---|---|
|
Create |
Create paid subscriptions, create trial subscriptions. |
|
Changes |
Subscription quantity changes, enabling and disabling add-ons, add-on quantity changes. |
|
Upgrades |
Subscription full upgrades, subscription partial upgrades. |
|
Renewals |
Subscription renewal settings changes. |
|
Cancels |
Cancelling subscriptions. |
In 5.0 the price threshold is no longer one of the triggers. It is a separate Trigger threshold field that applies to all of them: requests at or above that amount require approval. Set it in the organization's own currency, per subscription.
Two levels, configured separately
A broker runs an approval process over its customers. An organization can run its own process over its own users. The two are independent, so the same action can raise a request at one level, at both, or at neither.
Where to go next
Manage Approval Requests
Finding a request, reading what it contains, and approving or rejecting it with a comment back to the requester.
Read more about managing approval requests
Set Approval Triggers
Choosing which actions require approval, setting the threshold, naming the triggering and approving roles, and applying all of it per customer or as a default.
Read more about setting approval triggers
Organization Internal Approval Process
The process an organization runs over its own users, and how it sits alongside the broker's.