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.

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 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 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 shows each person’s effective approval authority, including when someone relies on this organization default because they don’t have their own limit set.


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 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 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 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.

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 (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, individual approval limit, and who they report to.
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 name when the limit comes from a level, and including the 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.

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 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, 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.
Below your policies, the Organization default row is the routing that runs when no policy matches: the required approver, budget owners, pedigree approvers, and then the threshold chain. It is assembled from your organization settings rather than stored as a policy, so it has no priority and cannot be reordered or archived. Open it to see each part it adds, in order, and to jump to the setting that controls that part.
Each policy has three parts, evaluated in this order:
When—which orders the policy applies to (policy matching)
Conditional approvers—who gets added, and under what circumstances (policy steps)
Approval authority—what those people may sign off on while this policy applies (policy overrides)
How policy matching works
Every policy has a name, a priority, and a When 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 When 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 When 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:
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:
Amounts in conditions are in your organization's base currency, the same as approval limits.
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 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.
Policy steps (conditional approvers)
A policy holds an ordered list of approver rules. Each rule has two halves:
When (gate)—an order condition, built the same way as the policy's own When condition. An empty condition always applies.
Then (candidate approvers)—a condition selecting the people to add.
Rules run top to bottom. For each rule whose gate matches the order, everyone the Then query selects is added to the chain, in rule order. Rules whose gate 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 own When condition—the gate over orders, the Then over people.
To refer to the order being approved, a Then condition uses the placeholder "$orderId". On the JSON tab that gives these shapes:
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 sets it. The policy editor shows it as a locked step at the end of the conditional 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.
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. 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:
That person's individual override on the matched policy
The policy's default for everyone
Their own approval limit, or your 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, 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.
How policies work with your approval settings
Policies sit on top of the approval settings above. What changes when one matches:
Organization chart and reporting structure
Always used. The threshold chain is appended after the policy's approvers on every matched order.
Default approval threshold and per-user limits
Used unless the policy overrides authority for that person.
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.
Still enforced. It decides whether the threshold chain starts at the requester or at their manager, the same as on any other order.
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 Then examples above) so you control where they land in the chain.
Reapproval thresholds, stale steps, signatures, 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
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 for more detail on how signatures work.

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.


The order is immediately approved and the current user is recorded as the only approver. This option is available when the current user's approval limit is above the order amount.

The order is immediately approved and the current user is documented as having used this expedited approval option. This option is only available to users with sufficient privileges when they ordinarily would not have the authority to self-approve a purchase.
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:
Click the Approve button in the email (requires being logged in)
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.

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 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
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:

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
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 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
Exporting approvals

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: statusin 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
Last updated
Was this helpful?


