Configuration Settings play a key role in shaping how Altus operates across your organisation.

While many settings are preconfigured, it is important to review key areas post-implementation to ensure alignment with your organisation’s governance model, delivery approach, and reporting needs.

For full, step-by-step guidance on individual settings, refer to:
https://docs.altus.pro/products/AltusPPM/Configuration/Settings/ConfigurationSettings.html

Important: Permissions Required

This task is available to users with administrative access to Settings in Altus.

• Changes in this area apply system-wide
• It is recommended to review settings in line with governance and change control processes

Top 10 Configuration Areas to Review

1. Altus Home Configuration (General)

Controls which homepage experience is available to users.

• Determines whether users see My Work, the legacy landing page, or both
• Impacts how users navigate and engage with the platform

✅ Review to ensure alignment with your adoption strategy and user experience

2. Global Configuration (General)

Controls global UI behaviour and system-wide controls.

• Influences visibility of interface elements such as quick actions
• Helps reduce user confusion by standardising interactions

✅ Review to ensure a consistent and simplified user experience

3. Notification Configuration (General)

Controls system-generated notifications.

• Enables or disables notification events across the platform
• Impacts user awareness of actions such as approvals and updates

✅ Review to align notifications with communication expectations and avoid noise

4. Project KPI and Summary Configuration (Projects)

Controls how project data is summarised and reported.

• Affects Issues, Risks, Deliverables, and Decisions summaries
• Influences KPI visibility and reporting consistency

✅ Review to ensure stakeholders receive the right level of insight

5. Project Type Form Tabs (Projects)

Controls which tabs are visible for different project types.

• Aligns user interface with governance requirements
• Ensures users only see relevant information

✅ Review alongside Project Types to maintain a streamlined experience

6. Fiscal Year Start Month (Finance)

Defines the start of the financial year.

• Impacts all financial reporting and aggregation
• Must align with organisational finance structures

✅ Critical to get right early — changes later can impact reporting consistency

7. Resource Horizon (Resourcing)

Defines the planning horizon for resource management.

• Controls how far ahead resource capacity and allocation can be viewed
• Impacts planning and forecasting

✅ Review to align with your planning cycles (e.g. quarterly, yearly)

8. Security Restrictions (Security)

Controls restrictions on key system actions.

Examples include:

• Prevent Project / Program / Portfolio deletion by non-admin users
• Control access to system-level features

✅ Review to enforce governance and protect critical data

9. Status Update Behaviour (Status Updates)

Controls how status reporting behaves.

• Includes duplication behaviour
• Controls locking of status update panels

✅ Review to ensure alignment with reporting governance and audit requirements

10. Timesheet Configuration (Timesheets)

Controls how time is captured and reported.

Key options include:

• Time entry mode (Project vs Task-based)
• Decimal precision
• Auto-population behaviour
• Override permissions

✅ Review to ensure alignment with your organisation’s time tracking model

Additional Tip: Review Inactive Configuration Settings

Some configuration settings are shipped but disabled by default.

• Switch to the Inactive Altus Config Settings view
• Review additional options available for advanced scenarios
• Enable settings where required based on organisational needs

These settings may support extended functionality and should be reviewed carefully before activation

How to Use This Guide

Use this checklist to:

• Validate your configuration after implementation
• Align system behaviour with governance and delivery models
• Identify gaps or misalignment early
• Support continuous improvement of your Altus environment

Tips

• Review these settings as part of project go-live or system health checks
• Involve stakeholders (PMO, Finance, Resource Managers) in decisions
• Document any changes for audit and support purposes
• Test changes in a controlled environment where possible