Before teachers and students start using Examplary, you set a few things up once as an admin: how people sign in, who's in the workspace, which rules apply and which integrations you use. It all lives under Account settings, in the Workspace and Advanced sections. This checklist puts the steps in a sensible order.
To open Account settings, click your name in the bottom left. Only admins and owners see the Workspace and Advanced sections.
Many of these steps are part of the Organization plan, such as single sign-on, verified email domains, branding and the security settings. Question types and taxonomies can be managed on every plan, and adding users is available from the Teacher plan up. See the pricing page for what each plan includes.
1. Set up your workspace
- Name your workspace under Workspace → General → Workspace name.
- Under Branding, add your school's logo and pick a Menu color and Accent color. The logo also appears on printed tests.
- Under Printing, choose the Default print font and Default print font size. Teachers can still change them for each test.
- Want Examplary on your own address, like tests.yourschool.edu? See Setting up a custom domain.
2. Decide how people sign in
- Under Advanced → Sign-in & domains → Single sign-on, choose how people sign in: with Google, with Entree Federatie, or with a Custom identity provider such as Microsoft Entra ID. See Setting up single sign-on and Integrating with Entree Federatie.
- Add your school's email domain, so colleagues who sign up with their school address land in your workspace automatically. See Verifying your email domain.
- If you want, require two-factor authentication. See Requiring two-factor authentication.
3. Add users and groups
Go to Workspace → Users & groups. Import adds everyone at once from a CSV file, groups included, and Invite new member adds people one by one. Importing users & groups walks you through the file, and Roles & permissions explains which role to give whom.
Teachers who already used Examplary with their own account have their tests in a separate workspace. Those aren't moved over automatically. Email hi@examplary.ai if you'd like them merged into your school's workspace.
4. Agree on the ground rules
Under Advanced → Security & compliance → Access settings, you decide what teachers can do:
| Setting | Default | What it does |
|---|---|---|
| Allow public link sharing | On | Teachers can share a test with Anyone with the link. |
| Allow teachers to invite new users | On | Teachers can invite new students and colleagues by email address. |
| Require two-factor authentication | Off | Anyone who signs in with a password also needs an authenticator app. Single sign-on and sign-in codes aren't affected. |
| Restrict user visibility to same groups | Off | People only see others from their own groups. |
On the same page, you choose the AI processing region (see Data residency and backups) and the Data retention period: how long deleted items are kept, 12 months by default. What you can bring back in that time is covered in Restoring deleted tests and practice spaces.
5. Choose integrations and question types
- Under Workspace → Integrations, enable the integrations your school uses, such as Schoolyear, Muute or Woots and Ans. If your school has a learning platform, read Connecting your learning platform to Examplary.
- Under Question types, decide which question types teachers can use. See Managing question types in Examplary.
- If your school works with its own taxonomy, create it under Taxonomies. See Using taxonomies in Examplary.
6. Get your network ready
If your school uses a firewall or web filter, ask your IT team to allow Examplary. Allowlisting Examplary on your network lists the addresses.
7. Help your teachers get started
Send your teachers the Getting started guides: Creating your first test in Examplary, Grading your first test in Examplary and Setting up your first practice space. Teachers you invite get an email with a link to choose a password, or sign straight in through single sign-on.
If you ever need to check who did what, you'll find it under Audit logs. See Audit logs.