-
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Timesheet Approval - RM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Timesheet Approval - RM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in.

