Skip to main content

 

Planview Customer Success Center

Designing the Project Settings page

Note: Only the project entity has a Settings page.

PPM Pro initially populates the Settings page with fields that are typically set by the project manager at the beginning of a project and not of interest to general project team members. The Available Fields panel displays all fields that can be placed on the Settings page. Mandatory fields must remain on the page. You can also configure restrictions on the Settings page, as well as create field-level PMO Lock restrictions.

You configure this page much the same way as you configure the Details page. See Designing the Details Page for more information.

For example, there will be a set of default group headers and fields that will automatically appear within the Details field list. Fields indicated as "(mandatory)" must remain, but you can remove and rearrange all other fields and group headers as appropriate. The following are fields of particular interest that you may consider keeping or removing depending upon your design:

  • Confidential Project - keep if you are going to allow permitted users the ability to indicate when category's project is confidential. 
  • Health Profile - keep if you are going to use explicit and automatically calculated indicators of project health and if you are going to allow permitted users to view or update the category's projects Health Profile.
  • Allocation Units, Resource Planning Mode - adjust based on your staffing design decision and if you are going to allow permitted users to change these for the category's projects.
  • Can Be Template - keep and adjust if you want to allow permitted users to indicate if the category's projects can be used as template projects.
  • Default Project Log Category - keep and adjust if you are going to use project logs or issues/risks, if you have included Project Logs or Issues/Risks in the category Sections to include, and if you are going to allow permitted users to change the default project log category.
  • Scoring Profile, Scoring Is Locked - keep if you are going to use a project scoring model, if you have included Scoring in the category Sections to include, and if you are going to allow permitted users to change these for the category's projects.
  • Default Task Category - keep and adjust if you are going to use tasks, if you have included Tasks in the category Sections to include, and if you are going to allow permitted users to change the default task category.
  • New Tasks, Requires Rescheduling, Conversion for Tasks-Hours per day, Conversion for Tasks-Hours per week - keep and adjust if you are going to use tasks (Step 1 question 4), if you have included Tasks in the category Sections to include, and if you are going to allow permitted users to change these values (see default fields for more information on the purpose of each of these).
  • Tasks Critical If Slack Days Less Than Or Equal To - keep and adjust if you are going to use tasks and particularly task dependencies, if you have included Tasks in the category Sections to include, and if you are going to allow permitted users to change this value (see default fields for more information on the purpose of each of this field).
  • % Complete Method - keep and adjust as appropriate if you are going to track project % complete and if you are going to allow permitted users to change the method.