Altus is continuously updated through structured release cycles that introduce new features, enhancements, and fixes.

To ensure your organisation remains aligned and prepared, it is essential to:

• Monitor release notes (what has been delivered)
• Review the product roadmap (what is coming next)
• Understand your organisation’s release management model
• Manage update behaviour through the Altus Hub console

Where to Start: “What’s New” in Altus

The primary entry point for release visibility is within Altus:

1. Navigate to Settings
2. Locate the Knowledge section
3. Select What’s New

This page displays:

• Your current solution version
• Embedded view of the Altus Product Roadmap
• Relevant updates aligned to your environment

👉 This allows you to cross-check:

• What has already been deployed
• What is planned for upcoming releases

Monitor Release Notes (Delivered Changes)

Release notes provide a detailed breakdown of:

• New features
• Enhancements
• Bug fixes
• Platform updates

👉 Refer to:
https://docs.altus.pro/products/AltusPPM/WhatsNew/Index.html

Release notes should be reviewed regularly, particularly when:

• Preparing for system updates
• Validating changes after deployment
• Communicating updates to users

Monitor the Product Roadmap (Upcoming Changes)

The Altus Product Roadmap provides visibility into:

• Features currently in development
• Planned enhancements
• Released capabilities

👉 Access the roadmap here:
https://portal.productboard.com/yyt7thvepjsnv8mh5ifqk1yo/tabs/3-released

The roadmap allows you to:

• Stay informed about upcoming changes
• Prepare training, communication, and adoption strategies
• Submit feedback and suggest enhancements
• Vote on existing features to influence development

👉 This acts as your direct feedback channel to the Altus product team

Understanding the Release Model

Altus follows a structured release process designed to ensure stability and predictability.

Key concepts include:

• Release train approach (scheduled updates aligned to defined cycles)
• Controlled rollout of features
• Validation activities before and after deployment

👉 Refer to the release checklist:
https://docs.altus.pro/products/AltusPPM/ReleaseChecklist.html?q=release

Understanding this helps you:

• Align internal change management processes
• Prepare for upcoming updates
• Validate system behaviour post-release

Release Management and Solution Layers

Altus is deployed using solution layering within Power Platform, which affects how updates are applied.

Key considerations:

• Managed vs unmanaged solutions
• Update propagation across environments
• Impact of customisations on upgrades

👉 Refer to:
https://docs.altus.pro/products/AltusPPM/AsBuilt/Releases/Solution-Layers.html?q=release%20manag

⚠️ Customisations may affect how updates are applied — always validate before and after upgrades

Managing Updates via Altus Hub Console

The Altus Hub (hub.altus.pro) provides administrative control over:

• Deployment status
• Update schedules
• Version management

👉 Refer to:
https://docs.altus.pro/products/LegacyProducts/SenseiHub/intro.html?q=hub

Depending on your configuration, your organisation may:

• Receive automatic updates, or
• Manage updates manually (controlled deployment)

This is typically managed by users with:

• Altus Hub administrative access

How This Impacts Your Organisation

Monitoring releases and roadmap ensures:

• You are aware of changes before they impact users
• You can prepare:
• • Training updates
  • Communications
  • Process adjustments
• You reduce risk during system updates
• You align with best practice release management cycles

Best Practice Approach

✅ Regularly check What’s New in Altus
✅ Review release notes before and after updates
✅ Monitor the product roadmap for upcoming changes
✅ Use Entra ID groups to manage rollout impact
✅ Validate functionality after each release

Important: Leverage Client Care or Partner Support

If your organisation has an active:

• Client care agreement, or
• Implementation partner relationship

👉 You should leverage this support to:

• Review upcoming releases
• Assess impact on your configuration
• Validate customisations
• Plan upgrades and testing

Key Considerations

• Altus updates are continuous and structured
• Product roadmap reflects actively evolving capabilities
• Release visibility is essential for adoption and governance
• Some updates may require preparation or validation

Tips

• Align release monitoring with your internal release cycles
• Use roadmap insights for future planning and adoption
• Engage stakeholders early when significant changes are coming
• Treat release notes as part of your operational checklist

This article:

• Completes your admin governance layer
• Connects product evolution → system administration → adoption
• Reinforces proactive (not reactive) managemen