Users

Updated 2026/09/08

Two classes of user share access to your organization. Teammates manage the admin side — questions, tests, tasks, and settings. Learners are candidates with a persistent account in your organization, used to take assessments.

Teammates

Teammates are staff members with one of several roles that determine what they can see and do. See Roles & Permissions below for the full breakdown.

Learners

Learners are candidates with a persistent account tied to your organization. A Learner account keeps someone's history connected to a single identity — useful when the same person takes multiple assessments over time and you want their scores centralized under one record.

A Learner account is not required to take an exam. Unless you specifically need a persistent, centralized account for someone, you can simply invite people to a Task directly — they take the assessment without ever being registered as a Learner in your organization.

In this section

Roles & Permissions Every user is a learner or a teammate. Teammates have one of seven access levels: Super Admin, Manager, Test Author, Task Operator, Custom Access User, Question Curator, or External Question Author.

Teammates sign in with the email and password set up for their account, from the main TestInvite sign-in page — separate from the candidate-facing portal that Learners use to access their assessments.

If your organization has SSO configured, teammates sign in through your identity provider instead. See Single Sign-On (SSO) for how it's set up.

Forgot a password? Use the reset password link on the sign-in page to set a new one.

How to add users to your organization one at a time or via bulk CSV/JSON import, and how to organize them using folders, groups, labels, and favorites.

Repository settings control policies that apply to all users in your organization's user repository. These settings are managed by the organization owner (Admin role only).

Unique Emails

When unique email enforcement is active, no two users in the repository can share the same email address. This is a prerequisite for enabling SSO.

To activate: the system checks for duplicate emails first. If duplicates exist, they are shown and activation is blocked until resolved.
To deactivate: unique emails cannot be turned off while SSO is enabled.

Unique email enforcement is required before you can configure Single Sign-On (SSO).

Single Sign-On uses SAML 2.0 — configure domain rules, an enforcement mode, and your IdP settings, and users are provisioned automatically on their first login.