Deciding who approves what
MekongHRM works out who should approve a request at the moment the request reaches them, from the org chart as it stands. Nothing is written onto the request in advance, so reorganising on Tuesday changes what happens to requests already in flight.
For most companies the setup is one question per kind of request: Their manager, and nothing else.
Before you start
- The
approval.configurepermission. The Owner and HR roles hold it. - Departments with managers. See Branches and departments.
Steps
Say who approves
- Open Approvals.
- Against each kind of request, choose where the approver comes from:
- Their manager — their own manager if they have one, otherwise their department's, plus anybody added as an extra approver.
- The level above — the level above.
- Whoever holds a role — whoever holds a role that covers them.
- Particular people — a list you pick.
Add somebody beside the manager
This is the answer to "a secretary should approve the team's leave". An extra approver on a unit stands equal to its manager: either can decide, and the first to do so passes the step. They can be set to cover the units beneath it as well as the unit itself.
Under Extra approvers on a unit, choose the unit and the person, and press Add.
It is not a role and not a permission, because it is neither — it is a fact about one unit, and the approval card arrives in their Telegram whether or not they ever open the web admin.
Seeing those requests is a separate question. If they should also be able to browse the team's requests in the admin, give them a role holding request.view_all and set its scope to the same unit — see Roles and who can do what. The two are deliberately not the same switch: approving from Telegram without a login is an ordinary arrangement, and most secretaries only need that.
Choose the company approver
Under Fallback approver, choose the person who decides a request when the flow finds nobody else, and press Save. Left empty, it is the Owner — as long as the Owner has a staff record; without one, such a request has nobody, and the screen says so. Saving sends the requests already waiting on nobody to the person you chose, with their cards in Telegram. The change is written to the activity log.
Check it before anybody relies on it
- Under Check a request would reach somebody, choose If this person filed and a request of this kind.
- Press Check.
What you should see
The checker shows each step, who is in it, and which of four ways they were arrived at — their own step, the level above, the company approver, or nobody.
It is worth running for a few different people, because the three problems it catches all look like success until a request depends on them:
- A unit in the chain has no manager.
- Requests fall through to the company approver.
- An approver has not linked Telegram. They can still decide on this site.
If something goes wrong
Nobody can approve this. Requests would be stuck. — nothing in the chain produced a person and there is no company approver set. Requests would be filed and then sit. Set a company approver, or give the department a manager.
The Owner's own requests, or somebody else's, have nobody. Nobody approves their own request, so when the company approver is the Owner, the Owner's requests run out of people. You do not have to wait for one to sit: the form says so before Send — in the Mini App and when you file for somebody here — and Overview warns you with the number of people affected, linking here. Choose someone else as the company approver, or give that person a direct manager who is not them.
Everything is going to the Owner. That is the company approver doing its job, and it means nothing above it answered. The checker says which step ran out.
An approver never sees the card. They have not linked Telegram. They can still decide from Requests on this site, and the checker marks them so you know.
A manager cannot approve their own team member's request. They can. What they cannot do is approve their own, which goes to the level above instead.
Last checked 19/09/2026