Who is this article for?

Administrators and solution owners interested in implementing Mazlan.

No specific access is needed.

Mazlan is embedded AI built into your Ideagen solutions — grounded in your data, your policies and global standards. Before your team can use it, three things need to be in place. The good news: Ideagen handles the heavy lifting. Your role is to confirm you're ready, and your account manager will guide you through every stage.

Step 1: You need to be hosted with Ideagen

Mazlan runs inside your Ideagen environment. It draws on your data, your SOPs and your standards — and to do that securely, your Ideagen solutions need to be hosted on Ideagen's cloud infrastructure.

If your organisation currently runs Ideagen products on-premise, this is the starting point. Your account manager will work with you to plan the migration. Your data stays within your region — UK, US or Australia — and within your existing security boundaries throughout.

If you're already hosted with Ideagen, you may be able to move straight to Step 2.

Step 2: You need to be on the modernised infrastructure

Once you're cloud-hosted, your environment needs to be on Ideagen's current, modernised infrastructure. This is the technical foundation that Mazlan is built on.

Again, Ideagen manages this process. Your team won't need to undertake technical work and you'll be kept informed of what's happening and when, and your account manager will coordinate the transition around your schedule.

Once the modernisation has been completed you will have some minor configuration changes to make on your environment:

• Whitelisting – Add the new domain to your organisation's allowlist so traffic and services aren't blocked post-migration.
• Mobile app configuration – Update the domain reference within your mobile app settings to point to the new URL.
• SSO configuration – If using single sign-on, add the new URL(s) to your SSO configuration to maintain uninterrupted authentication.
• Self-managed desktop updates – If you manage your desktop clients locally then you will need to deploy the appropriate update.
• Web reporting / DRS updates – Refresh base URLs used in web reporting and DRS, including any embedded hyperlinks, to reflect the new domain.
• Record attachment linkage – Where the application generates "locate record" links in user emails, update the file type association (e.g. to .qualitymanagement) so the desktop client correctly re-establishes the link between the file and the application.
• User record verification – Confirm every user has a primary email and username on file, as this is required for account continuity.

If you're already running on the modernised infrastructure, you may be able to move straight to Step 3.

Step 3: You need Ideagen Mazlan Home enabled

Ideagen Mazlan Home is where everything comes together: one login for all your Ideagen solutions. Mazlan AI is embedded within Mazlan Home, so enabling it is the final step before your teams can start using it.

Once Ideagen Mazlan Home is live, Mazlan AI is available inside your existing workflows. There is no new interface to learn, no separate tool to install.

You're Mazlan-ready!

When all three steps are in place, you are ready to experience Ideagen Mazlan. Your teams can ask questions, surface root causes, draft CAPAs and search records — directly within the workflows they already use. Mazlan prepares the output. You review and approve. You stay in control. Always.

Not sure which step applies to you? Speak to your Ideagen account manager. They'll confirm where you currently sit and what, if anything, needs to happen before you can get started.