Preparing for Ideagen Hub integration
Who is this article for?
Administrators planning to implement Ideagen Hub.
Administrator or IT Administrator access is required for some steps.
Ideagen Hub is a unified interface that consolidates all Ideagen solutions in one place. Users can access tools, actions, notifications, and support with a single sign in. It offers centralised permissions, quick workflow access, and AI features via Mazlan, serving as the launch point for Luminate and connected services.
This article guides Administrators and system owners on preparing their Ideagen Quality Management Professional system for the transition, covering key decisions, configurations, and checks to ensure a smooth move to Ideagen Hub without disruption.
1. Reviewing email and username formats
For all users moving to Ideagen Hub, valid email addresses are mandatory, as they are required for both native and SSO authentication.
Usernames must be cleanly formatted to ensure successful migration and system matching. This means the Ideagen Quality Management Professional username cannot contain spaces, empty strings, whitespace characters (such as tabs, spaces, new lines or line breaks), or any control characters, including non‑printable ASCII symbols like NULL, backspace, escape sequences or direction marks.
Usernames must be between 1 and 128 characters in length and must be unique within the environment. Because Hub treats usernames as case‑insensitive, variations such as ziee and ZiEe are considered identical. Ensuring all user records meet these requirements in advance will prevent authentication issues and support a smooth transition.
Need more information?
Visit our article on changing a username for more details.
1.1. Checklist
Use this checklist to ensure all user accounts meet the requirements for Ideagen Hub.
Email requirements
- Every user has a valid email address configured in the Primary Email Address field
- Email addresses are correctly formatted
- Email is available for both native and SSO authentication
- Where an individual email address is not available, a shared or team email address can be used.
Username requirements
Each username:
- contains no spaces
- contains no empty strings
- contains no whitespace characters (spaces, tabs, new lines, line breaks)
- contains no control characters (e.g., NULL, backspace, escape sequences, direction marks)
- is 1–128 characters in length
- unique within the environment
- uniqueness has been checked case‑insensitively (e.g., ziee = ZiEe)
Need to bulk edit users?
Visit our article on bulk editing users for more details.
2. Updating an external Identity Provider (IdP)
If your organisation signs in through an external identity provider (such as Okta, PingOne, Entra ID, or any other SAML/OIDC service), you will need to update one setting before your migration to Ideagen Hub is complete.
Your identity provider currently sends users back to your old Ideagen system once they’ve successfully signed in. After the move to Hub, that old return address (the redirect URL) will no longer work. Ideagen Hub uses a new redirect URL, and your IdP must be updated to point to it.
If the redirect URL isn’t updated, users will be sent to the old system and their sign in will fail.
As your organisation owns and manages your ldP, you must update the redirect/callback URL in your identity provider settings so your users return to the new Hub sign in page instead of the old one.
Important
You will receive the new Hub redirect URL in advance. Your IT team must add this to your IdP before migration begins.