Skip to main content
Lumos is a continuously evolving SaaS platform. New features, improvements, and underlying infrastructure updates ship on a regular cadence. This article explains how those changes are tested, deployed, and communicated, so you know what to expect and where to track what’s changing in your environment.

​
Where to Track What’s Changing

Lumos publishes product changes through several channels so you can stay informed at the level of detail you need:
  • Monthly release notes: A consolidated summary of major updates, platform changes, and customer-impacting enhancements. Published in the Help Center.
  • In-product notifications: Important UI or workflow changes are surfaced directly in the Lumos app when they affect Admin or end-user experiences.
  • Status page: Real-time visibility into platform health, incidents, and scheduled maintenance windows.
  • Your Customer Success Manager (CSM): For larger releases or changes that may require operational planning on your side, your CSM will reach out directly.

​
How Lumos Tests and Deploys Changes

Every change is validated before it reaches your production environment. The release process includes:
  • Automated testing: Unit, integration, and regression test suites run on every change.
  • Internal validation: Each release is exercised in internal Lumos environments before customer rollout.
  • Staged deployment: Larger platform or data-model changes are rolled out progressively, with rollout validation checkpoints between stages.
  • Backwards compatibility: Where possible, changes are designed to remain compatible with existing configurations and integrations to minimize disruption.
For larger platform changes, Lumos also evaluates customer operational impact as part of the release process before broader rollout.

​
Configurable Changes vs. Platform-Wide Changes

Lumos releases fall into two categories. Configurable changes are new features or behaviors that you can adopt at your own pace. These typically include toggles in Admin settings that let you enable, disable, or scope the change to specific users or groups. AI Insights in Access Reviews is one example. Configurable releases let you control adoption based on your team’s needs. Platform-wide changes are updates to underlying infrastructure, architecture, or security that apply to all tenants. These are not customer-configurable because they support the security, scalability, and reliability of the platform. This approach is standard for modern SaaS platforms and ensures every customer benefits from the latest improvements without operating divergent versions of the product. When a platform-wide change requires action on your side, Lumos communicates the timing, scope, and any preparation steps in advance through release notes, in-product notifications, and direct CSM outreach.

​
When Something Goes Wrong

If an issue arises after a release, the Lumos Support and Engineering teams engage quickly to investigate and resolve. You can report issues through the in-product help menu or by emailing support@lumos.com. Active incidents are also tracked on the status page. For questions about a specific change or to discuss operational planning for an upcoming release, contact your CSM or reach out to support@lumos.com.