Skip to content Meet Mira, the AI assistant built into your student information system
Account & sign-in

Single sign-on setup guide for IT administrators

What your IT team sets up in Google Workspace, Microsoft Entra ID, Okta, ClassLink, Clever or any SAML or OpenID Connect provider, then tests and rolls out.

Updated 5 min read

Managira works with any identity provider that supports SAML 2.0 or OpenID Connect. Your provider proves who the person is; their account, role and permissions stay in Managira. Managira never sees their provider password, and no software is installed on your side.

Who can do this: Your school's or district's IT administrator, working with a Managira manager.

Who does what

StepWhoWhere
Choose the provider and protocol, and copy the addressesA Managira managerSettings › Tenant configuration › Single sign-on › Copy all for our IT team
Add Managira as an applicationIT administratorYour provider's admin console (steps below)
Paste the provider's details, test, turn onThe Managira managerThe same Settings page
Move people to the providerThe Managira managerUse your provider for everyone, or one person at a time on Edit user

Good to know: Every person must already have a Managira account with the same email address the provider sends. Single sign-on doesn't create accounts.

SAML 2.0: what to configure

  • ACS URL (Reply URL) and Entity ID (Audience): copy them from Managira's settings page; each school has its own.
  • NameID: the person's email address (format emailAddress), or send the email in an attribute named email. If your provider uses another attribute name, the manager enters it under Advanced.
  • Signing: sign the assertion or the whole response (SHA-256 recommended). Unsigned answers are refused.
  • Back to Managira: give the manager your provider's metadata address (the simplest: it fills in everything), or the metadata XML, or the Entity ID, sign-in (SSO) URL and signing certificate.
  • Start URL (optional): add it as the app's link in your users' app launcher.

OpenID Connect: what to configure

  • Create a web application that uses the authorization code flow (Managira adds PKCE).
  • Redirect URI: copy it from Managira's settings page.
  • Scopes: openid email profile. The ID token must carry the person's email; an email your provider marks as unverified is refused.
  • Back to Managira: the issuer address, the client ID and the client secret. The secret is stored encrypted and is never shown again.
  • Microsoft Entra ID only: when the email claim is missing, Managira uses the user principal name, which your organization assigns.

Provider by provider

ProviderSAML 2.0OpenID Connect
Google WorkspaceAdmin console › Apps › Web and mobile apps › Add app › Add custom SAML app. Download the IdP metadata and give it to the manager to paste. Map Primary email to the NameID.Google Cloud › APIs & Services › Credentials › Create OAuth client ID (Web application). Issuer: https://accounts.google.com
Microsoft Entra IDEntra admin center › Enterprise applications › New application › Create your own › Single sign-on › SAML. Copy the App Federation Metadata Url.App registrations › New registration (Web). Issuer: https://login.microsoftonline.com/<tenant-id>/v2.0
OktaApplications › Create App Integration › SAML 2.0. Name ID format EmailAddress, application username Email. Copy the Metadata URL.Applications › Create App Integration › OIDC › Web Application. Issuer: your Okta address
ClassLinkManagement Console › Single Sign-On › SAML Console › Add. Copy the metadata address.Ask ClassLink support for an OpenID Connect app with Managira's redirect URI.
CleverYour SAML connector settings. Clever gives the metadata address.Not used.
Others (OneLogin, JumpCloud, PingOne, Auth0, AD FS, Shibboleth)Add a custom SAML application with the values above. AD FS metadata is at https://<server>/FederationMetadata/2007-06/FederationMetadata.xml; Shibboleth must release the mail attribute.Add a web application with the values above.

Test, then roll out

  1. The manager saves your details and selects Test the connection, then signs in on the new tab with a test account that exists in Managira. Nothing changes for anyone until the test passes.

  2. The manager selects Turn on and confirms with their password. Turning it on moves nobody.

  3. Move two or three people first (Edit user › How they sign in) and check they can sign in from the login page and from your app launcher.

  4. Then move everyone with Use your provider for everyone, and send staff the short note: enter your email on the Managira login page and choose Continue.

Good to know: Students sign in through the provider only if the manager ticks Students sign in this way too.

Security notes for your records

  • Your provider's own multi-factor authentication and password rules apply to every sign-in through it. Managira doesn't ask for its own code on top.
  • Each answer from your provider is checked for signature, audience, time and replay, and can only sign in an account of your school. It can never sign in a Managira platform administrator.
  • The school's main manager always keeps a Managira password, so someone can still get in if your provider is down. Keep that account's password and its own two-step sign-in in a safe place.
  • Changing the certificate, the metadata or the protocol turns single sign-on off until a new test passes. Plan certificate rollovers: paste the new certificate, test, turn on.
  • A session that came through your provider ends when the browser closes, and after the school's session time. Someone on hold or removed in Managira can't sign in through the provider.
  • Recent activity on the settings page shows the latest sign-ins and refusals, with the reason, to help with troubleshooting.

Troubleshooting

What you seeWhat to check
The test says no email was sentSend the email as the NameID (SAML) or include the email scope and claim (OpenID Connect), or set the attribute name under Advanced.
The test says no account matchesThe email your provider sends must match the person's email in Managira exactly (case doesn't matter).
Signature or certificate refusedSign the assertion or the response, and paste the current signing certificate (or read the metadata again).
Audience or ACS refusedThe Entity ID and ACS URL in your provider must be exactly the ones Managira shows for this school.
It worked, then stoppedSomeone changed the provider's details: test again and turn it back on.

Frequently asked questions

Does Managira support SCIM or automatic account creation?

No. Add people in Managira (Users / Employees, or Admissions for students), or move your records in with a data migration. Single sign-on only checks who they are.

Can we use two providers?

One connection per school. Pick the provider most of your people use; anyone else keeps a Managira password.

Where are the provider details stored?

With the school's other settings in the United States. OpenID Connect client secrets are encrypted (AES-256-GCM).

Was this guide helpful?