Governance

Approvals

When an action needs sign-off, BOS automatically creates an approval request and routes it to the right person — so nothing important slips through unchecked.

When approvals happen

An approval is triggered automatically whenever an action meets a rule you've set — usually based on roles and attributes. Common triggers include:

A value crosses a threshold (e.g. an expense over ₹50,000).
A sensitive record is changed or deleted.
A separation-of-duties rule requires a second person.

How an approval flows

1
A request is created
Someone (or Orin) starts an action that needs sign-off. BOS pauses it and creates an approval request.
2
It routes to an approver
The request goes to the right person based on your rules — a manager, a finance lead, or a specific role.
3
The approver decides
They review the details and approve or reject, optionally adding a comment.
4
The action completes
If approved, the original action executes. If rejected, it stops. Either way, the outcome is recorded.

Single vs. dual approval

Some actions need just one approver; higher-risk actions can require two. Dual approval pairs naturally with separation of duties to protect against fraud and error.

Escalation

If an approval sits too long, BOS can escalate it to another approver so work doesn't stall. Escalation rules are configured in Settings.

Approve from anywhere

Approvals appear in the app and can also be sent to Gmail, so you can approve or reject on the go. Every decision — wherever it's made — is logged.

Full traceability

Every approval decision is written to the audit trail with who decided, when, and any comment — giving you a complete record for compliance and reviews.