October 2026 release is live Read More
Breadcrumbs

Step-3: Configure SSO in Mavvrik

Below is the description of the steps to Configure SSO in Mavvrik

  1. Login to Mavvrik as owner.

  2. Click on Menu > Admin > SSO

  3. Click on Configure SSO button

  4. Enter Entity Id, SSO URL and Certificate copied in Step-2

  5. Click Save

  6. SSO is Configured Successfully, You can Edit or Delete the existing data if required.

  7. Click on Login with SSO

  8. Pop up/new page appears which navigates to Gmail Sign-in page to let you sign in using your  Gmail account(business)

  9. Enter your Gmail credentials and click login

Note:

  • Users who are added to Mavvrik are able to log in successfully with their Gmail accounts and access the Application based on their privileges.

Edit SSO Configuration

Enable Enforce SSO

Enable Enforce SSO
Enable Enforce SSO

Once enforced, users will be required to authenticate exclusively through SSO, and no other login methods will be allowed.

Enable User Provisioning

Enable user provisioning
Enable user provisioning

When User Provisioning is enabled, new users logging in via SSO will be automatically created in the Mavvrik platform during their first successful login attempt.

Previously, users had to be explicitly created in both the Identity Provider (IdP) and the Mavvrik platform before they could log in using SSO. This enhancement removes that requirement and reduces onboarding friction.

Password-based login is available only when Enforce SSO is disabled. In that case, users can set their password using the “Forgot Password” option after their account has been automatically created.

When this option is disabled, new users signing in through SSO will not be automatically provisioned in Mavvrik.

Troubleshooting

SSO login through Google Workspace fails

  1. Start with Login with SSO on the Mavvrik login page rather than an IdP-initiated launch.

  2. Compare the Entity ID, SSO URL, and certificate saved in Mavvrik with those from the intended Google Workspace SAML application.

  3. In the Google Workspace application, compare the service-provider Entity ID and ACS URL with the values copied from Mavvrik, and verify the EMAIL Name ID format documented in Step 2.

  4. Check that the SAML application's service status permits access for the intended user; a newly created app is described as off for everyone by default. Ask the Workspace administrator to review access within the organization's intended scope.