QMS Audit Pro – October 2025 Release

We are pleased to announce the latest release of Lyons QMS Audit Pro, delivering improved security, smarter logic, and greater flexibility for local users. This update focuses on usability, data reliability, and product governance. This release reflects direct customer feedback and ongoing investments in scalability, compliance, and usability.

1. Azure Login Integration

Azure-based authentication is now fully integrated into QMS Audit Pro.

What this means for you:

• Log in using your company email address

• Improved security through enterprise-grade authentication

• Reduced password fatigue with centralized identity management

• Easier onboarding and offboarding of users

This enhancement aligns QMS Audit Pro with modern IT security standards and enterprise identity policies.

2. Image Upload Validation

What’s improved:

• The system now verifies and confirms successful image uploads

• Users receive clear confirmation before moving to the next step

• Prevents missing or incomplete audit evidence

• Ensures audit records remain complete and defensible

This update significantly improves confidence in photo-based audit documentation.

3. Mat Enhancements

We enhanced the Mat product category to capture deeper insights:

• Added a new question to collect more detailed information.

• Introduced smart logic so that when Mat is selected and Faded is chosen as a non-compliance reason, additional related questions appear automatically.

4. Manage Product Feature for Local Users

Local users can now create, edit, and manage their own products directly within QMS Audit Pro.

Key benefits:

• Faster setup for site-specific or regional products

• Reduced dependency on central administrators

• Greater flexibility for decentralized teams

• Better alignment with local operational realities

This feature empowers teams while keeping the system structured and controlled.

5. Product Type Classification

We introduced a new internal field called Product Type to improve visibility and governance.

How it works:

• All existing products are classified as Public (P)

• Any product created by a local user is classified as Local (L)

Why this matters:

• Clear separation between global and site-specific products

• Improved reporting and filtering options

• Better long-term scalability as product libraries grow