Skip to main content
This guide takes you from no approvals to a working setup that enforces your discount, product, and legal-terms policy on every quote and subscription. By the end you will have one enabled ruleset with ordered rules, approver groups that will not stall, and notifications reaching the right people. It assumes you have read the overview. Approvals are configured in the dashboard under Settings → Approvals. There is no public API for rulesets, rules, or approver groups in the 2026-04-01 API; approval events are available as webhooks.

​
Prerequisites

  • Admin access to your Alguna organization, with permission to manage approval rulesets.
  • At least one product configured.
  • Team members with user accounts who can act as approvers.

​
Step 1: Plan the policy

Decide what needs sign-off and who gives it. Sketch the approver hierarchy before building it — for example Sales Managers up to 20%, VP of Sales up to 35%, CFO above that. Each level becomes an approver group on a rule.

​
Step 2: Create a ruleset

1

Open Settings → Approvals

Click New ruleset and give it a name and description.
2

Decide on justification

Turn on Require justification if the requester must explain why the deal needs approval. A rule that matches unconditionally never asks for one.
3

Choose what happens after approval

Pick the post-approval action — activate the subscription, send for signature, or manual (the rep progresses it) — and whether progression is automatic, manual, or the requester’s choice.
4

Leave it disabled for now

A disabled ruleset is skipped during evaluation. Enable it after the rules are in.
Every enabled ruleset is evaluated. Within a ruleset only the first matching rule by priority applies, so a deal picks up at most one rule per ruleset — but one from each ruleset. Put each concern (discounts, legal, product) in its own ruleset.

​
Step 3: Add rules

1

Click New rule in the ruleset

Give it a name and description.
2

Set the condition

One or more condition types, combined with ALL or ANY. See Step 4.
3

Add approver groups

At least one. See Step 5.
4

Set the priority

Lower numbers run first. See Step 6.
5

Enable the rule

Disabled rules are skipped.

​
Step 4: Conditions

Operators: greater than, greater than or equal, less than, less than or equal, equal, not equal. Discount type: percentage or fixed amount. A percentage threshold and a fixed-amount threshold are different tests; pick the one that matches how your reps discount. Combining: ALL means every condition must hold; ANY means one is enough. The “always” condition cannot be combined or negated.
Because only the first matching rule in a ruleset applies, an “always” rule makes every lower-priority rule in that ruleset unreachable. Give it the highest priority number unless you intend it as an override.
Details and examples on Approval Rules.

​
Step 5: Approver groups

Each rule carries one or more groups. A group defines who approves and how many are needed. The rule also has a groups strategy — whether all of its groups, any one group, or a minimum number of groups must be satisfied.
A group with one named approver stalls when that person is away. Prefer the approver role, or name several people with an any strategy.

​
Step 6: Priority

Within a ruleset, rules run lowest number first and the first match wins, so ordering decides who is asked. A 40% discount matches the CFO rule and stops. Reversed, the manager rule would match first and the CFO would never be asked. Reorder by dragging rules in the ruleset.

​
Step 7: Configure notifications

Approvers are emailed when a request needs them. To add Slack:
1

Connect Slack

Under Settings → Approvals, open the Slack settings panel.
2

Choose the workspace and channel

Requests are posted there and approvers can act on them from the channel.
3

Check the connection status

The panel shows whether the connection is enabled, disconnected, or needs reconnecting.
To drive your own notifications, subscribe to the approval webhooks: approval_request.created, approval_request.approved, approval_request.rejected, and approval_flow.completed.

​
Step 8: Test

1

Build a deal that should trip a rule

Create a draft subscription with, say, a 25% discount on a covered product.
2

Check the approval summary

Before publishing, the subscription shows which rules matched and which groups must approve. If nothing matched, revisit the condition and whether the ruleset and rule are enabled.
3

Walk it through

Have an approver approve or reject from the dashboard or Slack and confirm the flow ends where you expect, and that the post-approval action runs. See Approval Flows.
4

Test a deal that should pass

Confirm a standard deal goes through untouched.

​
Step 9: Roll out

  1. Enable one ruleset covering your highest-risk case, usually deep discounts.
  2. Watch a week of real deals and confirm the approvals that fire are the ones you expected.
  3. Add rules for terms and product governance once the first is settled.
  4. Add an “always” ruleset only for a defined period, such as a pricing migration, and disable it afterwards.

​
Troubleshooting

Check, in order: the ruleset is enabled; the rule is enabled; a lower-numbered rule in the same ruleset is matching first; the condition’s discount type matches how the discount was applied; the product on the condition is the product on the subscription.
Every enabled ruleset contributes one rule. Consolidate related rules into a single ruleset.
Open the flow and see which group is outstanding. An all group waits for every named approver; a group with no members waits for any user holding the approver role.
Confirm the approver has a user account and email address, and that the Slack connection shows as enabled.

​
Next steps

Approval Rules

Condition types and evaluation in detail.

Approval Flows

How requests progress to a decision.