Governance · Approvals & Workflow

One queue, every kind of decision.

Invoice requests, leave, timesheets, milestones — in one place, not four.

Invoice requestMilestone 2 — Inception reportRaised by finance · invoice.request
LeaveAnnual leave, 12–16 AugYour direct report · leave.approve
TimesheetWeek of 10 Aug — 40.50h6 entries awaiting review · timesheet.approve
MilestoneInception, discovery and planningMarked complete · milestone.approve

One surface, not one authority — each row has its own permission.

Current capabilities

What you can do in Approvals & Workflow

Milestone sign-off, invoice requests, leave, and other workflow approvals surface in a single inbox, so nothing sits waiting because it was buried in a module someone doesn't open daily.

  • A unified approval inbox across modules
  • Override capability for the roles that need it, logged either way
  • Directly linked back to the record under review — no re-searching
Read the workflow guide →

Why one inbox matters.

The cost of scattered approvals isn't the clicking. It's the waiting.

Where do you check?

Four toolsEmail, plus three apps you might not open today

KoraOne queue, and it's empty or it isn't

What's actually blocked?

Four toolsYou find out when someone chases

KoraThe thing waiting on you says what it's holding up

Who approved it?

Four toolsSomewhere in a thread

KoraOn the record, with the decision and the time

Override, but visibly

approval.override exists because organizations have genuine emergencies. It's a distinct permission and an audited act — not an admin quietly doing it a different way.

Next

Where this connects.

See Approvals & Workflow on your own work.

We'll run a live project of yours through it rather than showing a demo tenant.

Request a demo