Approvals matter, but they're easy to bottleneck. A cashier might need a permission override right now, with a customer waiting on counter, but the manager who can approve it isn't always available.
On the back office side, a Purchase Order sent for approval can just sit there forgotten, since there's nothing pulling anyone's attention to it.
Xilnex for Lark Approvals solves both of these by sending the request straight to Lark, wherever the approver already is, instead of relying on someone physically walking over or remembering to check.
Xilnex for Lark supports two kinds of approval. Make sure you know which one you need before diving into setup:
| Permission Approval | Document Approval |
Triggered by | Cashier attempting a blocked action at POS | Submitting a back-office document |
Set up under | Approvals → Permission Approvals tab | Approvals → Document Approvals tab |
Approvers configured in | Lark Approvers card, same tab | System Configuration → Approval Setting |
Covers | Sales, Item, Receive, Listing | Purchase Order, Stock Request, Stock Adjustment |
Who's involved | Cashier + assigned approver | Requester + approver group |
Lark component | Lark Approval Form | Lark Card |
For Permission Approval setup and the POS experience, see Permission Approvals in Xilnex for Lark.
For Document Approval setup and the requester/approver experience, see Document Approvals in Xilnex for Lark.