Overview
By default, a user's authorization limit also applies when they approve their own documents. This setting lets admins define a separate, lower threshold for self-approval without affecting the user's authority to approve others' requests in workflows.
Prerequisites
Admin mode access required
Setting is configured per user individually
Steps
1. Go to Manage User → Users and click Edit on the user.
2. Under the Details tab, open the Profile sub-tab.
3. Scroll to the bottom right and uncheck "Use authorization limit for self-approval".
4. Enter the dollar amount in the Self approval limit field that appears. Changes save automatically.
FAQ
Q: Why is my request going for approval when I normally approve at this value?
If your admin has set a separate self-approval limit on your profile, requests you create yourself will go for approval if they exceed that limit — even if your standard authorization limit is higher. Contact your admin to check whether a self-approval limit has been set on your account.
Q: Where is the "Use authorization limit for self-approval" setting in ProcureDesk?
It is in the user's profile under Manage User → Users → Edit User → Details tab → Profile sub-tab. Scroll to the bottom right — it appears as a checkbox next to the PD Admin checkbox.
Q: What is the difference between the authorization limit and the self-approval limit?
The authorization limit controls how much spend a user can approve on other people's documents within an approval workflow. The self-approval limit is a separate, lower threshold that only applies when the user is creating and approving their own documents. The two limits work independently of each other.
Q: Can a user set or change their own self-approval limit?
No. This setting is only accessible in Admin mode. Individual users cannot view or modify their own self-approval limit.
Q: Will setting a self-approval limit affect how the user appears in other people's approval workflows?
No. The self-approval limit only affects documents the user creates themselves. Their authorization limit and their role in other users' approval workflows remain completely unchanged.