Approval route

A React component in Beamline's Data & tables category.

A policy you can read by trying it: an amount on a log scale with the thresholds as marks (the arrows stop just under, at and just over each), the request's choices and facts, and the route the host's policy gives it: stages of approvers in order, each with the rule that put them there, what they decide and how long they usually take, an away approver's stand-in, a missing approver that blocks the route; the policy's numbered sentences light as they apply.

Use it for

  • Spend, purchasing, payroll or time-off apps: on the policy settings page (what does this policy do?) or on a request form (who will approve this?).
  • The host's policy engine resolves the route; the part draws it, the thresholds and the rules that apply, and never decides who approves.

Not for

  • Building the policy itself (conditions, branches) → flowchart or a rule editor.
  • One approval decision on a request → approval-card.

Anatomy

  • header: the label
  • request: the amount scale (log, thresholds as marks, readout), the choices (segmented) and facts (switches)
  • summary: N approvers · usually about T, No approval: it goes through on submit, or Can't be approved as the policy stands
  • route: stages in order with arrows; a stage of several says Any one approves or All must approve; a step: avatar, name (or the stand-in), role, Must approve / Gets a copy · usually T · Rule N, the away note or the missing note
  • policy: numbered sentences, the applying ones in full ink with Applies

States

  • no approval
  • one stage
  • several stages
  • a stage of several (any one / all)
  • a copy
  • away (stand-in)
  • missing (blocked)
  • exactly at a threshold

Keyboard

  • The amount is the Scrubber's slider: ←/→ stop just under, at and just over each threshold, Page Up/Down jump between thresholds, Home/End the ends
  • Tab reaches the choices and facts; each change that settles says the route and the summary once (a polite status)

Motion

A stage that joins grows in at its place and the route slides (the shared FLIP); the summary changes in place. Nothing runs at rest; reduced motion places everything.

Props

PropTypeDefaultDescription
label (required)string—What is being approved: "Purchase requests", "Payroll runs".
amount (required){ min: number; max: number; thresholds: { value: number; label?: string | undefined; }[…—The amount scale: drawn logarithmically from `min` (above 0) to `max`, with each threshold as a mark; the arrows stop just under, at and just over every threshold (a step of `unit`, default 1), Page Up/Down jump between them.
choicesApprovalChoice[]—
flags{ id: string; label: string; }[]—
valueApprovalRequest—Controlled request; omit to use defaultValue.
defaultValueApprovalRequest—Initial selection when uncontrolled; omitted by default.
onValueChange((request: ApprovalRequest) => void)—Reports the selected value after a change; no callback by default.
rules (required){ id: string; text: ReactNode; }[]—The policy as numbered sentences, in order; the ones the current route uses light.
resolve (required)(request: ApprovalRequest) => ApprovalStage[]—The host's policy engine: the stages a request goes through, in order. The part never decides who approves.
format((amount: number) => string)—Money in the host's own format.
classNamestring—Classes on the documented visual root; no override by default.
classNamesPartial<Record<"root" | "step" | "request" | "route" | "policy", string>>—Classes for the named visual parts; no overrides by default.
styleCSSProperties—Inline styles on the documented visual root; no overrides by default.
refRef<HTMLDivElement>—Receives the documented native target or imperative handle; omitted by default.

Built from

Used in

Dependencies

lucide-react

Import

import { ApprovalRoute } from "@beamline/approval-route";

Get it

Approval route is part of Beamline UI. Install the parts you need in your React app as compiled packages or editable source. Get Beamline · Connect your agent

More in Data & tables

  • Living table: A table that shows as much as fits on both axes: width decides which columns show (the rest ride in the name line, moving there rather than vanishing)…
  • Availability layers: A week of bookable start times whose closed times explain themselves: every availability rule (hours, time off, bookings, buffers, rooms, lead time…
  • Capacity terrain: A schedule that stands on a terrain of capacity: under each station's lane of jobs, every day's load rises to its capacity line and an overload is a…
  • Domino move: A room board where one move shows its chain: drag a booking (or pick it and aim it with the keys) onto a taken room and the bookings it would push appear…
  • Match board: Month-end matching as one picture: bank lines and books entries side by side with threads between them — solid for matched, dashed with the host's reason…
  • Split anything: One splitter for money, quantities and time: a bar of the whole shows every target's part and what is not split yet; items are dragged onto targets…
  • Proposal twin: A proposal edited beside the client's exact page, the two linked both ways: a field in focus lights its twin on the page, scrolls it into view and joins…
  • Quantity river: The life of one order line's quantity: at rest a bar of its real split ("5 delivered · 1 back in stock · 1 damaged · 5 cancelled"), unfolding into a…
  • Stock horizon: Projected stock per item over the coming weeks: a strip of weeks with the safety line, weeks under safety in warn and short in danger, every dip said in…
  • Ageing queue: Tickets that visibly age: each ticket's ring fills toward its own service target and steps from on time to late to very late, the words say when it is…
  • Import lens: A messy import made fixable by kind: rows stream through the checks once with live counts; problems gather into groups that say what is wrong in words…
  • Duplicate guard: A new record that watches for the one that already exists: as you type, the likely duplicates slide in beside the form with the fields that match lit and…
  • Scan flow: A pick list that takes scans: each scan flies from the scan field into its row and fills that row's quantity ring, and the prompt moves to the next bin…
  • Pack planner: The packing bench: the order's items sit in box outlines drawn to scale, each box filling to its padding line, weighing against its limit and naming the…
  • Provenance lens: Hold Alt (or press Lens) over any number on the page and see what makes it: hairline threads draw from the number to the rows, cards and documents on…
  • Record time machine: The record itself, rewound in place: a slim track of every change (a tick per change in its person's colour, hollow for automation, named moments as…
  • Tension timeline: A plan where slack is something you see: every dependency is a string from one task's end to the next one's start, sagging with the days it has to spare…
  • Replay bar: Rewind for anything live: pause a stream, scrub back to the moment you missed (markers for the ones that matter), step one update at a time, replay at a…
  • Event calendar: A schedule of events by day, week or month: events that overlap sit side by side, drag one to another time or day or pull its bottom edge to change its…
  • Kanban board: Work as cards in columns by stage: drag a card (or lift it with Space and walk it with the arrows) to another column or place, the cards around it make…
  • Data grid: Virtualised local or server-driven grid: stable row IDs, manual sort and filters, pages or infinite loading, retry without losing rows, inline editing…
  • Pivot table: Records summed up by the fields people choose: rows grouped by one or more fields that fold open level by level, columns split by another, one or more…
  • Query builder: Conditions people build by hand to pick out records: each rule is a field, an operator that fits the field (contains, between, in the last N days, is any…
  • Sort order: Several sort keys in order. Each key says its rank in words ("Sort by Plan, A to Z", "then by Size, largest first") with its order named for the field's…
  • Metric rules: Ordered rules that colour a dashboard number. Each rule has a name for what its colour means ("At risk", not just red) and a tone (good, watch, act…
  • Log viewer: Log lines as they stream: it follows the newest line until you scroll up, then counts what arrived and brings you back in one click; filter by level with…
  • JSON viewer: A JSON value as a tree you can read and walk: branches open and close (one level, or all at once), closed ones preview what they hold, every value reads…
  • JSON diff viewer: Two versions of a JSON value compared as one tree: added keys marked +, removed ones struck through with −, changed values read old → new, unchanged keys…
  • Import mapping: Map the columns of a file to the fields of one record type, see what every value becomes, then run the import and get an outcome for each row…
  • Diff table: Proposed edits to a table before they happen: new rows green, removals struck through, changed cells old → new; each change can be left out and Apply…
  • Filter toolbar: The filters on a list kept in view: chips that remove themselves, Add filter with fields and their values, Clear all, and room for search or view controls.
  • Table: A native HTML table for small datasets, composed with children or driven by records; shared server paging, sorting, filters, search, stable-ID selection…

Part of Beamline UI: polished, editable React components and complete screens for custom applications. Build your own style from any look; tokens, fonts, radii, motion; not only colours.