--- title: "Set up and maintain default configuration settings" url: "https://help.altus.pro/fr/article/set-up-and-maintain-default-configuration-settings" language: "fr" last_updated: "2026-05-28T06:38:43.329Z" --- # Set up and maintain default configuration settings The **Configuration Settings** area allows administrators to control how Altus behaves across the system. For step-by-step guidance and detailed explanations of each configuration setting, refer to the official documentation: [https://docs.altus.pro/products/AltusPPM/Configuration/Settings/ConfigurationSettings.html](https://docs.altus.pro/products/AltusPPM/Configuration/Settings/ConfigurationSettings.html)  These settings provide **platform-level controls** that influence functionality, user experience, governance, automation, and integration behaviour across projects, resources, and reporting. Changes made here apply at an **organisation-wide level** and typically take effect immediately. > Configuration Settings are designed to allow administrators to **adjust system behaviour without requiring code changes**. > > Your organisation’s implementation partner may have configured additional custom settings (often under **Data Management**) to support self-service updates, lookup tables, or tailored configuration options—refer to their documentation for details. * * * > Important: Permissions Required This task is available to users with **administrative access to Settings in Altus**. - If you do not see the required options, you may not have sufficient permissions - Changes in this area can impact multiple modules and users - It is recommended to follow governance and testing practices before making updates * * * ## Accessing Configuration Settings 1. Navigate to **Settings** 2. Locate the **System Configuration** section 3. Select **Configuration Settings** This page displays a structured list of configurable system areas. * * * ## How Configuration Settings Are Structured Configuration Settings are grouped into functional sections. Each section contains specific controls that influence behaviour within that area of Altus. * * * ## Important: Viewing Additional Configuration Settings By default, the view displays **active configuration settings** only. To access additional settings: - Switch the view from **Configuration Settings** to **Inactive Altus Config Settings** This allows you to: - Discover additional settings that are **shipped with the solution but disabled by default** - Review optional or advanced configuration options - Enable settings where required based on organisational needs > These inactive settings are typically used for **extended functionality or advanced scenarios** and should be reviewed carefully before enabling. * * * ## Understanding Key Configuration Sections ### General Controls core system experience and global behaviours. Typical capabilities include: - Configuring the **Altus homepage experience** - Managing global UI behaviour and controls - Defining notification and reporting configurations These settings apply across the entire application and influence how users interact with Altus. * * * ### Projects Controls how project-related features behave. Typical capabilities include: - Configuring summaries (e.g. Issues, Risks, Deliverables, Decisions) - Managing ownership and reassignment behaviour - Defining form structure and visibility (e.g. tabs, KPIs) These settings influence how project data is **captured, displayed, and summarised**. * * * ### Programs and Portfolios Controls aggregation and governance of higher-level entities. Typical capabilities include: - Summary controls for Issues, Decisions, and Change Requests - Group ownership and visibility settings - Tab visibility and reporting alignment These settings ensure consistency in **roll-up reporting and governance across programs and portfolios**. * * * ### Finance Controls financial behaviour within the system. Typical capabilities include: - Managing finance-related configuration - Defining the **fiscal year start month** This ensures financial reporting aligns with organisational accounting structures. * * * ### Dependencies Controls how dependencies are managed across projects. Typical capabilities include: - Defining rules and behaviour for dependency tracking These settings support **cross-project coordination and scheduling logic**. * * * ### Artificial Intelligence Controls AI-related features within Altus. Typical capabilities include: - Managing Copilot or AI-assisted functionality These settings determine how AI capabilities are enabled and used within the system. * * * ### Power BI Insights Controls integration with Power BI reporting. Typical capabilities include: - Configuring portfolio-level insights - Defining value formatting for reports Supports **advanced reporting and analytics integration**. * * * ### Resourcing Controls resource management and planning behaviour. Typical capabilities include: - General resource configuration - Resource finance integration - Resource planning horizon These settings influence **resource capacity, allocation, and financial alignment**. * * * ### Risks Controls behaviour of risk-related features. Typical capabilities include: - Mapping between risks and issues Supports governance and alignment between **risk management and issue tracking**. * * * ### Security Controls system-level protections and restrictions. Typical capabilities include: - Restricting deletion of key records (e.g. Projects, Portfolios, Programs) - Managing access to specific services or features - Controlling form visibility through exclusions These settings help enforce **data protection, access control, and governance rules**. **Important:** By default, only users with administtator privilege can delete parent records namely projects, programs, portfolios and bookable resources. These protection settings does **not** extend to the child records associated to the parent records when collaboration is enabled e.g. read-write access to the group members of a project record. * * * ### Status Updates Controls behaviour of project status reporting. Typical capabilities include: - Managing duplication behaviour - Controlling locking of information panels These settings influence how **status reporting is captured, maintained, and governed over time**. * * * ### Strategy Controls strategic planning and prioritisation. Typical capabilities include: - Managing evaluation criteria and categories - Defining prioritisation models Supports structured **decision-making and portfolio planning**. * * * ### Tasks Controls behaviour of task management features. Typical capabilities include: - Configuring task tracking and execution behaviour These settings impact how **work is structured and managed within projects**. * * * ### Teams Controls integration with Microsoft Teams. Typical capabilities include: - Managing app tabs - Managing channel tabs Supports collaboration and integration with Teams environments. * * * ### Timesheets Controls time tracking configuration. Typical capabilities include: - Defining how time is entered (e.g. project vs task-based) - Managing time entry rules and behaviour - Supporting finance integration for timesheets These settings determine how users **enter, submit, and report time**. * * * ## How to Use Configuration Settings Use Configuration Settings to: - Tailor the system to your organisation’s **governance model** - Align functionality with **delivery, financial, and reporting processes** - Enable or restrict features based on **user needs and roles** - Maintain consistency across projects, programs, portfolios, and resources * * * ## Key Considerations - Changes apply **system-wide and immediately** - Some settings impact **multiple modules simultaneously** - Always validate changes in a **controlled or test environment** where possible - Align updates with **organisational governance policies** * * * ## Tips - Review settings periodically to ensure alignment with evolving business needs - Document key configuration decisions for audit and support purposes - Use consistent approaches across modules - Avoid unnecessary changes to default settings unless required