Timesheet Approval Options in SuiteProjects Pro
Is your timesheet approval process causing more headaches than it should?
Register for this Power-Up Series video, where Ronn Breaux, CEO of Top Step, breaks down the approval options available in SuiteProjects Pro and shares practical tips for setting them up correctly. Misconfigured approvals can mean spammed end users or approvers who never get notified, so getting this right matters.
Key Takeaways:
- Understand the difference between project-level and user-level approval settings, and when you need one, the other, or both
- Learn why designating role-based approvers like "Project Owner" is a better practice than hard-coding named approvers
- Explore options for applying sequencing in multiple approver scenarios to allow for simultaneous approvals, and set auto-approval thresholds
- Discover how proxy approvals keep timesheets moving when an approver is out of the office
- Get tips on avoiding common pitfalls that lead to approval bottlenecks and confused end users
Approval processes don't have to be a source of frustration. Whether you're managing simple project-level approvals or a more complex, multi-step process, this Power-Up Series video will give you the tools to configure timesheet approvals that actually work for your team. Register now to streamline your approval workflow and keep timesheets moving smoothly.
Have not had a chance to watch the video yet? You can watch it here.
Frequently Asked Questions
When a timesheet is submitted, how does SuiteProjects Pro determine the approval process (user/project level) to execute first?
SuiteProjects Pro looks first at the project level approval setting(s) and proceeds to satisfy all project level approval requirements. Once project level approval requirements are met, the system proceeds to review user level approval setting requirements.
If all approvals are designated at the project level, what should the User level approver be set to?
Self-approver
What's the best practice for designating named user(s) as part of the approval process?
The best practice for designating named user(s) in an approval workflow, is to set named users within an approval process and apply the approval process to the applicable project vs setting a named user as an approver directly on the project. This prevents the need to update each individual project directly when the named user changes, as the change will only need to be updated once within the approval process itself vs on each individual project.
How can you set up an approval process/sequence where only one approval is required but more than one designated approver(s) can provide the approval?
Within an approval process, start by designating your approvers and assigning the same sequence number for each designated approver line. Once you have that set, check the 'A sequence number requires only one approval' setting, towards the bottom of the form, to allow for only needing one of the designated approvers to provide the approval for the same sequence number.
If a designated approver is on PTO, should we update the approval processes?
No, you can grant temporary proxy rights to a designated user who will be covering an absent employee's timesheet approvals.
