Why nobody approves their own request
Separation of duties across time off, timesheets, bills, pay runs and offers, and how Logpagia enforces it in every app.
Logpagia team · 12 Nov 2026 · 5 min read
Approvals protect an organization only when the person who asks and the person who decides are different people. Logpagia applies that rule everywhere an approval exists, so a manager cannot approve their own timesheet and a finance lead cannot approve a bill they entered.
Where the rule applies
The same check runs in every app that has an approval step:
- Timesheets, work records, time off and time adjustments
- Task reviews and document approvals
- Contract triage and contract approvals
- ID cards and visitor invitations
- Bills, pay runs, offers and requisitions
- Knowledge articles, service requests and volunteer hours
How it looks in practice
Your own requests appear in Waiting on you so you can follow them, but the approve and reject actions belong to someone else. When a request reaches its approver, it arrives with everything they need to decide in the list itself.
Pay runs and money
Payroll goes further. Whoever prepares a pay run hands it to someone else to approve, and nobody approves a run that pays them. In Payables, the person who records a payment hands its release to someone else.
Reasons on the record
Status changes and payroll edits need a written reason. Every payroll change keeps the old value, the new value, who made it and when, so an auditor can follow each decision.
Where Pagia AI fits
Pagia can prepare a time-off request, draft a reply or summarize what is waiting on you. It never approves anything. Approvals stay with people.
- Approvals
- Time and attendance
- Payroll
- Pagia Finance