> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/approvals.md).

# Approvals

Route purchase approvals using your org chart and per-user limits, with flexible step editing and a break-the-glass override for out-of-band approvals

Approvals in Silkline provide a fast and flexible way to request purchase approvals. This workflow is meant to serve as a speed limit sign—guiding behavior and flagging issues—rather than a spike strip that brings everything to a halt.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-e7f95ca0c6ddec14471681bfa2706fe950ff34d1%2Fsilkline_mascot_referee%402x.png?alt=media" alt="" width="188"><figcaption></figcaption></figure></div>

## The Basics

Here are the need-to-know basics for how Approvals in Silkline work:

* Purchase approvals in Silkline are based on the **organization structure** and **approval limits** per user
* The default routing for a purchase approval **begins with the requester (or optionally their manager) and then progresses up the organizational chart until the approver's limit exceeds the order amount.**
* The buyer can **flexibly modify the approval routing** by adding, removing, and reordering approval steps.
* The only enforced requirement is that **at least one approver must have the authority to approve the order.**
* **Even that requirement has a "break-the-glass" option** for when approvals happen outside Silklin.e
* Organizations with more involved routing can layer [**custom approval policies**](#custom-approval-policies) on top, adding approvers and adjusting authority for specific kinds of orders.

## Setting your Approval Rules

Users with sufficient privileges can [set the organization chart and approval limits](https://app.silkline.ai/dashboard/organization/settings/approvals) that define your organization's approval rules.

#### Default Approval Threshold

Set the approval limit that's used when a user doesn't have a limit specified. If a user has a limit set that's less than the default approval threshold, the user's lower limit will be used. For example, if the default limit is $500, but Joan has a limit of $250, she can only approve orders up to $250.

The [organization chart](#organization-chart) shows each person’s **effective** approval authority, including when someone relies on this organization default because they don’t have their own limit set.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-5fc895b9263b677453d4397ad40a7d0e4ec41440%2FScreenshot%202025-07-20%20at%2010.46.01%E2%80%AFAM.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-fc96316396c1e250e0334354cdfbf66eae3bc6b6%2Fapproval-limits.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Approval Levels

Approval levels are named approval limits, such as **Manager** or **Director**, that you assign to team members instead of setting a limit on each person individually. Create levels on the **Approval levels** tab of the Approvals settings page, giving each a name and an approval threshold (or **Unlimited**).

Assign a member to a level from the [organization chart](#organization-chart) edit panel, or set the **Approval Level** column to the level's name when bulk importing users (a blank value clears the level). While a member is on a level:

* The level's threshold is their approval limit. Their **individual approval threshold** is grayed out and does not apply.
* Changing the level's threshold applies to every member on that level immediately.
* Moving the member to a different level gives them that level's threshold.

Clear the level to return the member to their individual threshold, or to the [default approval threshold](#default-approval-threshold) when they have none. Deleting a level does the same for everyone who was on it.

For deciding whether an approval is sufficient, Silkline uses the member's level threshold when they have one, otherwise their individual threshold, otherwise the organization default. An authority set by a matching [custom approval policy](#custom-approval-policies) takes precedence over all three.

#### Reapproval Threshold

Specify a dollar and percent increase threshold. Reapproval is required only when the order total **increases** and **exceeds** the configured thresholds. You can configure whether reapproval requires exceeding **either** threshold (OR logic, default) or **both** thresholds (AND logic). Orders at or below the thresholds do not require reapproval. **Important:** Reapproval is never required when an order total decreases.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-c4657fe875e406c024cc7568ef1e4053ea256209%2FScreenshot%202025-07-20%20at%2010.46.06%E2%80%AFAM.png?alt=media" alt=""><figcaption></figcaption></figure>

**OR Logic (Either Threshold - Default):** Let's say an organization sets reapproval thresholds of 10% or $10,000 with OR logic. The Organization's default approval threshold is $1,000.

**Example 1:** A $500,000 purchase increases to $520,000. The $20,000 increase is only 4%, but reapproval is required because the increase exceeds $10,000.

**Example 2:** A $5,000 purchase increases to $6,000. The $1,000 increase is less than $10,000, but reapproval is required because the order increased by 20%.

**Example 3:** A $250 purchase increases to $750. The $500 increase (200%) exceeds the 10% rule, so re-approval is required. However, at $750, the purchase falls under the organization's $1,000 default approval threshold, allowing the user to self-approve the purchase.

**Example 4:** A $500,000 purchase decreases to $480,000. No reapproval is required because the order total decreased, even though the change is $20,000 (which would exceed the $10,000 threshold if it were an increase).

**AND Logic (Both Thresholds):** With the same thresholds (10% and $10,000) but AND logic, reapproval is required only when both thresholds are exceeded:

**Example 5:** A $500,000 purchase increases to $520,000. The $20,000 increase exceeds the dollar threshold but is only 4% (below 10%), so **no reapproval is required**.

**Example 6:** A $5,000 purchase increases to $6,000. The 20% increase exceeds the percent threshold but is only $1,000 (below $10,000), so **no reapproval is required**.

**Example 7:** A $100,000 purchase increases to $125,000. The $25,000 increase (25%) exceeds **both** thresholds, so **reapproval is required**.

#### Stale approval steps

When the order total **increases** after one or more approvers have already approved, some of those approvals can become **stale**. A step is stale when the approver approved at a lower amount and the order total has since increased beyond your [reapproval thresholds](#reapproval-threshold) (dollar and/or percent).

**Example:** The order is $100,000. Bob ($80,000 limit) approves first. The order is then edited and the total increases to $120,000 (the increase exceeds your reapproval thresholds), so Bob’s step is now **stale**—he approved at $100,000 but the order is now $120,000. Alice ($150,000 limit) then approves at the new $120,000 total. Alice has sufficient authority and a non-stale approval, so Bob’s approval is not needed for release. You can remove Bob’s step and release the order. Alternatively, if you want Bob to approve as well, re-request his step so he approves at the new total.

**When some steps are stale and others are not:**

* The approval widget will show **Reapproval Required** when any step is stale.
* Before the order can be released (moved to Approved), **stale steps must be removed or re-requested**. Edit the approval workflow (pencil icon), and remove or re-request the stale approval steps.
* You are **blocked** until all stale steps are removed or reset.

#### Organization Chart

Specify a reporting structure and dollar value limits for each user. Click the pencil icon next to a user to define their job title, [approval level](#approval-levels), individual approval limit, and who they report to.

{% hint style="info" %}
Enable **Lock "Reports To"** in the edit panel to manage a user's manager manually. While locked, their **Reports To** won't be changed by integration syncs (such as an HRIS connection). Turn off the lock to change it.
{% endhint %}

Each row shows **name**, **email**, and **job title** (when set); search matches any of those. Active users see **effective** limits (**Unlimited** or a dollar amount), prefixed with the [**approval level**](#approval-levels) name when the limit comes from a level, and including the [**default approval threshold**](#default-approval-threshold) when no personal limit applies. Inactive users omit the limit badge. **Inactive** and **delegate** labels appear when relevant. A **lock** indicator appears next to a user's integration labels when their **Reports To** is locked.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-feb9b33c9490d9566dbf9c8e629a9f8337158bc2%2FScreenshot%202025-04-19%20at%202.30.12%E2%80%AFPM.png?alt=media" alt=""><figcaption><p>Approval Settings</p></figcaption></figure>

#### Required Approver

Optionally designate a specific user who must approve all orders in your organization, regardless of other approval settings. When a required approver is set:

* This user's approval is **required** for every order approval workflow to be considered sufficient
* The approval threshold rules still apply - there must still be at least one approver with sufficient authority for the order amount
* Both conditions must be met: the required approver must approve **AND** someone with sufficient threshold must approve
* Force approvals bypass this requirement (as they bypass all other approval requirements)

This feature is useful for organizations that want to ensure a specific person (such as a CFO or procurement lead) reviews all purchases, while still maintaining approval threshold requirements.

#### Always Include Requesters in Approval Chain

Control whether requesters with no budget authority are included in the default approval chain. By default, all requesters are included as the first approver. When this setting is disabled:

* Requesters with **$0 or no approval authority** are excluded from the default approval chain
* The approval chain **starts at the requester's manager** instead of the requester
* Requesters who were granted **their own positive approval authority** (greater than $0) are still included in the approval chain
* Only authority granted to the requester individually counts here: their personal approval limit, or a [policy override](#policy-overrides-approval-authority) naming them. Blanket grants—the organization's default approval threshold or a policy's default approval authority—do not put an excluded requester back on the chain
* Requesters may still appear in the approval workflow if triggered by other rules (e.g., they're a budget owner)

This setting is useful for organizations where requesters without budget authority should not need to "approve" their own purchase requests, and approvals should go directly to management.

#### Prevent Requester Solo Approval

Control whether requesters can approve their own orders based on their normal approval limit. When this setting is enabled:

* Requesters are treated as having a **$0 limit on their own orders**
* This rule applies to routing, sufficiency checks, and threshold badges
* On orders above $0, the requester cannot be the only sufficient approver
* If no other approver has enough authority, add a qualified approver

#### Require Signature by Default

Control whether new approvers added to approval workflows automatically have signature capture enabled. When this setting is enabled:

* New approvers added to an approval workflow will have the **signature requirement turned on by default**
* Existing approval steps are not affected—this only applies to newly added approvers
* Users can still manually toggle the signature setting off for individual approvers if needed

This setting is useful for organizations where most or all approvals should appear as signatures on the finalized purchase order, saving time when setting up approval workflows.

#### Admin-only Expedited Approvals

Control who can use expedited approval to bypass normal approval requirements. By default, users with the Buyer or Admin role can use expedited approval. When this setting is enabled:

* Only users with **admin privileges** can use expedited approval
* Non-admin users will be prevented from using the expedited approval option, even if they normally have the permission
* This setting applies only to **expedited approval** and does **not** block standard self-approval when a user has sufficient approval authority

This setting is useful for organizations that want to ensure only the most trusted users can use the "break-the-glass" expedited approval option.

## Custom Approval Policies

Some organizations need approvals to depend on more than the order total—for example, budgeted spend routes to budget owners and finance, while unbudgeted spend climbs the org chart first. **Custom approval policies** let you describe those cases as named rules that Silkline applies automatically when an order is sent for approval.

Policies live in [Organization Settings → Approvals](https://app.silkline.ai/dashboard/organization/settings/approvals), in the **Custom approval policies** section. Use the **Enabled** switch to turn the feature on for your organization, then **Create policy** to add one. Editing policies requires the *edit approval policies* permission.

{% hint style="info" %}
Policies **add** to your approval settings; they don't replace them. Every policy-matched order still enforces your spend authority rules: when nobody the policy selects can cover the order total, the threshold chain built from your [organization chart](#organization-chart) and approval limits fills the gap.
{% endhint %}

Above your policies, the **Organization default** section shows the routing an order gets when no policy matches, as steps in order: the requester (when [Always Include Requesters in Approval Chain](#always-include-requesters-in-approval-chain) is on), the [required approver](#required-approver) (when one is set), budget owners (when budgets are on), pedigree approvers (when your organization has active pedigrees), and then the reporting line up to someone whose authority covers the order total. Steps marked **Every order** also run after a matched policy's own approvers. The section is built from your organization settings, so change those settings to change it.

Each policy has three parts, evaluated in this order:

1. **Which orders**—the orders the policy applies to ([policy matching](#how-policy-matching-works))
2. **Approvers**—who gets added, and under what circumstances ([policy steps](#policy-steps-conditional-approvers))
3. **Approval authority**—what those people may sign off on while this policy applies ([policy overrides](#policy-overrides-approval-authority))

### How policy matching works

Every policy has a **name**, a **priority**, and a **Which orders** condition describing the orders it covers.

Matching happens when an order is sent for approval (and again whenever the approval workflow is re-sent). Silkline walks your active policies in priority order—**lowest number first**—and evaluates each policy's Which orders condition against the order:

* The **first policy that matches wins**. Lower-priority policies are not evaluated, and **at most one policy applies to an order**.
* If **no policy matches**, the order uses your standard threshold routing, exactly as it would with the feature turned off.
* An **empty Which orders condition** matches every order, which makes it a useful catch-all—give it the highest priority number so it's checked last.

Conditions are built with the **Builder**, which has two tabs:

* **Builder**—pick a field, an operator, and a value, and group clauses with AND/OR. A **plain-language preview** underneath restates the condition as a sentence, so you can check it says what you meant before saving.
* **GraphQL JSON**—the same condition as raw JSON, for conditions the builder doesn't cover and for reading exactly what's stored.

Both tabs edit one condition; switch freely between them. If a condition uses a clause the builder doesn't handle, it's preserved intact and shown as an *advanced GraphQL condition*—editable on the JSON tab, and the rest of the condition still editable in the builder.

Common shapes, as they appear on the JSON tab:

| Orders you want to cover                    | Which orders condition                                        |
| ------------------------------------------- | ------------------------------------------------------------- |
| Every order                                 | `{}`                                                          |
| Orders over $50,000                         | `{"totalInBaseCurrency": {"_gt": 50000}}`                     |
| Orders with at least one budgeted line item | `{"OrderItems": {"budgetId": {"_is_null": false}}}`           |
| Orders with no budgeted line items          | `{"_not": {"OrderItems": {"budgetId": {"_is_null": false}}}}` |

Combine conditions with AND/OR in the builder, which is `_and` and `_or` on the JSON tab:

```json
{
  "_and": [
    { "OrderItems": { "budgetId": { "_is_null": false } } },
    { "totalInBaseCurrency": { "_gt": 2500 } }
  ]
}
```

Amounts in conditions are in your organization's base currency, the same as approval limits.

{% hint style="success" %}
**Test before you rely on it.** Use **Test policies** in the Custom approval policies section to pick a real order and preview which policy matches it and the exact chain of approvers it would produce.
{% endhint %}

Once an order is sent, the matched policy's name is shown on the approval workflow and in the **Approval Policy** column on the [Approvals](https://app.silkline.ai/dashboard/approvals) page, where you can also filter by it. Orders that matched no policy show **Default approval policy**.

A workflow keeps the policy it was sent with. If the order is edited afterwards so that a different policy matches it—or none does—the approval workflow shows which policy applies now, under the policy name when you edit approvers. Sending the order for approval again attaches that policy.

{% hint style="warning" %}
If a policy's condition can't be evaluated—for example, it references a field that doesn't exist—sending for approval fails with an error instead of quietly skipping the policy. This is deliberate: a broken policy should never silently produce a weaker approval requirement.
{% endhint %}

### Policy steps (conditional approvers)

A policy holds an ordered list of **approver rules**, under **Approvers**. Add one with **Add approvers**. Each rule has two halves:

* **Only when the order matches**—an order condition, built the same way as the policy's Which orders condition. An empty condition always applies.
* **Add these people**—a condition selecting the people to add.

Rules run top to bottom. For each rule whose order condition matches, everyone the people condition selects is added to the chain, in rule order. Rules whose order condition doesn't match contribute nobody. Reorder rules with the drag handles; the order you set is the order approvers appear in.

Both halves use the same Builder/GraphQL JSON editor as the policy's Which orders condition—one over orders, the other over people.

To refer to the order being approved, an **Add these people** condition uses the placeholder `"$orderId"`. On the JSON tab that gives these shapes:

| Approvers you want                        | Add these people condition                                                              |
| ----------------------------------------- | --------------------------------------------------------------------------------------- |
| A specific person                         | `{"id": {"_eq": "<organization user id>"}}`                                             |
| The order requester                       | `{"OrdersAsAssignee": {"id": {"_eq": "$orderId"}}}`                                     |
| Budget owners for budgets on the order    | `{"BudgetOwnerships": {"Budget": {"OrderItems": {"orderId": {"_eq": "$orderId"}}}}}`    |
| Pedigree (quality) approvers on the order | `{"PedigreeApprovals": {"Pedigree": {"OrderItems": {"orderId": {"_eq": "$orderId"}}}}}` |

A single rule can select several people—each becomes their own approval step. Only active users are selected, and anyone already in the chain is not added twice.

After every matching rule has contributed, Silkline checks whether the selected approvers can cover the order: if none of them has approval authority for the full order total, it appends the **threshold chain**—the walk up your org chart, continuing until it reaches someone whose authority covers the order. It starts at the requester or their manager, exactly as [Always Include Requesters in Approval Chain](#always-include-requesters-in-approval-chain) sets it. The policy editor shows it as **Always added last: spend limit approvers**, a locked step at the end of the approver list.

* When an approver the policy selected already has enough authority for the order total, the threshold chain adds **nobody**—the spend is covered.
* When it doesn't, anyone on the walk whose approval authority is at or below the highest authority among the policy's approvers is **skipped**: a policy approver can already sign off at that level. The people who remain are those the policy's approvers cannot stand in for, ending with someone who covers the order total.
* The requester is never skipped by these authority comparisons—their presence is governed only by the requester-inclusion setting.

**Steps are a starting point, not a lock.** The person sending the order can still add, remove, and reorder approvers, mark steps as signatures, and edit the workflow later—the same as any other approval. Approvers a policy selected appear with the **Additional Approver** (plus) indicator.

{% hint style="info" %}
If a policy matches but none of its rules' order conditions apply—say every rule is gated above $2,500 and the order is $900—the policy adds no approvers of its own. The order still gets the threshold chain, so a requester with enough authority may be the only step.
{% endhint %}

### Policy overrides (approval authority)

A policy can also change **how much authority people have on the orders it covers**. This is set in the **Approval authority** part of the policy:

* **Default for everyone**—the authority applied to anyone without an individual override below. It **replaces** each person's normal limit rather than topping it up, so it can lower authority (even to $0) as well as raise it. Leave it blank to keep everyone's normal limits.
* **Individual overrides**—an explicit authority for a specific person, added with **Add person**. Each person can appear only once.

Both accept a dollar amount or the **Unlimited** toggle.

While a policy applies to an order, each approver's **effective authority** is resolved in this order:

1. That person's individual override on the matched policy
2. The policy's default for everyone
3. Their own approval limit, or your [default approval threshold](#default-approval-threshold) when they have none

Effective authority is used everywhere authority matters on that order: how far up the org chart the threshold chain climbs, whether the workflow is [sufficient](#completing-approvals), and the limit shown on each approval step. An amount a policy set is marked with an asterisk, and its tooltip names the policy and shows the person's normally configured authority.

Overrides apply **only to orders the policy matched**. The same person keeps their usual limit everywhere else, and their profile and org chart entries are unchanged.

{% hint style="warning" %}
[Prevent Requester Solo Approval](#prevent-requester-solo-approval) always wins. When it's enabled, a requester is treated as having $0 authority on their own order even if a policy grants them more.
{% endhint %}

### How policies work with your approval settings

Policies sit on top of the approval settings above. What changes when one matches:

| Setting                                                                                                                                                                                           | With a matched policy                                                                                                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Organization chart](#organization-chart) and reporting structure                                                                                                                                 | Always used. The threshold chain is appended after the policy's approvers on every matched order.                                                                                               |
| [Default approval threshold](#default-approval-threshold) and per-user limits                                                                                                                     | Used unless the policy overrides authority for that person.                                                                                                                                     |
| [Required Approver](#required-approver)                                                                                                                                                           | Not added automatically, and their sign-off is not required for sufficiency. The policy's own rules decide who reviews—add a rule selecting that person if you still want them on these orders. |
| [Always Include Requesters in Approval Chain](#always-include-requesters-in-approval-chain)                                                                                                       | Still enforced. It decides whether the threshold chain starts at the requester or at their manager, the same as on any other order.                                                             |
| [Prevent Requester Solo Approval](#prevent-requester-solo-approval)                                                                                                                               | Still enforced, and it overrides any authority the policy grants the requester.                                                                                                                 |
| Budget owners and pedigree approvers                                                                                                                                                              | Not added automatically. Select them with an approver rule (see the **Add these people** examples above) so you control where they land in the chain.                                           |
| [Reapproval thresholds](#reapproval-threshold), [stale steps](#stale-approval-steps), [signatures](#signatures), [delegation](#approval-delegation), self-approval, expedited approval, $0 orders | Unchanged.                                                                                                                                                                                      |

Sufficiency works the same way it always does: at least one approver whose effective authority covers the order total must approve, and expedited (force) approvals bypass the requirement entirely.

Turning the **Enabled** switch off returns every order to standard threshold routing. Your policies are kept, so you can turn it back on without rebuilding them. Individual policies can also be archived from the policies table.

## Sending for Approval

{% stepper %}
{% step %}

#### Start the approval

When viewing a draft order, click the **Send for Approval** on the top right of the page. Note: this button will only show if Approvals are activated for your organization.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-eb89e8cc3d9da4a2e89b3062c9732949d7efb8c3%2FScreenshot%202025-04-19%20at%202.50.49%E2%80%AFPM.png?alt=media" alt="" width="176"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select approval steps

The default approval steps are based on your organization's settings and ladder up your org chart until the approval threshold is met. You can flexibly modify the approval steps as needed.

**Approver Type Indicators:** Each approver displays visual indicators showing their role in the approval process:

* **Required Approver** (red asterisk icon): The organization's required approver who must approve all orders
* **Threshold Approver** (sitemap icon): Users included based on the organizational reporting structure and approval thresholds
* **Budget Approver** (dollar icon): Budget owners for items on the order, automatically included to review spending against their budgets
* **Quality Approver** (certificate icon): Pedigree approvers assigned to ensure quality standards for specific items
* **Additional Approver** (plus icon): Users manually added to the workflow who don't fall into the above categories (e.g., "cameo" approvers)

Users may have multiple indicators if they serve multiple roles on the order. For example, someone could be both a Budget Approver and an Threshold Approver.

**Budget Approvers:** If order items are assigned to budgets, the budget owners are automatically included in the default approval chain. Budget approvers appear early in the workflow (after required approvers, before threshold-based approvers) and are labeled as "Budget Approver" in the approval steps. When an order pulls in more than one budget owner, they are sequenced by approval limit from lowest to highest, so the person who can sign off on the least spend reviews first. Budget information, including utilization and spending, is displayed in the approval guide to help approvers make informed decisions. When budget owners are on the order, the default chain also **drops any threshold approvers whose approval limit is at or below the highest budget owner's limit**—since the budget owner can already approve at that level, those threshold approvers would be redundant. The requester is never dropped this way and always appears first in the default chain.

**Pedigree/Quality Approvers:** If order items have pedigrees (quality requirements) assigned, the designated pedigree approvers are automatically included in the default approval chain to ensure quality standards are met.

We'll warn you if you select an approval routing where none of the approvers have the authority to approve the order, but you can still start the approval process.

**Signature Steps:** You can mark specific approval steps as "signatures" that will appear on the finalized PO by clicking the signature icon next to an approver. See [below](#signatures) for more detail on how signatures work.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-d4cc73ffbe6c252146ac18b6f4f3ca7f053b2e83%2FScreenshot%202025-11-02%20at%208.49.11%E2%80%AFAM.png?alt=media" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Add notes

Add notes or instructions you'd like to share with the approval request. This will be included in the email to the approver.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-498d24996862e5db61291639a76b2e304f18c105%2FScreenshot%202025-04-19%20at%202.43.17%E2%80%AFPM.png?alt=media" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Send for approval

Send the request for approval by clicking the **Send for Approval** button. The first approver will be notified immediately. Subsequent approvers, if applicable, will be notified once the prior approval steps have been completed.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-5f1fd5af92f914ef03432dd937864f2a90258df1%2FScreenshot%202025-04-19%20at%202.47.31%E2%80%AFPM.png?alt=media" alt="" width="191"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Alternatively, users can **self-approve** or **expedite approval.**
{% endhint %}

<table data-header-hidden><thead><tr><th width="193.62109375">Option</th><th>What it does</th></tr></thead><tbody><tr><td><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-2b15d7d1002de1655a8928783bb6fcf844944c84%2FScreenshot%202025-04-19%20at%203.02.46%E2%80%AFPM.png?alt=media" alt="" data-size="original"></td><td><strong>The order is immediately approved and the current user is recorded as the only approver</strong>. This option is available when the current user's approval limit is above the order amount.</td></tr><tr><td><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-a36de159efbdd20d1275f3db2c16ae93b3665dd9%2FScreenshot%202025-04-19%20at%202.54.29%E2%80%AFPM.png?alt=media" alt="" data-size="original"></td><td><strong>The order is immediately approved and the current user is documented as having used this expedited approval option.</strong> This option is only available to users with sufficient privileges when they ordinarily would not have the authority to self-approve a purchase.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

## Approving an Order

When it's your turn for approval, you will receive an email with key details of the order, notes, an overview of the approval steps, and an option to approve directly from that email.

If you have all of the details you need, you can approve in two ways:

1. **Click the Approve button** in the email (requires being logged in)
2. **Reply to the email** with one of the following approval keywords:
   * `#approved`
   * `#approve`
   * `#yes`
   * `#ok`

If you'd like to review the order details or leave a comment in the order's activity feed, click the **Review** button to view the order.

Once you have approved, the next approver will be notified.

{% hint style="success" %}
**Tip:** When replying via email to approve, simply type one of the approval keywords (e.g., `#approved`) in your reply. The system will automatically extract your approval from the email thread, even if it contains quoted content from previous messages.
{% endhint %}

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-06e9f51dd6464417dcfb7e4d845172478814c31a%2FScreenshot%202025-04-19%20at%203.17.20%E2%80%AFPM.png?alt=media" alt="" width="563"><figcaption><p>Example Approval Request email</p></figcaption></figure>

### Approving early

Although users are only notified when it's their turn to approve, users can approve an order before it's their turn. To do this, navigate to the order in question and click **Approve** for your step. You can also go to the [Approvals](https://app.silkline.ai/dashboard/approvals) page to search and filter across all approvals.

## Rejecting an Order

Approvers can reject an order by clicking the "Reject" button on the approval step. This sets the order back to draft and cancels the approval chain. The user must provide a reason for rejection. The order's buyer and requester receive an email notification that the order was rejected.

To send a rejected order for approval again, click the pencil icon at the top right of the approval widget. The previous approvers are pre-filled; add, remove, or reorder them, then click **Send for Approval**. This starts a new approval workflow, so every approver in it must approve again. The rejected workflow stays in the order's history.

## Completing Approvals

{% hint style="success" %}
An approval is **complete** when all listed approval steps are complete.
{% endhint %}

{% hint style="info" %}
An approval is **sufficient** when any completed steps have an approval limit above the order amount. If your organization has configured a required approver, that person must also approve for the workflow to be considered sufficient.
{% endhint %}

{% hint style="info" %}
$0 orders are considered approval-exempt.
{% endhint %}

When all steps in an order's approval workflow are complete, the order will *automatically* be marked as **Approved**. The order's buyer and requester receive an email notification that the order was approved, unless they approved the final step themselves.

Once an order is approved by *any* approver whose approval limit is above the order amount (and by the required approver, if configured), the order can be *manually* moved to the **Approved** status by using the order state dropdown:

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-da5704acb21f455c1c2c7c7b610f520f29c83fd7%2FScreenshot%202025-04-19%20at%204.29.00%E2%80%AFPM.png?alt=media" alt="" width="158"><figcaption></figcaption></figure></div>

## Signatures

Silkline allows any approval step to be displayed as an electronic signature on the purchase order. This is useful when internal or vendor policies require signatures on certain POs. Here's how signatures work:

* When sending a PO for approval, click the signature icon<img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-399d75793faeda5dd03d0282d1ead04d16f3ca56%2FScreenshot%202025-11-02%20at%208.55.58%E2%80%AFAM.png?alt=media" alt="" data-size="line">on approval step to use that approval as a signature.
* Approval steps that are marked as signatures will display a signature badge in the approval workflow
* When a PO is released (moved to OPEN status), each signature approval will be written to the PO. The approver's electronic signature, name, and approval date will appear in the "Authorized by:" section on the order web view and PDF

**Keep in mind:**

* Future approval workflows on the same order will replace the existing signatures; these changes are tracked in the audit log
* If your organization's reapproval thresholds are such that reapproval is not required for a given PO, new signatures also will not be required
* When approving as a delegate on behalf of someone else, the *requested* approver's signature is displayed on the Purchase Order, not the delegate's

## Managing Approvals

A frequent complaint about approval workflows is that it can be hard to see all of the pending approvals requiring your attention or identify where an approval you've requested is blocked.

Silkline's [Approvals](https://app.silkline.ai/dashboard/approvals) page makes it easy to monitor approvals and keep them on track. Users can see three tabs:

* **Waiting on Me** – approval requests where you are the current reviewer
* **Coming Up –** approval requests where you are an upcoming reviewer
* **My Completed** – approvals you've already completed
* **All Approvals** – all approvals across all orders

{% hint style="info" %}
You can identify which approvals someone is blocking by navigating to the **All Approvals** tab and filtering on **Next Approver**.

Example: *I want to see all orders that are being held up by my Head of Finance*
{% endhint %}

## Exporting approvals

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-3f197599db2e2af3bd1714b4a06693fea31ad92a%2Fapprovals-table-export.png?alt=media" alt="Approvals table on the All Approvals tab with the Export button in the footer"><figcaption><p>Approvals table with the Export button in the footer</p></figcaption></figure>

Use the **Export** button below the approvals table to download a CSV of the current tab. The export reflects the table as configured on screen:

* Any active filters and search terms are applied, and every matching row is included — not just the rows on the current page.
* The CSV contains the columns currently visible in the table, with headers matching the column names shown on screen. Use the column picker to add columns to the export — for example, **Last Activity** and any order custom fields are available but not shown by default.
* **Approvers** lists each step as `approver: status` in step order, using the same status words the table shows (Approved, Expedited, Rejected, Skipped, In review, Waiting). **Next Approver** names the delegate when one is set.

Each tab exports its own scope, and the file name includes the tab and the date.

## Approval Delegation

Each user can indicate a delegate who may approve on their behalf. This can be particularly useful when an approver is out of the office or has an executive assistant who assists with approvals.

When using approval delegation, the designated individual is copied on approval requests and will see a "Approve as Delegate" button for orders where they are a delegated approver. When a delegate approves on behalf of an original approver, the user completing the approval is recorded.

The applicable approval threshold is based on the *original* approver's authority, not the delegate. For example, let's say that Connor has an approval limit of $5,000 and Stacey has an approval limit of $10,000. If Stacey designates Connor as her delegate, Connor can approve on behalf of Stacey for up to $10,000. If an approval is requested of Connor directly, his approval limit is $5,000.

## Frequently Asked Questions

<details>

<summary>Do all approval steps need to be complete for an order to be approved?</summary>

**Nope!** An order can be approved when *any* steps are complete where the approver has an approval limit above the order amount.

Keep in mind that an order won't *automatically* move to the **Approved** state until all approval steps are complete.

</details>

<details>

<summary>Can I change approval steps after I send?</summary>

**Yes!** To edit an active approval workflow, navigate to the order and click on the pencil icon at the top right of the approval widget.

If the current step changes as a result of your edits, the new current approver will be notified of the approval request.

</details>

<details>

<summary>Can I re-request approval once someone has already approved?</summary>

**Yes!** To re-request approval, edit the approval workflow and simply remove the approval tag from the corresponding approver(s) <img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-6dc72afdd11e1d48e37c08f277abd36a49b14e71%2FScreenshot%202025-04-19%20at%205.12.21%E2%80%AFPM.png?alt=media" alt="" data-size="line">

</details>

<details>

<summary>What is a self-approval, and when should I use this?</summary>

A **self-approval** allows a user to immediately approve the order without starting an approval workflow. This option is only available to users that have an approval limit above the order amount.

</details>

<details>

<summary>What is an expedited approval, and when should I use this?</summary>

An **expedited approval** is a "break-the-glass" option that allows select users to bypass the normal approval limits.

This is useful when:

* Relevant approvers have already agreed outside Silkline
* The approval is time-sensitive but required approvers are unavailable

When using an expedited approval, the order is immediately approved and the user exercising this option is recorded as having used this option. A reason for using expedited approval is required.

**Note:** Organizations can restrict expedited approvals to admin users only through the [Expedited Approvals setting](#expedited-approvals). When enabled, only users with admin privileges can use this feature, providing an additional safeguard against unauthorized use of this "break-the-glass" option. This setting affects expedited approval only and does not affect normal self-approval eligibility.

</details>

<details>

<summary>What are stale approval steps, and what if only some steps are stale?</summary>

A **stale** approval step is one where the approver approved when the order total was lower, and the order total has since **increased** beyond your organization’s [reapproval thresholds](#reapproval-threshold).

**Stale steps must be removed or re-requested before the order can be released.** Edit the approval workflow (pencil icon), then either remove the approval from the stale step(s) and re-request so they approve at the new total, or remove those steps. Once stale steps are cleared and you have at least one approver with sufficient authority who has a non-stale approval, the order can be moved to Approved. Expedited (force) approvals are never considered stale.

</details>

<details>

<summary>What happens if none of the approvers in an approval workflow has the authority to approve an order?</summary>

This can happen in several cases:

* The order amount changes after an approval workflow has started
* Approval limits change after an approval workflow has started
* The user starting the approval intentionally sends an incomplete approval workflow – this can be useful if they want to get approvals started

When this occurs, a message like this will be shown:

{% hint style="warning" %}
Order total of **$55,000** exceeds highest approval limit of **$50,000**
{% endhint %}

In these cases, the order cannot be approved until the workflow is edited to add a qualified approver.

</details>

<details>

<summary>How do approvals work with orders in different currencies?</summary>

Approval limits are set in your organization's base currency (configured in [Organization Settings](https://app.silkline.ai/dashboard/organization/settings/currency)). When an order is in a different currency, Silkline automatically converts the order total to your base currency for approval comparisons.

**Currency Conversion:**

* The exchange rate is pinned to the date the order was created
* All approval amounts display in your organization's base currency
* Approval limits and thresholds are always in your base currency

**Example:** If your base currency is USD and you have a $10,000 approval limit, you can approve a €9,000 order or a £8,500 order (assuming the exchange rates on the order creation date make them equivalent to less than $10,000 USD).

{% hint style="info" %}
**Important:** Changing your organization's base currency does **not** automatically adjust existing approval limits. You'll need to manually update user approval thresholds if you change your base currency.
{% endhint %}

</details>

<details>

<summary>What is a required approver?</summary>

A **required approver** is a designated user who must approve all orders in your organization, regardless of other approval settings. When set:

* This person's approval is required for every order, in addition to meeting the normal approval threshold requirements
* Both conditions must be satisfied: the required approver must approve AND someone with sufficient authority for the order amount must approve
* Force approvals bypass this requirement (as they bypass all approval requirements)

This is useful when organizations want a specific individual (like a CFO or procurement manager) to review all purchases for oversight purposes, while still maintaining approval authority thresholds.

</details>

<details>

<summary>Where can I see the approval history of an order?</summary>

You can view the approval history of an order by clicking on the approval event in the order's activity feed, or from the [Approvals](https://app.silkline.ai/dashboard/approvals?tab=3) page.

</details>

<details>

<summary>Do you support group approvals?</summary>

Currently, approvals can only be routed to one individual at a time. Approvers can approve early, but they won't be notified until it's their turn.

Our research shows that group approvals actually *slow down* approvals because when reviewers know that there are multiple available approvers, each individual approver is less likely to take action.

</details>

<details>

<summary>Can I add a "cameo" approver?</summary>

**Yes!** In some cases you may want to add additional approvers that wouldn't typically be necessary for an approval. In Silkline, you can easily add cameo approvers to document their review.

</details>

<details>

<summary>How do budgets affect approval routing?</summary>

When order items are assigned to budgets, the budget owners are automatically added to the approval workflow as "Budget Approvers." This ensures that budget owners can review and approve spending against their budgets.

**Key points:**

* Budget approvers are automatically included in the default approval chain
* They appear early in the workflow (after required approvers, before threshold-based approvers)
* Multiple budget owners are sequenced by approval limit, lowest first
* Budget information, including utilization and spending, is displayed in the approval guide widget
* If a budget owner already appears in the approval chain (e.g., as a required approver), they are not duplicated
* Threshold approvers whose approval limit is at or below the highest budget owner's limit are omitted from the default chain, since the budget owner can already approve at that level (the requester is always kept and listed first)
* Budget approvers can be removed or reordered like any other approval step

For more information about budgets, see [Budgets](https://github.com/Silkline/client-app/tree/development/docs/profile-and-settings/organization-settings/budgets.md).

</details>

<details>

<summary>What is a signature approval step?</summary>

A **signature approval step** is an approval that will be formally documented in the "Authorized by:" section on the order PDF. When setting up an approval workflow, you can mark specific approvers as signatures by clicking the signature icon next to their name.

**When to use signatures:**

* For formal purchase authorizations that need to be documented
* When creating records for audit purposes
* For approvals that should appear on printed or PDF versions of the order

**How it works:**

* Mark an approval step as a signature when setting up your workflow
* The step displays with a signature badge in the approval interface
* Once the approver completes their approval, their name and approval date appear in the "Authorized by:" section on the order PDF
* Multiple approvers can be marked as signatures if needed

</details>

<details>

<summary>What do the approver type indicators mean?</summary>

When selecting approval steps, you'll see visual indicators showing why each approver is included:

* **Required Approver** (red asterisk icon): Your organization's required approver who must approve all orders
* **Threshold Approver** (sitemap icon): Included based on your organization's reporting structure and approval thresholds
* **Budget Approver** (dollar icon): Budget owner for one or more items on the order
* **Quality Approver** (certificate icon): Pedigree approver ensuring quality standards for specific items
* **Additional Approver** (plus icon): Manually added approver who doesn't fall into the categories above

Some approvers may display multiple indicators if they serve multiple roles. For example, a manager who is also a budget owner would show both the Threshold and Budget indicators.

These indicators help you understand the composition of your approval workflow and ensure all necessary stakeholders are included.

</details>

<details>

<summary>Can more than one approval policy apply to an order?</summary>

**No.** Silkline evaluates your policies in priority order, lowest number first, and the first one whose **When** condition matches the order is the one that applies. Everything that order needs—conditional approvers and authority overrides—comes from that single policy, so build one policy per scenario rather than expecting several to combine.

If you want a rule to apply broadly, put it inside a policy as an approver rule with an empty gate instead of creating a separate catch-all policy.

</details>

<details>

<summary>Why did my approval policy add no approvers?</summary>

A policy can match an order and still contribute nobody, when none of its approver rules' **When (gate)** conditions apply to that order. For example, a policy whose rules all start above $2,500 adds no one to a $900 order.

The order isn't skipped—it still gets the threshold chain up the org chart. Use **Test policies** to preview the exact chain for a specific order.

</details>

<details>

<summary>Does a custom approval policy still require my Required Approver?</summary>

**No.** When a policy matches an order, that policy decides who reviews it: your organization's [Required Approver](#required-approver) isn't added automatically, and their sign-off isn't needed for the workflow to be sufficient.

To keep them on orders a policy covers, add an approver rule to the policy that selects them by name, with an empty gate so it applies to every order the policy matches.

</details>

<details>

<summary>What are pedigree approvers?</summary>

**Pedigree approvers** (also called Quality Approvers) are users designated to review and approve orders containing items with specific quality or compliance requirements. When order items have pedigrees assigned:

* The designated pedigree approvers are automatically included in the approval workflow
* They appear with a certificate icon to indicate their quality approval role
* They review to ensure items meet the required quality standards and specifications

This is useful for organizations that need specialized review for certain types of purchases (e.g., lab equipment, medical supplies, or products requiring specific certifications).

</details>
