Skip to main content
Use Sanka to centralize approvals instead of scattered chats or email threads. Define who approves, when, and under what thresholds, then let workflows route, notify, and track decisions.

​
What you can do

  • Build approval flows for purchase orders, bills, expenses, contracts, inventory moves, and custom objects
  • Route by amount, category, cost center, or requester role
  • Collect comments, files, and decision history for audits
  • Notify via in-app and email; remind or escalate when pending
  • Log final decisions and update the underlying records automatically

​
Typical flow

  1. Define policy: set thresholds (e.g., over $5k needs director), approver roles, and SLA targets.
  2. Create workflow: add Approval Actions, set parallel/sequential steps, and map outcomes to status updates.
  3. Trigger approvals: start from object events (creation/update), forms, or imports; capture request data in the record.
  4. Review & decide: approvers see context, attachments, and diffs; approve/reject/return with comments.
  5. Post-decision actions: on approval, update status or create follow-up records (PO, receipt, payment, journal); on reject, notify requestor and keep the trail.

​
Setup tips

  • Keep approval chains short; use amount bands to avoid over-approval.
  • Standardize required fields (vendor, amount, tax, account/department) to reduce back-and-forth.
  • Enable reminders for pending items over your SLA; escalate after a set number of hours/days.
  • Use forms for ad-hoc requests; map fields to object properties so data stays structured.
  • Dashboards: track cycle time, approval rate, and backlog by approver or department.