How to set up SSO with your identity provider

Goal

Connect BoodleBox to your identity management provider (IMP) through Edlink so your team members sign in with their existing institutional accounts — no separate BoodleBox password needed.

SSO controls how people sign in, and can support who has access once provisioning is established. Rostering and user provisioning are configured after the integration described here.

Before you start

Confirm your IMP is supported: Microsoft Entra, Google Workspace, or OneLogin. Edlink's platform-specific docs (linked) are the reference for provider-side configuration.
Know the timeline. Edlink approval can take up to 48 hours, plus up to 24 hours of propagation after approval. Plan for SSO to take 2–3 weeks end to end, including rostering.

Steps

Open the BoodleBox Edlink integration link — https://ed.link/integrate/231f9d64-bdb9-4cc1-babc-1787d618e2aa — and sign in or create your administrator account using your school email.
Select your identity provider from the supported platforms list and follow the on-screen instructions. Edlink shows platform-specific steps for your provider.
Authorize the connection between your identity provider and BoodleBox, then submit for approval.
- Microsoft Entra note: the consent screen lists more permissions than SSO needs. Only offline_access, openid, email, and profile are required. Your IT team can revoke the other permissions after setup from your Entra dashboard without breaking the integration.
Scoping access by directory group? If you're automating provisioning with Entra, send each group's UUID to your Customer Success representative so it can be added to the configuration.
Wait for approval and processing. Once approved, allow up to 24 hours for your organization's information to appear in both Edlink and BoodleBox. Users may not be able to log in immediately — this is expected, not a failure.
Test sign-in. Click "Sign In with Your EDU Account" and complete your institution's login (see How to sign in with SSO).

Common issues

400 error at sign-in → the user isn't provisioned. See Troubleshooting SSO and sign-in errors.
"Account not found" in the first 24 hours → propagation is still in progress; try again the next day.
IT concerned about requested permissions → only the four scopes above are required; the rest can be revoked post-setup.
A new department or group can't sign in → the directory group hasn't been shared yet; send its UUID to your Customer Success representative.

Good to know

SSO is only available for users associated with a paid team at the institution.
If a user already has a BoodleBox account, SSO automatically associates with it as long as the BoodleBox email matches the IMP email. A mismatch creates a duplicate account.
A welcome email is automatically triggered when a user is granted access — plan your internal communications so users aren't surprised.

Still stuck?

BoodleBox integration questions → email success@boodle.ai, typical response within 8 business hours.
Errors in the Edlink wizard or dashboard → support@ed.link