With single sign-on, people in your workspace sign in with an account they already have: Google, Entree Federatie, or your own identity provider, such as Microsoft Entra ID or Okta. An admin sets it up under Account settings → Sign-in & domains. You can offer it next to passwords and emailed codes, or require everyone, students included, to use it.
Single sign-on is available on the Organization plan. Only admins and owners can set it up.
Choose a sign-in method
Go to Account settings and, under Advanced, open Sign-in & domains. Under Single sign-on you pick one of four methods:
| Method | Best for | What you'll need |
|---|---|---|
| Email and password | The default, without single sign-on | Nothing |
| Sign in with Google | Schools on Google Workspace | Your email domain (optional) |
| Sign in with Entree Federatie | Dutch schools that already use Entree | Your BRIN number |
| Custom identity provider | Microsoft Entra ID, Okta or any OpenID Connect provider | An issuer URL, client ID and client secret |
Fill in what the method needs, click Save sign-in method and confirm.
Offer it, or require it
Once you pick a method other than Email and password, you also choose whether to switch on Require everyone to sign in this way.
- Off (the default): single sign-on works next to passwords and emailed codes. People who open your workspace's sign-in page see a Single sign-on button below the usual form.
- On: everyone in the workspace has to sign in through the identity provider. Opening your workspace's sign-in page takes them straight there.
When you require single sign-on, passwords, magic codes and magic links stop working for everyone in the workspace, students included. Students who signed in with a code are signed out within the hour. Make sure everyone can reach the identity provider before you switch it on.
Emails with an invitation or results still arrive. Their link takes people to the sign-in page, which sends them on to the identity provider.
Sign in with Google
Choose Sign in with Google and, if you like, enter your school's Email domain, for example myschool.edu.
With a domain, only Google accounts on that domain can sign in, and someone new who signs in is added to your workspace automatically. Without one, any Google account can sign in, but people who aren't members yet aren't added to your workspace: they end up in a personal workspace of their own.
Google doesn't tell Examplary who is a student, so someone new joins as a teacher. Import your students first, so they already have a student account when they sign in with Google.
Sign in with Entree Federatie
Choose Sign in with Entree Federatie and enter your school's BRIN number, for example 01AB.
You also need to switch Examplary on for your school in the Entree dashboard. Integrating with Entree Federatie walks you through it, including the roles and groups Entree sends along.
Use your own identity provider
Any identity provider that supports OpenID Connect works, including Microsoft Entra ID, Okta, Google Cloud Identity and Keycloak.
1. Create an application in your identity provider
In your provider's admin console, create an OpenID Connect (or "web") application. Set its redirect URI to the address shown on the Examplary setup screen:
https://auth.examplary.ai/oauth2/callbackMake sure the application can use the openid, profile and email scopes.
2. Enter the details in Examplary
Choose Custom identity provider and copy three values from your provider:
- Issuer URL: the base address of your provider, for example
https://login.microsoftonline.com/<tenant-id>/v2.0. It has to be the issuer, not the sign-in page. - Client ID: the identifier of the application you just created.
- Client secret: the secret that came with it. Examplary never shows it again. To change other settings later, leave the field empty and the current secret stays.
Click Save sign-in method and confirm.
Open your workspace's sign-in page in a private browsing window and sign in once before you tell everyone. If the issuer URL or secret is wrong, your own session is still open to fix it.
3. Optional: send roles and groups
If your identity provider adds any of these claims to its token, Examplary uses them. None of them are required. Without them, everyone new joins as a teacher, without groups.
| Claim | What it does |
|---|---|
role | Sets the person's role in Examplary when their account is created. |
groups | Group names. Missing groups are created, and membership is updated every time they sign in. |
group_ids | IDs of existing Examplary groups, if you'd rather match on those. Wins over groups. |
The role claim accepts these values, in upper or lower case:
| Claim value | Examplary role |
|---|---|
admin, manager | Admin |
teacher, employee, staff | Teacher |
student, member, participant | Student |
Any other value is ignored, and the person joins as a teacher. Send groups and group_ids as a list, such as ["Class 3A", "Class 4B"], which is what most providers do. A single text value counts as one group, commas and all.
The role is only set when someone's Examplary account is created. If you change it in your directory later, an admin changes it in Examplary too, under Users & groups. Group membership, on the other hand, is updated every time someone signs in.
Existing accounts are linked
People who already used Examplary with a password keep their account. The first time they sign in through single sign-on, Examplary links it to their existing account with the same email address, so their tests come along:
- Google: when Google has verified the email address.
- Entree Federatie: when their school has set up Entree in its workspace.
- Your own identity provider: straight away when the address is on one of your verified email domains. Otherwise, Examplary emails the account a code first, which they enter in the same browser tab.
Send people to the sign-in page
Share your workspace's own address: your custom domain if you have one, or https://app.examplary.ai/org_12345, with your organization ID in place of org_12345. You'll find that ID in the address bar when you're signed in.
If you get locked out
A wrong issuer URL or an expired client secret can leave nobody able to sign in. While single sign-on is required, a workspace owner can get back in without our help, at:
https://app.examplary.ai/org_12345?recovery=1The address is also shown under If you get locked out on the setup screen once single sign-on is required, so note it down before you need it. On that page, the owner enters their email address and clicks Email me a code. The code skips the identity provider once, long enough to fix the settings or switch back to Email and password.
The code works for 15 minutes and signs you in for an hour. It only works for workspace owners, and every other admin and owner gets an email when one is requested, so nobody can quietly get around your sign-in settings.
If the owner has also lost access to their mailbox, email us at hi@examplary.ai and we'll help you back in.
Switch back
Choose Email and password under Single sign-on and click Save sign-in method. Everyone goes back to signing in with a password, and students to codes and links by email.
Accounts stay as they are, with everything in them. Someone who has only ever signed in through your own identity provider doesn't have a password yet: they set one with Forgot password? on the sign-in page.
Troubleshooting
Students still get a code by email. Single sign-on is offered, not required. Switch on Require everyone to sign in this way if everyone has to use it.
I get "This domain is already in use by another workspace". A Google email domain or BRIN number can belong to only one workspace. Contact us at hi@examplary.ai if that doesn't seem right.
Someone sees "We couldn't sign you in". The message below it says why, for example that the sign-in was cancelled at the identity provider or that their account there has no email address.
I don't see the recovery address. It's only shown, and only works, while single sign-on is required.