This article covers:
- Client / contact information;
- Planning settings;
- Time entry settings;
- Other settings;
- Home page settings;
- Security settings;
- Technical settings.
The System Configuration settings provides control over some core functions of PPO. This is typically set up and configured during implementation and should be stable post implementation.
System Configuration can be accessed from the Administration Menu.
The client / contact information section contains three pieces of information: Client name, Project office e-mail address and Billing e-mail address.
Client Name: This is displayed in the browser tab and can be changed by the PPO Administrator as required.
Project office e-mail address: This is used in PPO's e-mail events module. For more information on e-mail events, please see the following knowledge base article.
Billing e-mail address: This is the e-mail address that all monthly subscription invoices will be sent to.
PPO uses the standard hours specified in resource planning calculations. For more information on the planning functionality, see the following knowledge base article.
This is where you configure the various defaults and settings relating to time entries as shown below. For more information on the effect of these settings, refer to the Time Entries knowledge base article.
Other settings include: Default priority for "Admin" projects; Document check in / out; Task import fields; and Currency Symbol.
Default priority for "Admin" projects: PPO allows clients to set a default priority value for admin projects which allows users to easily filter administrative projects out of their reports and dashboards. The admin priority is set to 999 by default. When a project is selected as an admin project (Admin field on the project entity is TRUE) the Priority field on the Projects entity will automatically update with the default priority, as set up in this section of the System Configuration.
Document check in / out: This setting enables the document check in / out functionality in PPO. This functionality is described in more detail in the Documents knowledge base article.
Task Import fields: This setting is used to map custom fields between MSP and PPO when using the Import Tasks Wizard (to import task information from MSP into PPO). More information on this functionality is available in the Tasks knowledge base article.
Currency Symbol: The default currency symbol setting can be changed by specifying a new currency symbol in this setting. Refer to the Costs knowledge base article for more information.
Default skin: You can either select the Default skin, one of the other standard skins listed or define a custom skin. For more information on how to create your own custom skin, refer to this knowledge base article. Note that the skin that is selected will be the default skin for all users. Users that have selected a different skin can revert to the instance default by selecting the "…Global Default…"
The purpose of the Home Page is to show each user a summary of their current and relevant items. PPO shows the Tasks, Issues and Risks entities on the Home Page by default, but often it will be required to bring another entity, such as Projects, Benefits, Decisions, Leads or Health Indicators to the user's attention when they log in.
This will create greater visibility as well as provide the users with easy access to the items that need their attention most. Entities that appear on the PPO Home Page can be defined by the System Administrator.
To change the entities that appear on the PPO home page, select the entities from the Home Page Settings section.
Note: the entities will appear on the Home Page in alphabetical order.
Also note that when additional entities are added to the Home Page it's recommended that the administrator creates a shared filter to ensure that users only see items that are applicable to them. For more information on setting up filters, see the following knowledge base article.
Security settings relate mainly to passwords and log in settings.
Minimum password length: This is the minimum required length allowed for a user's password. If the user selects a password shorter than the length specified here, they will be asked to submit a new password. If this field is set to zero, the password can be any length.
Must include numeric characters: This field indicates whether the users' passwords must contain numbers.
Must include alphabet characters: This field indicates whether the users' passwords must contain alphabet characters.
Must include special characters: This field indicates whether the users' passwords must contain special characters.
Maximum number of logon attempts: PPO can lock a user's account if they have tried to log on unsuccessfully for a specified number of times. If this field is set to zero, the user can try to log on for an infinite number of tries and never be locked down.
Password expiry days: This field indicates the number of days after which the users' passwords will expire. When a password has expired, the user will be asked to reset their password when they log in. If this field is set to 0, the users' passwords will never expire.
Minimum number of days between password changes: This field indicates the minimum number of days between password changes. If this field is set to three, it means the user will have to wait three days after resetting their password before they will be allowed to reset it again. If this field is set to zero, the users can change their passwords as often as they prefer.
Password history: This field indicates whether the user may use the same password more than once. If the password history is set to three, the user's password must be unique for three password changes before the user can use a previous password again. If this field is set to zero, the user can use the same password continuously.
Technical settings include: Life Cycle start up SVG file; and Disable email events.
Life Cycle start up SVG file: This is the landing page for the life cycle component of PPO. For more information on the Life Cycle, see the following knowledge base article.
Disable e-mail events: PPO sends out e-mail notifications to keep users up to date with changes made to PPO. The e-mail events for an instance can be disabled (when this setting is set to ON) which will result in no e-mail notifications being sent out. For more information on e-mail events, see the following knowledge base article.
Send e-mails to non-users: This setting will only be seen by the key client contact and will allow for e-mail notifications to be sent to persons who are not users on PPO (i.e. persons who are only loaded as employees). For details on this setting, its implications and consequences, as well as the process to activate this functionality, see the following FAQ.