Review, approve, or reject a requisition you've been assigned to sign off on — from Slack, email, or Kula directly.

Methods to get notified

• Slack — a message from Kula in Slack (if Slack notifications are set up for your account)

• Email — an approval notification email

• In-app — the notification panel inside Kula, plus the requisition's own record page under Requisitions

Approving a requisition

• Open the notification from Slack, email, or the in-app notification panel — or go directly to the requisition under Requisitions.

• Review the requisition details shown (department, office, work type, headcount, and other configured fields).

• Select Approve.

• If your approval is one of several steps in the flow, the requisition moves to the next step and the next approver is notified. If yours was the last step, the requisition moves to Approved (or Open, depending on configuration).

Rejecting a requisition

• Open the notification or go to the requisition directly.

• Select Reject.

• Enter a reason for the rejection. For non-bulk requisitions, this reason is captured and stored against the requisition.

• The requisition returns to the requester in an editable state so they can revise and resubmit it.

What happens after you act

• Approving or rejecting redirects you to the requisition's details page.

• The requisition's status updates immediately to reflect your decision.

• Changing an approval workflow's configuration only affects requisitions submitted after the change — it doesn't re-route requisitions already mid-approval. See "Requisition approval workflows" for how flows and approvers are configured.

Super Admin override

• Super Admins can approve or reject on behalf of another assigned approver — useful when an approver is out of office or otherwise unavailable.

• This also covers the sanctioned way to push through an approval when someone can't act themselves; Kula does not support impersonating another user's login to do this.

• When a Super Admin acts on behalf of someone else, the activity feed records that the action was taken on behalf of the original approver.

Good to know

• The Approve/Reject controls only appear if requisition approvals are turned on. If your account has requisition approvals disabled, you won't see an approval button at all — this is expected, not a bug.

• Rejection reason capture applies to non-bulk requisitions. If you're rejecting requisitions in bulk, check with your admin on whether a reason is captured the same way.

• Approval emails link out to the requisition rather than offering one-click Approve/Reject buttons inside the email itself. Kula deferred building inline email action buttons; instead, the email takes you to the requisition to act there. A related, currently open enhancement (in progress as of this writing) covers giving approvers a more direct path from the notification into the requisition — particularly useful if your requisition has custom fields you need to see before deciding, since today's approval notification only shows the default fields.

• Reminder notifications for pending requisition approvals are working as of mid-2026. A past bug where approvers weren't receiving reminder emails for un-actioned requisitions has been fixed.

• A known, currently open bug affects the reject flow initiated from email in some cases: the rejection modal can fail to close/cancel properly, and occasionally the requisition's status doesn't update even though the rejection went through. If this happens, refresh and check the requisition's actual status directly on its record page rather than relying on the modal state.

• If the sole approver on an active step has been deactivated, the requisition can get stuck with only a Reject option showing and no way to Approve. This is a configuration/workflow-level scenario — see "Requisition approval workflows" for the two ways to resolve it.

• Two recent display-only bugs affecting requisition approval notifications have been fixed: notifications no longer show raw HTML instead of formatted text in the description field, and Slack/notification messages for group-based requisitions now show the correct newly-added headcount rather than the group's total headcount when heads are increased on an already-approved group.

FAQ

• Why can't I find the Approve button on a requisition? Requisition approvals may be turned off for your account, in which case no approval button is shown by design. Check with your admin, or see "Requisition approval workflows" for how approvals are configured.

• Can I approve a requisition on behalf of someone who's out? If you're a Super Admin, yes — you can act on behalf of any assigned approver. This is the supported way to handle an unavailable approver; Kula doesn't support logging in as another user to do this.

• Why don't I see all the requisition's fields before I'm asked to approve? Today, approval notifications show the requisition's default fields. If your requisition uses custom fields you need visibility into before deciding, go to the requisition record directly rather than relying on the notification content — this is a known gap that's actively being worked on.

• I rejected a requisition but it still shows as pending — what's going on? This can happen due to a known issue with the rejection flow when actioned via email, where the requisition's status doesn't always update immediately. Check the requisition's record page directly; if it's still showing the wrong status, contact support.

• Can I add a reason when I reject a requisition? Yes, for individual (non-bulk) requisitions — you'll be prompted to enter a rejection reason, which is stored against the requisition.

• Does changing the approval workflow affect requisitions that are already pending approval? No — workflow changes only apply to requisitions created or submitted after the change. See "Requisition approval workflows" for details.

Need help?

Contact Kula support if an approval or rejection isn't going through as expected, or if a requisition seems stuck.