Skip to main content

🔐 SSO: Connecting Myagi to Your Internal Training Platform

Make accessing Myagi simpler, faster, and more secure by integrating it with your company’s existing authentication system through Single Sign-On (SSO).

Myagi Support avatar
Written by Myagi Support
Updated this week

If your organization uses an identity provider (IdP) like Okta, Azure AD, or any SAML 2.0-compliant system, you can enable Single Sign-On (SSO) for seamless access to Myagi. This integration is available free of charge.


🧠 What is SSO?

Single Sign-On (SSO) is an authentication method that lets users access multiple platforms with a single set of login credentials. By connecting Myagi to your company’s identity provider (IdP), your team can log in seamlessly without needing a separate Myagi username or password.

With SSO enabled, users can access supplier training on Myagi directly from internal systems such as:

  • 📚 Learning Management Systems (LMS)

  • 🧑‍💼 Human Resource Information Systems (HRIS)

  • 🏢 Custom intranet portals or internal dashboards



🌟 Key Benefits of Enabling SSO

Enabling SSO isn’t just about convenience — it’s about efficiency, security, and better user experience:

  • 🔑 1-Click Login: Access Myagi directly from your internal systems without additional logins.

  • 👥 Automated User Management: New hires get instant access, and departing employees are automatically deactivated.

  • 📊 Better Reporting: Track training engagement more easily across your workforce.

  • 🔒 Enhanced Security: Centralized access control ensures only authorized users can access your company’s training environment.



🧰 What You’ll Need from Your IT Team

To connect your identity provider (IdP) (e.g., Okta, Azure AD, or any SAML 2.0-compliant system) with Myagi, we’ll need a few key details:

🔐 Required SAML Metadata

  1. Single Sign-On Service URL: The IdP endpoint where Myagi sends authentication requests.

  2. Single Logout Service URL (optional): Where logout requests are sent if your IdP supports single logout.

  3. IdP x509 Certificate: The PEM-encoded public certificate used to verify authentication requests.

  4. Username Field: The unique identifier for each user (e.g.,

    bashCopyEdithttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
  5. Email Field: The email address field.

  6. First Name Field and Last Name Field: For user identification and profile setup.

📁 Optional Fields for Enhanced Integration

  • Team ID Field: Maps users to a specific team in Myagi.

  • Group ID Field: Maps users to one or more groups (supports multiple values).

  • Permission Group Field: Defines user roles — team_managers, company_admins, or leave empty for standard users.



📤 What We’ll Provide

Once you share your SAML metadata, our team will send you Myagi-specific configuration values based on your company’s subdomain:

  • Audience

  • Recipient

  • ACS URL (Assertion Consumer Service)

  • Logout URL
    Provide a Test User

To complete the setup and run end-to-end tests, we’ll also ask you to provide a test user account (email and password) that we can use to validate the integration from your side. This ensures everything works correctly before enabling SSO.



🐞 Testing the Integration

Before SSO goes live, we’ll need a test user account (email and password) to verify the setup from your side. This ensures that authentication, access, and provisioning all work smoothly before we enable SSO for your whole organization.


🚀 How to Get Started

Ready to connect Myagi with your internal systems? Enabling SSO is simple — just reach out to our support team, and we’ll guide you every step of the way:

📩 Email: myagisupport@rallyware.com
💬 Chat: Contact us directly through the in-app support chatbot.

Our team will assist you in configuring SSO, testing the connection, and rolling it out across your organization.

Did this answer your question?