Core architecture

Legacy Project Web App (SharePoint-based)

Power Platform (Dataverse)

Altus is built on Microsoft’s modern platform; Project Online is in sustain‑only mode ahead of retirement (watch the Altus app Overview).

Product lifecycle

Sept 2026 retirement

Actively developed

Altus aligns with Microsoft’s future investment direction (visit the Altus for Microsoft 365 page).

Release cadence

Sept 2026 retirement

Fortnightly

Altus evolves continuously rather than via large, infrequent upgrades (read the Release train checklist documentation and bookmark the Altus Release Notes documenation and Released - Altus Product Roadmap website to stay up to date.

Runs inside customer Microsoft 365 tenant

✅ Yes

✅ Yes

Altus operates entirely within the customer tenant, supporting data sovereignty and compliance Altus aligns with Microsoft’s future investment direction (visit the Altus for Microsoft 365 page).

Environment support (Dev/Test/Prod)

Sept 2026 retirement

Fully supported by client care teams and channel partners

Aligns with Power Platform governance and ALM practices (read the Solution Layers documentation for information on environments)

Settings and Administration

PWA Settings + Site Settings (self-service)

Altus Settings (self-service) + Power Platform Admin Centre (+ Dataverse) and Power App Maker (not self-service)

Read the Settings, System settings, and Configuration Settings for more technical information on Altus settings (self-service).

For more information on where these settings are now managed in Altus, refer to Section 10: General Settings and Administration of this article.

Microsoft Project Desktop integration

✅ Core

✅ Core (one‑way sync, read-only)

Richer scheduling remains anchored in Project Desktop by design but MPP files can now be be published in Altus (read the Altus for Project documentation and follow the Faster Project Scheduling - Altus Product Roadmap card for upgrade to this capability).

Important:

• There is no need to check-in, check out or force-check-in a project schedule in Altus once the mpp file is linked. Task updates from the mpp file must still be published regularly to update the schedule view in Altus (read the Integrate a Microsoft Project Plan (MPP) in the Altus app KB article for instructions).
• Nevertheless, there is currently no mechanism to open linked mpp files directly from Altus (follow the Open MS Project Files Directly from Altus - Altus Product Roadmap card for updates and Altus for Project | Supported Locations documentation)
• Linking and unlinking privileges can be restricted to specific Altus roles for governance.

Web‑based scheduling

Limited

✅ Native Altus schedule

Altus scheduling is designed for lighter planning and continues to mature (read the Altus Projects | Tasks documentation).

Important:

• Milestones are created by converting an existing task to a milestone rather than instantly (read the Identify work using the Timeline view KB article for instructions).
• New and existing custom columns can be added to schedules only when implemented by an Altus partner (watch Altus Schedule - Custom Columns | Feature Demo video), while self‑service creation is not currently available.
• Project managers can also lock tasks for timesheeting out of the box, with this control synchronised with Microsoft Project Desktop.
• Altus does not use an enterprise global template for standardising custom views, tables, columns, or filters across schedules. Instead, it provides a default Timeline (Gantt) view and a Board view for Kanban‑style scheduling, with the ability to save and share additional custom schedule views not yet supported (follow Saving and Sharing Views - Altus Product Roadmap card for updates on this feature).
• Schedule printing or exporting to formats other than Excel CSV is not currently available (follow the Exporting Altus Schedules - Altus Product Roadmap card for updates on this feature).
• Altus supports core schedule tracking through percent complete, completed effort, and importing timesheet actuals into a schedule (read the Track task progress and variance in the schedule KB article for instructions) whilst more detailed time‑phased task and resource usage views (similar to those available in Project Online) are not currently supported by default (follow the Altus Tasks - Time Phased Effort and Resourcing - Altus Product Roadmap card for updates on this enhancement rolling out this year)
• The Status Date in Altus is exclusively used for project reporting and status updates, rather than for retroactively marking incomplete work in the schedule (read the Drill-through Project insights and Set project KPIs and compose status narratives KB articles for instructions and follow the Customisable Project Status - Altus Product Roadmap for updates on this feature)

Planner / Planner Premium integration

❌ Not supported

✅ Supported

Altus intentionally supports both multiple Microsoft and non-Microsoft scheduling tools (read the External Execution Tools documentation).

Schedule tool flexibility by project type

❌ No

✅ Yes

Teams can choose the right scheduling tool based on complexity (read the External Execution Tools documentation).

Schedule template flexibility by project type

✅ Yes via MSP

⚠️ Partial

Altus uses project types to template workflows, registers, and settings for consistent project delivery, with pre‑defined content for RAID registers and baseline schedule templates currently under exploration (follow the Project Content Templating - Altus Product Roadmap card for updates).

Important: Unless a custom templating feature is developed for your organisation by an Altus partner, use a temporary workaround by linking and unlinking a schedule template .mpp file to enable management of a standard set of activities within the native Altus schedule (read the Disconnect a Microsoft Project Plan (MPP) from the Altus app KB article for instructions).

Schedule unification across tools

❌ Not supported

✅ Supported

Altus consolidates schedules from multiple tools into a single portfolio view (read the Navigate the All Active Projects - Timeline view KB article)

Enterprise calendars for project, resource, and task scheduling

✅ Supported

⚠️ Partial

While Altus supports core scheduling fundamentals such as task types, task locking for tracking, lead and lag times, dependencies, resource unit allocation, and notes, calendar management at the project, resource, or task level is not currently supported within the native Altus scheduling experience.

Important:

• Altus uses a standard project scheduling calendar of 8 hours per day, Monday to Friday, excluding weekends, with no support for public holidays or calendar exceptions (follow the Project Calendars - Altus Product Roadmap | Product Roadmap card for updates on this feature).
• As the calendar is currently centralised and not customisable for project scheduling (i.e. creation and maintenance of local project calendars are not yet supported), schedulers may need to account for holidays and non‑working days within task duration estimates to ensure realistic finish dates.
• While enterprise calendars can be maintained by administrators in Altus, they currently apply to resource capacity and demand planning only, not task‑level scheduling as customisable project calendars are not yet available.
• When an MPP file is linked, project calendars are not imported into Altus; however, task start and finish dates calculated in Microsoft Project are retained in Altus, along with task dependencies and related schedule attributes (follow the Altus for Project - Smarter Calendar Sync - Altus Product Roadmap card for updates on this feature).

Critical path analysis

✅ Full (via MSP)

⚠️ Partial

Advanced CPM remains within Project Desktop (follow the Altus Tasks - Show the Critical Path Product Roadmap card for updates)

Baselines (schedule)

✅ 11 Baselines (Baseline 0-10)

✅ Enhanced (20 Baselines)

Scheduling fundamentals such as baselines are retained (read the Set reportable project baselines for variance tracking KB article for instructions).

Important: Unless specifically configured for your organisation by an Altus partner,

• Baselines created in your .mpp files are not published into Altus by default.
• Once your project tasks have been published into Altus, the Altus Baseline feature can be used to set baselines on the tasks for variance tracking and reporting in Altus (follow the New Project Summary tab - Altus Product Roadmap card for updates on this relevant feature)
• While Altus supports multiple baselines to align with governance requirements, only one baseline can be set as the reportable baseline at any time, which is used to determine schedule health in status reporting (read Altus for Project - Training | FAQ documentation)
• Once created, baselines in Altus are not reset or updated (or overriden) and may only be hidden or deleted from the schedule.
• Baselining privileges can be restricted to specific Altus roles for governance.

Master / parent projects and inter-project dependencies

• ✅ Supported

• 🔄 Portfolio roll‑ups

• Altus replaces master projects with portfolio and program aggregation (read the Altus Portfolio documentation).
  
  Important:
• Unlike the Project Centre view in the PWA interface of Project Online, there is currently no mechanism to bulk open multiple linked mpp files directly from any Altus system view to create a temporary master schedule (follow the Open MS Project Files Directly from Altus - Altus Product Roadmap card for updates)
• While there is no direct equivalent of master schedules in Altus yet, a similar outcome can be achieved with roll-up of schedule data both at a program and portfolio level (read Altus Portfolio documentation and discover the Timelines view from the Drill-through Portfolio and Program insights KB article).
• While inter‑project dependencies are typically managed through a master project in Microsoft Project, Altus supports inter‑project dependencies at a project (and structural) level only (read the Creating dependencies between projects KB article for instructions), rather than as fully task or milestone‑level dependencies across projects (follow the Inter-Project Dependencies - Alerts & KPIs - Altus Product Roadmap and Dependencies Projects - Connect Milestones & More - Altus Product Roadmap cards for updates on these features).
• Nevertheless, mpp files that combine schedules from multiple projects (master schedule) can still be published to Altus (read the Integrate a Microsoft Project Plan (MPP) in the Altus app KB article).
• Only tasks contained directly within the master project will synchronise into Altus, while tasks embedded from linked child projects do not currently synchronise (follow the Portfolio & Program Management Enhancements - Altus Product Roadmap card for a relevant feature request).

Auto and manual scheduling depth

• ✅ Supported

• ✅ Supported

• Native Altus schedule provides both auto and manual scheduling mode albeit with no visual task indicator yet (read Identify work using the Timeline view KB article and follow the Visual Indicator for Task Schedule Type - Altus Product Roadmap card for updates)

Task management (boards and sprints)

• ❌ Not supported

• ✅ Supported

• Board‑ and sprint‑based task management is provided by Altus alongside traditional schedule‑driven planning (read Identify work using the Board view KB article and follow the Altus Tasks - Hybrid Project Management - Altus Product Roadmap card for updates on blending waterfall and agile projects)

External scheduling and task system integrations (Jira, Azure DevOps, Planner Premium)

❌ Not supported

✅ Supported

Altus integrates with multiple external scheduling and task systems, aligning with its multi‑tool unification approach (read the External Execution Tools documentation).

Enterprise global resource pool

✅ Supported

✅ Supported

Core enterprise resource pool capability retained (read Create and define bookable resources KB article for instructions and read the Bookable Resources documenation for more information)

What Altus resource pool currently supports:

• Resources can be created from scratch directly in Altus
• Resource type can be changed after creation
• Resources can only be deleted by users with administrator privileges.
• Resources can be mapped to equivalent resources in an MPP file when a schedule is linked
• Resources can be manually reconciled with external resources coming from schedules in other tools linked to Altus (referred to as Related Resources), enabling consolidated reporting and timesheets
• Generic (role-based) resources list is used for the primary role of named resources for better visibility in capacity and demand
  
  Important: Generic (role‑based) resources in Altus do not currently have a defined capacity value in the same way as named resources. Capacity calculations are applied to named resources only, with generic resources used primarily for role‑based demand planning and visibility.
  
• No requirement to check‑in, check‑out or force-check-in bookable resources when editing, simplifying administration compared to legacy approaches
  
• RBS (Resource Breakdown Structure) equivalent
  
  Important: Instead, security access can be managed through Business Units, which provide a comparable way to control visibility and access across the organisation (read the Security for documenation on how to implement the Business Unit model).
• Booking types for task assignments (committed vs proposed) although this is handled differently in Altus exclusively for resource planning rather than for scheduling and time tracking via timesheets
  

What Altus resource pool does not support yet:

• Bulk edit all resource attributes at once (read Bulk edit multiple bookable resources KB article for instructions).
  
  Important: Altus still supports bulk editing of resources albeit via the Excel Online method only, with additional inline bulk‑edit capabilities available when enabled through Power App Maker configuration.
  
• Ability to open all resources for bulk editing using Microsoft Project (MSP)
• Self‑service import/export of multiple resources, except when using an Excel Online–based method from a system view.
• Auto‑populated resource name from the associated user account or through Entra-ID-based resource pool synchronisation and option to create resources directly from user accounts via Altus Settings
  
  Important: Altus still supports automated resource creation, resource‑to‑user association and naming alignment but these are managed through the Power Platform Admin Centre (e.g. Settings > Users area and typically with configuring Entra ID group membership at the environment level (e.g. Environment > Settings > Teams) rather than being auto‑generated within Altus.. Once configured, user information can be reflected consistently across resources.
  
• Self‑service creation of custom resource fields via Altus Settings
  
  Important: Custom resource fields are managed through Power App Maker rather than self‑service Altus settings, aligning with best‑practice platform governance and ensuring configurations are consistently maintained across environments.
• Team Pool or Assignment Pool features
• Non‑labour resource types (e.g. work vs budget, cost and material resources managed in an MPP file do not currently translate into the Altus financial grid or resource pool as they are handled differently in Altus except for time-phased costs of in-flight projects that were imported to your current Altus environment as part of the one-off data migration (read the Enhanced Project Online Migration Accelerators - Altus Product Roadmap card for more information).
• Option to require resource approval before being assigned to project tasks (assignment) because resource planning and task scheduling are separately handled in Altus.
  
  Important: Whilst task‑level resource approval is not enforced out of the box, it can still be configured through Power Automate to align task assignment with resource approval processes.
  
• Option to enforce resource levelling in the schedule

Global resource pool across multiple scheduling tools

❌ MSP‑only

✅ Cross‑tool

Altus extends the resource pool across Project, Planner, and other schedules (read the External execution tool configuration and synchronisation documentatrion on this feature).

Important:

• Bookable resources in Altus should still be manually reconciled with external resources coming from schedules in other tools linked to Altus projects (referred to as Related Resources) enabling consolidated reporting and timesheets (read Associate sync external resources to named resources KB article for instructions).
• This mapping is currently not available for generic resources (follow the Mapping Generic Resources with External Resource - Altus Product Roadmap card for updates on this feature).

Named and Generic (role‑based) resources

✅ Supported

✅ Enhanced

Parity retained. Both platforms support role‑based planning using generic resources (read Create and define bookable resources KB article for instructions).

Important:

• Generic (role‑based) resources are used to represent the primary role of named resources, improving visibility across capacity and demand which can also be requested for fulfilment within a project’s resource plan (read Create and update resource requests in the resource plan for instructions).
• Altus supports skills‑based resource modelling through generic roles; however, only one primary role can be assigned to a named resource, unless a custom set of resource skill fields are implemented by an Altus partner (follow the Skills-Based Resourcing - Altus Product Roadmap card for updates on this feature).

Target (planned) resource allocation

✅ Supported

⚠️ Partial

Capacity can be planned before assigning named resources (read the Review and commit work resources to projects KB article for instructions).

Important:

• Altus does not currently provide an option to require resource approval before assignment to project tasks. In Altus, resource approval is applied at the resource demand and fulfilment stage (typically by a line manager), rather than enforced at task‑level scheduling as it can be in Project Online.
• While Altus supports a Target Utilation percentage per resource, this value is indicative only and does not actively calculate or constrain capacity. This differs from Project Online’s Current Max Units, which defines resource capacity and automatically flags overallocation when assignments exceed that threshold (follow the New Resource Dashboard - Altus Product Roadmap card for updates on the new reports)

Formal resource requests and commitments

✅ Supported

✅ Supported

Resource demand can be requested (proposed work) and fulfilled (committed work) across initiatives formally (read Review and commit work resources to projects KB article for instructions and the Resource Plan documenation for more information).

What Altus resource planning currently supports:

• Scheduled column to reflect planned hours from resource assignments in the schedule versus the Proposed and Committed hours in the resource plan
• Resource requests support comments to formally record agreements between the project manager and line manager
• Resource hours shifting to adjust allocations
• Surfaces variances via Insights reports, comparing requested and committed work against schedule forecasts and timesheet actuals.
• Defaults the line manager as the fulfiller of resource requests, with automatic notifications.
• Generic resources are substituted with named resources.
• Named resources can be directly allocated to projects (comitted hours) without a formal request via the resource plan (proposed hours) as an option.

What Altus resource planning does not supaport yet:

• Real‑time MSP alerts or visual indicators when hours allocated in resource plans and schedule assignments are misaligned or out of compliance.
  
  Important: WIthin the Altus app, this is handled by instantly creating a resource plan from a schedule (read the Create a resource plan from the schedule KB article for instructions) to ensure consistent alignment albiet with restrictions (i.e. not possible if committed work hours exist in the resource plan) when the demand shifts (read Align project resource requests to the project schedule KB article for instructions on shifting the resource request).
  
• Visibility of proposed and committed hours from the resource plan directly within the schedule.
• Ability to resolve out‑of‑compliance hours directly in the schedule when there is variance between task assignments and committed resource hours i.e. this is currently managed through Insights reporting rather than interactively within the schedule.
• Ability to subscribe to resource request alerts for selected resources being requested for projects

Resource capacity and demand management

✅ Supported

✅ Enhanced

Dedicated forward‑looking capacity planning and compliance tracking supported (read the Availability Heatmap and Resource Demand documentation for more information);

Important:

• Capacity vs demand forecasting is facilitated across key initiatives in Altus –from proposals to projects and broader portfolio‑wide view.
• Resource heat map (capacity vs commitments) and Insights reporting visualise over‑ and under‑allocation against committed and scheduled work in daily, weekly, monthly, quarterly, and yearly views (see Identify and resolve resource overallocations KB article and follow the Improvements to Resource Heatmap and Demand - Altus Product Roadmap card for updates on this feature)
• Inisights reporting in Altus also includes resource utilisation, remaining availability, and work by resource (read the Resource Insights documenation for more information)

Enterprise calendars (resource calendars)

✅ Supported

✅ Limited

Parity retained. Enterprise‑wide working calendars are available in both platforms (read the Enterprise Calendars documenation for more information)

Important:

• Enterprise calendars in Altus apply only to resource capacity and demand planning, not to task‑level scheduling as resource planning and scheduling are handled separately in Altus (read the Set-up and maintain calendars KB article for instructions).
• No requirement to check‑in, check‑out or force-check-in enterprise calendars when editing, simplifying administration compared to legacy approaches
• While multiple enterprise calendars can be created to define standard working times and non‑working exceptions (e.g. statutory holidays), they can only be assigned to bookable resources, affecting capacity calculations but not task dates or scheduled work.
• Altus does not currently support calendar duplication or recurring events, as was available in Project Online enterprise calendars managed via Microsoft Project which means public holidays and non‑working days must be recorded and maintained per calendar at the moment.

Time‑phased resource cost and sell rates

✅ Supported cost only

✅ Supported (cost and sell)

Forecast labour costs are calculated from planned or committed allocations via resource planning, with actuals captured from approved timesheets, and multiple cost rates per resource over time are reflected in the project financials.

Important:

• Altus allows cost and sell rates (where revenue tracking applies) to be maintained per resource to support labour cost forecasting, with effective dates retained to reflect rate changes such as CPI increases (such as CPI increases) to be reflected over time (read the Set up and update resource rates KB article for instructions).
• Resource work hours from the resource plan (using proposed, committed hours or the higher value) can be imported into the project financials as labour forecast cost or sell values, noting the hover‑over tooltips revealing the rate and hours applied to users by default (read the Resource Plan as Financial Forecast documentation on this feature).
• These hours can also be synchronised with timesheet actuals to calculate labour actual costs in the project financials (read the Timesheet to Finance Actuals Sync documentation on this feature).
• Labour costs in Altus are managed at the resource planning level only and do not apply to tasks in the schedule, as task‑level cost tracking is not currently supported (follow the Altus Tasks - Time Phased Effort and Resourcing - Altus Product Roadmap; Altus Tasks - Enable Task Financials - Altus Product Roadmap and Categorising Resource Cost - Altus Product Roadmap cards for updates on these features).
• Sell rates can be overridden per resource at a project level to support negotiated client or vendor rates; however, cost rate overrides are not currently available. This differs from Project Online, where multiple cost rate tables (A–E) in Microsoft Project could be applied to support different roles, pay scales, task types, or currency conversions.
• Overtime rates and cost‑per‑use values, plus multi-currency are not currently supported within Altus resource rate features (follow the Multi-currency Management - Altus Product Roadmap card for this feature)
• Time‑phased costs for in‑flight projects are retained during the one‑off migration to Altus (follow the Enhanced Project Online Migration Accelerators - Altus Product Roadmap card for more information on its impending release).
• Importing financials from linked mpp files for ongoing use is tracked under Import Financials from your Altus for Project plan - Altus Product Roadmap card for more information on its impending release).

Material (non‑labour) resources

✅ Supported

❌ Not currently supported

Altus resource model is labour‑centric today.

Important:

• Non‑labour resource types (e.g. work vs budget, cost and material resources managed in an MPP file do not currently translate into the Altus financial grid or resource pool as they are handled differently in Altus (read the Define and adjust the project financial forecast KB article for instructions on managing non-labour cost)
• Except for time-phased costs of in-flight projects that were imported to your current Altus environment as part of the one-off data migration (read the Enhanced Project Online Migration Accelerators - Altus Product Roadmap card for more information; follow the Altus Tasks - Enable Task Financials - Altus Product Roadmap and Import Financials from your Altus for Project plan - Altus Product Roadmap | Product Roadmap cards for updates on these features).

External HR system integrations

❌ Not supported

✅ Supported

Altus supports HR system integrations to enrich resource data through an implementation partner (visit the Integrations section of the Altus website),

Timesheets

✅ Supported

✅ Supported

Core capability retained (read the Track progress using timesheets KB article for instructions and the Timesheets documentation for more information).


What Altus Timesheets currently support:

• Altus supports two (2) modes of time entry:
• • Project mode, where users record time against projects they have committed work to through the resource fulfilment (not tasks from the schedule)
  • Project Task mode, where timesheets are populated from task assignments across project schedules (whether native Altus schedule or mpp files) for a familiar task‑based experience.
• Project managers can lock tasks in the schedule for timesheeting out of the box, with this control synchronised with Microsoft Project Desktop.
• Users can record time against both assigned project work and non‑project line items.
• Time entry is captured in hours only, enabling precise and consistent effort tracking.
• Approved timesheet actuals can be:
• • Applied to schedules as actual work, updating task progress % in the schedule (whether native Altus schedule or mpp files; read the Timesheet to Task Actuals Sync documenation)
  • Imported as labour actual costs in the project financials using the set resource rates (cost or sell; read the Timesheet to Finance Actuals Sync documentation)
• Compliance reporting and Insights dashboards provide strong visibility into:
• • Timesheet submission and approval status
  • Variances between timesheets, committed resource plan hours, and schedule forecasts (read the Resource Insights documentation)
• Automatic notifications are sent to timesheet users and timesheet managers as part of submission and approval workflows.
• Visibility of task assignments and notifications is enabled when a project is associated with a Microsoft 365 Group (follow the Enhanced Timesheet Access Control - Altus Product Roadmap card for updates on this feature).

What Altus Timesheets do not currently support:

• Time entry in days or FTE is not supported.
• Timesheets are submitted as a complete timesheet (project and non-project) rather than allowing sending progress for selected tasks or project-related rows only for interim status reporting.
• Project work hours are approved by the timesheet manager only:
• • There is no separate status manager or project manager approval step.
  • Project managers currently do not have visibility into timesheet approvals or reports.
• While users can select from existing assignments and non‑project lines, there is no ability to:
• • Create new tasks from the timesheet
  • Add personal tasks
  • Add overtime or non‑billable ad‑hoc rows
  • Export to Excel or print timesheets rows
  • Reassign tasks to another resource via the timesheet
  • Autofill or replacement of actuals based on planned values.
• Total planned, remaining and actual work (for the overall task) and assignment information (timesheet user's portion of work) are presented at a summary level only via columns (view the Assigned vs Actual Hours in Timesheets - Altus Product Roadmap card for more information) )and hover-over tooltips, without:
• • Time‑phased (day‑by‑day) view of planned row versus actual rows
  • Inline visibility of task progress, start/end dates, duration, hierarchy (summary task), baseline work/cost, or dependencies as columns.
• Detailed task context (e.g. dates and assignment detail) is available via hover‑over tooltips, rather than interactive task views.
• Other task‑level context such as task-level notes; recent task change history, attached risks or issues, related assignments based on dependencies, other resources assigned to the same task or project group and project manager details are not surfaced within the timesheet experience.
• Timesheet actuals flow to the schedule and financials, but do not write back to the resource plan by default (evenin Project mode).
• Notifications are not sent to the line managers by default (read the Timesheet Approvals for more information)
• Visibility of task assignments and notifications requires the project to be associated with a Microsoft 365 Group for collaboration (follow the Project Access Without Microsoft 365 Groups - Altus Product Roadmap card for updates on this feature).

Timesheets in Microsoft Teams

❌ No

✅ Supported

Timesheet users can access their timesheets via the My Timesheet tab in the Altus app if installed in Microsoft Teams to reduce context switching (read the Track progress using timesheets KB article for instructions and follow the Altus Timesheet Entry in Microsoft Teams - Altus Product Roadmap card for updates on a related feature).

Daily timesheet commentary

❌ Limited

✅ Supported

Timesheet users can add daily comments to their entries to add qualitative insight to time capture (read the Track progress using timesheets KB article for instructons).

Important: Unlike Project Online, Altus does not require overall timesheet comments on submission; however, timesheet daily comments are not currently visible to project managers or reports.

Sync timesheet actuals to Project Desktop

✅ Supported

✅ Supported

Parity retained. No double‑handling of actuals in the mpp file (read the Import approved timesheet actuals into the Microsoft Project Plan (MPP) KB article for instructions)

Important: Follow the Altus for Project - Enhanced Actuals Management - Altus Product Roadmap card for more information on preserving actuals from in-flight projects migrated into Altus)

Non‑project time capture

✅ Supported

✅ Supported

Parity retained. Operational and non‑project effort is supported (read the Track progress using timesheets KB article for instructions).

Budget / Forecast / Actuals

✅ Supported

✅ Supported

Core financial tracking essentials are retained in Altus even though its financial grid feature behaves fundamentally different from that in Project Online, (read the Financials documentation, and these KB articles for instructions: Record and update the project budget, Define and adjust the project financial forecast and Update and validate actual cost monthly

Important: Follow the Lock Custom Financial Transactions at Project Level and Top-down Budgeting - Altus Product Roadmap cards for updates on these relevant features.

Time‑phased financials

✅ Limited (schedule-driven)

✅ Supported

Extended through scenario modelling and focused on financial scenario planning (read the Project Configuration documenation for fiscal periods and performance analysis)

Important: Follow the Altus Tasks - Enable Task Financials - Altus Product Roadmap and Import Financials from your Altus for Project plan - Altus Product Roadmap | Product Roadmap cards for updates on related feature requests.

Earned Value Management (CPI/SPI)

✅ Supported (schedule-driven)

❌ Not currently available

Unless delivered through a custom report or system developed by an implementation partner, classic Earned Value Management (EVM) is not available by default but existing EVM information can still be imported into Altus by mapping task‑level fields from Microsoft Project Desktop via the Altus for Project connector and Power App Maker, if needed.

Schedule / Cost Variance (SV/CV)

✅ Supported (schedule-driven)

⚠️ Partial

Emphasis is on forecast impact rather than EVM calculation (read the Project Financials documenation for finance grid variance calculation)

Important: Follow the Altus Tasks - Enable Task Financials - Altus Product Roadmap and Import Financials from your Altus for Project plan - Altus Product Roadmap | Product Roadmap cards for updates on related feature requests.

External finance system integrations

❌ Not supported

✅ Supported

Altus supports integration with external finance systems implemented through an implementation (visit the Integrations section of the Altus website)

Portfolio hierarchy and program management

❌ Not supported by default

✅ Supported

Stronger portfolio and program governance than Project Online (read the Portfolios and Programs documentation; and the Define a new portfolio and program and Drill-through Portfolio and Program insights KB articles for instructions)

Important:

• While there is no direct equivalent of master schedules in Altus yet, a similar outcome can be achieved with roll-up of schedule and financial data (follow the Top-down Budgeting - Altus Product Roadmap card for updates on this relevant feature) both at a program and portfolio level (read Altus Portfolio documentation and discover the Timelines view from the Drill-through Portfolio and Program insights KB article).
• Unless custom-configured by an implementation partner, registers managed at the project level do not roll up to portfolio‑level and program-level registers in Altus by default (follow the Viewing Project Items from Portfolios and Programs - Altus Product Roadmap card item for an update on this feature).
  
  Important: Altus supports reporting roll‑ups of these project support items at the portfolio and program levels, available through status reports and selected Insights dashboards, providing aggregated performance visibility across initiatives.
  
• Follow the Portfolio & Program Management Enhancements - Altus Product Roadmap card for updates on this feature request.

Demand and idea intake

❌ Not supported by default

✅ Supported

Retained and improved (read the Ideas documentation and the Create and submit ideas for innovation KB article for instructions)

Important: Follow the Generate Projects from Ideas and Linking Ideas and Proposals to Portfolios/Programs - Altus Product Roadmap cards for updates on these features. Optionally, follow the Considering Deprecating Challenges - Altus Product Roadmap card for updates on relevant feature.

Proposal management

❌ Not supported by default

✅ Supported

Altus supports formal proposal management as part of demand intake (read the Proposals documentation and the Create and submit project proposals KB article for instructions)

Important: Follow the Extension of the Proposal capabilities and Proposal-to-Project Traceability - Altus Product Roadmap cards for updates on these features.

Project prioritisation models

✅ Single model (pairwise comparison)

✅ Multiple models

Enables more nuanced prioritisation

Important: Read the Prioritisation documentation and the Perform a prioritisation exercise KB article for instructions and follow the Manual Rank Override for Portfolio Prioritisation and Enhancements to Prioritisation - Altus Product Roadmap cards for updates on these features)

What‑if scenario planning (resource and budget)

✅ Supported

✅ Enhanced

Advanced strategic optimisation and time-phased resource-aware and cost-based portfolio scenarios are supported in Altus (read the Optimisation documentation and Perform an optimisation exercise KB article for instructions)

Strategic alignment

❌ Not supported

✅ Supported

Altus explicitly supports strategic alignment of initiatives (read the Altus Strategy documentation and Create and edit strategic themes and Create strategic goals within strategic themes and Drill-through Strategy Insights KB articles for instructions)

Benefits tracking

❌ Not supported

✅ Supported

Benefits tracking is provided by Altus as part of strategic management (read the Benefits documentation and the Capture project, portfolio, and program benefits KB article for instructions)

Stage‑gate governance

✅ Supported

✅ Supported

Governance continuity maintained (read the Altus Projects documentation for information on Business Process Flows or BPF in Altus)

Workflow engine, approvals and controls

Project workflows

Power Automate

Easier to extend and maintain (read the Altus Deployment and Automation documentation for information on automated flows deployed in Altus by default).

RAID registers

✅ Supported via SharePoint sites

✅ Native

Full parity retained (read the Altus Registers documentation for a full list and read the Manage project issues and Manage project risks KB articles as examples)

Important:

• Unless custom-configured by an implementation partner, registers managed at the project level do not roll up to portfolio‑level and program-level registers in Altus by default.
  
  Important: Altus already supports reporting roll‑ups of these project support items at the portfolio and program levels, available through status reports and selected Insights dashboards, providing aggregated performance visibility across initiatives.
  
  The new program and portfolio governance reports provide relevant insights in this area, and it is relatively straightforward to expose and adjust report‑level filters to support the required analysis (watch this Portfolio and Program Dashboard | Feature Demo for instructions)
  
• Follow the Viewing Project Items from Portfolios and Programs , Connecting Registers and Action Register: Altus Product Roadmap cards for updates on these features.

Audit history

✅ Supported

✅ Supported

Comparable compliance capability (read the System settings documentation on enabling audio logging consideration and risks)

Built‑in reports and Power BI integration

OData‑based (and/or via Reporting Hub retired April 2026)

Native datasets (Dataverse)

Faster, simpler, and more reliable:

Useful links:

• Read the Insights documentation for Power BI reports
• Read the Gathering Altus Insights with Power BI KB article for instructions
• Read the Reporting for more technical information
• Read the New Standard Reports and Paginated Reports documentation for more information

Custom reporting

✅ Supported

✅ Supported

Improved data model in Altus (access the Data Models and Reports documentaion for the latest report packages to deploy)

Executive dashboards

✅ Supported

✅ Goal‑focused dashboards

Optimised for decision‑makers (read the Strategic Insights for more information and New Power BI Standard Reports 3.2 for the latest dashboard releases)

Excel exports

✅ Supported

✅ Supported

No regression.

Microsoft Teams integration and embedded Teams project experience

❌ Limited

✅ Native

Core project interactions and collaboration inside Teams (read the Use the Altus for Teams app KB article for instructions and Altus for Teams documentation for more information)

Important: This feature requires project to be associated with a Microsoft 365 Group for collaboration (read the Build and manage the project group for collaboration KB article for instructions and Groups and Teams documentation for more information).

SharePoint document management

✅ Supported

✅ Supported

Retained with modern UX. This feature also requires project to be associated with a Microsoft 365 Group for collaboration (read the Manage project documents KB article for instructions)

Important: OneDrive synchronisation with project document libraries is supported, providing a native offline/online document experience with automatic sync for users.

Power BI, Word and other Microsoft 365 native integrations

Limited

✅ Native sync

Reduces reporting administration.

Useful resources:

• View the Integrations section of the Altus website for more information
• Read the Altus for Project documentation
• Read the Altus For Word documentation (also follow the Link a Portfolio / Program or Proposal to Microsoft Word - Altus Product Roadmap |card for updates on this feature request)
• Read the Synchronise Altus Information in a Microsoft Word Document KB article for instructions)
• Read the Altus for Teams documentation
• Read the Insights documentation for Power BI reports and Gathering Altus Insights with Power BI KB article for instructions)
• Read the External Execution Tools documentation and External execution tool configuration and synchronisation for instructions).

Copilot / AI assistance

❌ Not available

✅ Supported

New capability, not parity‑based. Altus includes Copilot‑enabled, AI‑assisted capabilities (read the Altus Copilot dociumentation for more information).

Important: Altus also features an AI chat embedded within its built-in Altus Help capability (read the Altus Help documentation and Navigating the Built-in Help KB article for instructions).

Planner ecosystem integration

❌ Not supported

✅ Supported

Aligns with Microsoft’s future tooling direction (read the Synchronise Planner Premium Task Assignments with the Altus app KB article and Microsoft Planner documentation)

Telemetry and Analytics

✅ Limited via Site Settings > PWA Usage

✅ Supported

Altus provides selected usage telemetry via the Power Platform Admin Centre, with additional telemetry maintained internally by Altus (read Telemetry for more information).

Project Online | PWA Settings

How This Is Managed for Altus PPM

A. Security and Access Management

Permission Mode

• SharePoint Permission Mode
• Project Permission Mode (groups, categories, RBS‑based security)

Groups and Categories

• Manage Groups
• Manage Categories
• Manage Group Membership
• Category Permissions (Projects, Resources, Views, Data)
• Check Effective Rights

Identity and External Access

• Manage Users
• External User Access
• Site Collection Administrators (override access)
• Connected ShrePoint Sites

• User management, security roles, and permission assignments are handled through the Power Platform Admin Centre, at the environment level where the Altus app is deployed (read the Security documentation for tehcnical guidance).
• This requires System Administrator privileges, which are broader than the standard Altus Admin role.
• A third‑party browser plugin compatible with Power Apps can be installed to impersonate a user and check their effective permissions (e.g. Level-up for Dynamics plug-in). Alternatively, the built‑in Check Access feature is available on individual records within Altus, allowing users to view their access rights instantly.
• Altus does not use dedicated project site management settings; collaboration and document access are managed through Microsoft 365 group membership (read Groups and Teams documenation for information) with settings controlling group ownership and creation across initiatives (read the Altus Configuration Settings documentation for information on settings related to group ownership).
• Implementation partners can extend Altus security roles and permission models to support more complex access control scenarios, based on required customisations and enhancements.

B. Enterprise Data

Enterprise Custom Fields and Lookup Tables

• Enterprise Project Fields
• Enterprise Task Fields
• Enterprise Resource Fields
• Departmental Custom Fields
• Lookup Tables (single & multi‑level)
• Required / Calculated / Formula fields

Calendars

• Enterprise Calendars
• Base Calendars
• Resource Calendars
• Exceptions (holidays, non‑working time)

• Standard and custom forms, fields, lookup tables and formulas for Altus are managed via the solution layers in Power App Maker, not self‑service in the Settings area of Altus, and require Environment Maker or higher privileges (follow the Department Management Configuration - Altus Product Roadmap card for an example of a relevant feature request).
• Implementation partners can extend the Altus Settings area with a data management section to enable controlled self‑service of selected lists and lookup tables.
• Enterprise calendars (for resource capacity and demand management, not for task scheduling) are available in the Resources > Enterprise Calendars area of Altus for self-service management (read the Enterprise Calendars documentation for information and Set-up and maintain calendars KB article for instructions)

C. Projects and Enterprise Project Types (EPTs)

Enterprise Project Types

• Create / manage EPTs
• Associate Project Detail Pages (PDPs)
• Associate Workflows
• Control project creation behaviour
• Schedule and site template

Project Detail Pages (PDPs)

• Project Summary PDPs
• Custom PDPs
• Field placement and layout
• Web parts and sections

Project Settings

• Unique Project ID configuration
• Project naming rules

• Project types are available in the Settings > Project Configuration area of Altus (read the Project Configuration for information on project types)
• Self‑service management is limited to general project type information, showing or hiding tabs relevant to the project type, and workflow association
• Implementation partners can extend project types in Altus to enable additional project templating scenarios, such as document structures, schedule templates, and predefined project registers, where required (follow the Project Content Templating - Altus Product Roadmap card for this feature request)
• Standard and custom forms and pages (equivalent to Project Detail Pages in Project Online), as well as project ID and naming rules, are managed through solution layers in Power App Maker, not via the Altus Settings area; and require Environment Maker or higher privilege (follow the Setting - Hide Sections on Form Config setting - Altus Product Roadmap card for updates on a related feature request).

D. Workflow and Demand Management

• Demand Management configuration
• Restarting Workflows and Changing Project Types
• Workflow Phases
• Workflow Stages
• Stage behaviors (required fields, validation)
• Workflow status tracking

• Project lifecycle workflows are managed via Power Automate in Power App Maker solution layers, not via the Altus Settings area; and require Environment Maker or higher privileges (read the Altus Projects documentation for information on Business Process Flows or BPF in Altus)
• Where administrator rights are not required, end users can reset the project lifecycle or move a project back to a previous stage using the BPF associated to the project type. However, once a project lifecycle is closed or marked finished, re-activating it requires an administrative action via background processes.
• Changing the project type for multiple projects in bulk can be performed self‑service by users through the available system views in Altus.
• Implementation partners can extend Altus workflow capabilities to support controlled stage‑gate checklists, as well as simple to complex stage‑gate approval mechanisms and approval centre views, where required.

E. Resource Management

Resource Center Configuration

• Activate Resource Center
• Resource attributes visibility
• Generic vs Named resources
• Active Directory Enterprise Resource Pool Synchronization

Resource Engagements

• Enable Resource Engagements
• Engagement approval settings
• Replace legacy Resource Plans

RBS (Resource Breakdown Structure)

• Define RBS
• Use RBS for security and reporting

• Self-service management of bookable labour resources (generic, named, and external) is facilitated in the Resources > Resources area of Altus (read Bookable Resources documentation and Navigate the Resources area KB article for instructions)
• Unless custom-built by an implementation partner, Altus does not support Entra ID–based Enterprise Resource Pool synchronisation by default as bookable resources are managed independently within the platform.
• Self-service management of resource engagements (or Resource Demand in Altus) is facilitated in the Resources > Resource Demand area of Altus (read Resource Demand documentation and Review and commit work resources to projects KB article for instructions).
• Altus does not use an RBS model; instead, security access can be managed through Business Units, which provide a comparable way to control visibility and access across the organisation (read the Security for documenation on how to implement the Business Unit model).

F. Time and Task Management (Timesheets)

Timesheet Setup

• Enable / disable timesheets
• Timesheet periods
• Default timesheet mode

Time and Task Progress Settings

• Time vs Task progress capture
• Actuals entry rules
• Status manager configuration
• Approval routing (Timesheet Manager vs Status Manager)

Non‑Project Time

• Vacation
• Sick leave
• Administrative categories

• Self-service management of timesheet settings is facilitated in the following areas of Altus:
  
  a. Initiatives > Work > Current Timesheet area for completing and recalling timesheets by the resources (read the Track progress using timesheets KB article for instructions)
  
  b. Initiatives > Work > Current Timesheet > My Timesheets area for managing previous, current, and future timesheets by the resources for completing and recalling timesheets by the resources (read the Track progress using timesheets KB article for instructions)
  
  c. Resources > Timesheet Approvals for reviewing, recalling, approving, and rejecting resource timesheets by their timesheet managers (read the Review and approve submitted timesheets KB article for instructions).
  
  Important: In Altus, project work hours (task progress) are approved by the timesheet manager only with no separate status manager or project manager approval step. Project managers currently do not have visibility into timesheet approvals or reports by default. Approved timesheet actuals can still be applied to the project schedules to drive task progress.
  
  d. Settings > Resources > Timesheet Periods for the bulk creation and closing/opening of timesheet periods by the administrator (read the Timesheets documentation for information on timesheet periods).
  
  e. Settings > Resources > Non Project Time for the creation and management of non-project time rows across resource timesheets by the administrator (read the (read the Timesheets documentation for information on non-project time).
  
  f. Settings > System Configuration > Configuration Settings > Timesheets for general and timesheet finance sync settings by the administrator (read the Timesheets, Timesheet to Finance Actuals Sync, Active Fiscal Periods, and Fiscal Year documentation for information on related settings).
  
• Automatic notifications sent to timesheet users and timesheet managers as part of submission and approval workflows are managed via Power Automate in Power App Maker solution layers, not via the Altus Settings area; and require Environment Maker or higher privileges (read the Automation documentation for information on automated flows deployed in Altus by default)
  
• Altus does not have a timesheet delegate feature; instead, approvers use filters on the Timesheet Approvals page to manage other users’ timesheets (read the Act as a timesheet delegate KB article for instructions).
  
  Important: Administrators may use impersonation via third‑party Power Apps browser plugin (e.g. Level-up for Dynamics plug-in) for troubleshooting or support purpose but this capability is not intended for end‑user delegation.
  
• Implementation partners can extend Altus timesheet capabilities to support integration with external financial systems and related settings for self-service management in the Altus app.

G. Portfolio Analysis and Optimization

Business Drivers

• Define business drivers
• Weighting models

Portfolio Analyses

• Create portfolio scenarios
• Cost modeling
• Resource modeling
• Constraint definitions
• Scenario comparison and commitment

• Altus Strategy includes built‑in prioritisation and optimisation capabilities. Self‑service management of the related settings—used to implement, configure, and maintain these capabilities—is available in Settings > Configuration Settings > Strategy within Altus (read the Configuration > Strategy General Settings for information).
  
• Read the Altus Prioritisation and Prioritisation documentation for technical information and Describe the requirements for the prioritisation process KB article for instructions.
  
• Read the Optimisation documentation for technical information and Perform an optimisation exercise KB article for instructions).

H. Reporting and Data Access

Reporting Infrastructure

• OData feed configuration
• Reporting permissions
• Time‑phased data roll‑up settings

Power BI and Excel

• Configure reporting access
• Data refresh considerations

BI Center

• Permissions inheritance
• Data exposure settings

• Altus provides faster, simpler, and more reliable BI reporting, supported by a continuously improving data model (read the Insights documentation for Power BI reports and the Gathering Altus Insights with Power BI KB article for instructions).
• Report‑related configuration is primarily managed within the Power BI workspace deployed for Altus Insights and requires Owner, Report Author and/or Administrator privileges in Power BI for the Altus environment and Power Platform Dataverse (read the New Standard Reports and Paginated Reports documentation for more information; and the Data Models and Reports documentaion for the latest report packages with improved data models for Altus.
• These reports are then surfaced in Altus through self‑service settings under Settings > System Settings > Configuration Settings > Power BI Insights (read the Altus Configuration Settings documentation for information this setting)
• Implementation partners can extend Altus BI capabilities to support data modelling and integration with external systems and related settings for self-service management in the Altus app.

I. Queue and Database Administration

Queue Management

• Manage Queue Jobs
• Job History
• Retry / cancel jobs

Database Settings

• Delete Enterprise Objects
• Force Check-in Enterprise Objects
• Cleanup and maintenance tasks

In Project Online, queue and database administration were explicit administrator responsibilities. In Altus, these functions are handled by the Power Platform and Dataverse, reducing administrative overhead while improving reliability and scalability (visit the publicly available Overview of the Power Platform admin center - Power Platform website from Microsoft Learn for more information).

These functions are handled through a combination of platform‑managed services requriing environment-level administrator privieleges rather than a single queue UI:

• Queue processing is handled by the Power Platform and Dataverse services
• Background processing runs as Dataverse asynchronous system jobs and Power Automate flows, which are managed and monitored at the platform level.
• Administrators do not manually retry or cancel queue jobs in the same way as in PWA.
• Execution history and failures are visible through:
  • Power Platform Admin Centre > Environment > Settings > System jobs
  • Power Automate run history for flows used by Altus (success, ailures, retries)
  • Solution deployment history in Power App Maker
• Retries and error handling are managed through Power Automate flow configuration and platform retry logic, rather than manual queue intervention. Failed processes are typically remediated by adjusting flows or data, not re‑running queue items.
• The Project Online database is replaced by Dataverse, which is fully Microsoft‑managed. There is no direct Altus administrator access to database tables, indexing, or performance tuning for manual maintenance
• Enterprise objects (projects, resources, assignments, financials, registers) are stored and governed within Dataverse tables and managed via Altus solution layers, rather than direct database administration.
• Cleanup, optimisation, indexing, and maintenance are handled automatically by the Power Platform. Administrators manage:
  • Environment health
  • Storage capacity
  • Audit and retention policies
  via the Power Platform Admin Centre, rather than performing manual cleanup tasks.
• Altus does not require check‑in/check‑out of enterprise objects; however, deletion of key records (Projects, Programs, Portfolios, and Resources) is governed by protective controls within Altus Settings > System Settings > Configuration Settings > Security section (read the Altus Configuration Settings documentation for information on these settings).

J. System and Look‑and‑Feel

UI Customization

• PWA branding
• Logo and theme branding
• Enterprise views (Project Center, Resource Center, Task views)
• Tables, filters, and groupings
• View sharing and standardisation across users
• Navigation links
  

Personal Settings

• Manage My Alerts and Reminders
• Manage My Resources' Alerts and Reminders
• My Queued Jobs
• Notification behaviors
• Act as a Delegate

Regional and Language Settings

• Supported languages
• Locale behavior
  

• In Altus, UI behaviour and layout are defined by the app design, rather than configured through administrator‑defined views. Page layouts and experiences are delivered as part of the model‑driven Power App (read the Altus Solution Architecture, Solution Layers, and Customisation documenation for more technical information).
• Altus uses Power Platform and Microsoft 365 environment‑level modern UI theming, enabling branding alignment through logos, colours, accents, and fonts managed directly in the customer environment. For setup details, see Microsoft’s guide: Modern Theme Overrides in Power Apps and preview how theme will look from this site.
• Enterprise views (e.g. Project, Resource and other system views) are no longer configured as administrator‑defined artefacts. Altus provides out‑of‑the‑box, role‑based views as part of the application experience.
• Tables, filters, and groupings (and formats) are not exposed as self‑service admin settings. Any changes to underlying system views require solution‑level changes and appropriate Power Platform privileges.
• While system views are administrator‑defined and read‑only for users in Altus, personal views from can be created and shared with other users (read the generic Create and manage personal views on a grid page KB article from Microsoft Learn for instructions).
• Schedule views are app‑controlled and limited to a Timeline (Gantt) view and a Board (Kanban) view. These are not Dataverse system views and are not managed through solution layers.
• Dataverse system views are defined within solution layers in Power App Maker, but they are primarily used for data access, filtering, and reporting, not for recreating PWA‑style enterprise views.
• Navigation links and layout are defined by the Altus app navigation model via Power App Maker, not configurable via settings or solution‑level view management.
• Nevertheless, certain aspects of the Altus user interface can be managed through self‑service settings under Settings > System Settings > Configuration Settings (read Altus Configuration Settings documentation for managing the homepage, landing page, grid cells, report viewer, tab visibility, resoucing heatmaps, and summary widgets).
• Implementation partners can extend Altus UI capabilities, from simple enhancements to more complex user experiences, where required.
  
• In Altus, personal settings are intentionally limited in favour of centralised governance, automation, and consistency, with configuration handled through platform services and solution layers rather than per‑user self‑service.
• Users without administrative rights do not have access to the Altus Settings area.
• Personal preferences such as time zone, date formats, and regional settings are managed through the standard Power Apps / Dynamics 365 personalisation settings (read the Set personal options article from Microsoft Learn)
• These settings affect the platform experience only and do not alter Altus‑specific behaviour.
• Altus does not provide individual self‑service personal alert configuration equivalent to PWA.
• Notifications are centrally managed through automations deployed and maintained in Altus solution layers via Power Automate (read the Solution Notification Config documeantion)
• Administrators can control:
  • Whether Altus automatically checks for out‑of‑date items
  • Which notification events are enabled (e.g. resource requests, proposal approvals, timesheets, resource plans).
• Where deployed, an implementation partner may provide a Notification Configuration feature to allow controlled customisation of alert behaviour.
• Notification behaviour is not user‑configurable at a personal level.
• All notification logic is defined through centralised automation, ensuring consistency across the organisation.
• End users in Altus do not have access to queue or background job visibility.
• Background processing is handled by the Power Platform and Dataverse services, with monitoring performed by administrators through the Power Platform Admin Centre rather than by individual users.
• Altus does not include a timesheet or task delegation feature equivalent to PWA (read page to manage other users’ timesheets (read the Act as a timesheet delegate KB article for instructions).
• • Administrators may use impersonation via third‑party Power Apps browser plugin (e.g. Level-up for Dynamics plug-in) for troubleshooting or support purpose.
  • This capability is not intended for end‑user delegation.

K. Performance and Limits

• Software boundaries and limits
• Performance tuning recommendations
• Customization considerations
• Resource Engagement performance guidance

• Read the Software boundaries and limits and Altus Data Handling Policy documentation for related information.
• Read the Customisation documentation for information on customisation considerations.

L. Site and Environment Management

• Add or delete PWA sites
• Change default PWA site (Project Home)
• Migration from Project Server
• License requirements
• Back up, archiving, and recovery
• Telemetry and analytics

• Site and environment management in Altus is handled through the Power Platform Admin Centre and requires environment‑level administrator privileges (read the Power Platform environments overview documentation for information)
• Product updates, release notes, and version details are available under Settings > Knowledge > What’s New, with release management handled via the Altus Hub portal (read the Altus Hub documentation for instructions).
• Project Online exposed limited usage telemetry via Site Settings; in Altus, telemetry is not user‑configurable, with selected usage insights available through the Power Platform Admin Centre and additional telemetry maintained by Altus (read Telemetry for more information).