Implementation resources: Inspera Assessment without integrations

This article is a supplement to the Implementation Guide and provides information about how you can use Inspera without integrations such as Single-Sign On (for candidates), LTI integration etc.




Creating non-SSO candidates

As candidates only exist in the system in the context of test instances, you can choose between creating different types of candidates:

One-time users

One-time users are independent users, which means that one single one-time user is created per candidate per test. If a candidate has more than one one-time user, they cannot be combined. The candidate must log in with the username and password that belong to each one-time user.


Permanent users

Permanent users are users that can be added as candidates on more than one test. By using permanent users, candidates can use the same username and password to access all their tests. 

The list of permanent users will grow over time. If many of the same candidates are to take the same test, we recommend creating a test template with these candidates. This way you save time setting up each test as it is easier to remove and add single permanent users than adding larger groups of these users to each test. 

For more information about candidates types, see the article Candidate types in Help Center.


Creating admin users

Without integration, you can create admin users in User Administration in the following ways:

  • Manually one by one
  • CSV upload
  • Through Inspera API

If you do not set a password when creating an admin user, an email will be sent automatically to the registered email address, informing the person that an Inspera Assessment user account has been created, with a prompt to set a password. In this way, the user is both made aware that an account is created, and of their login credentials, without you having to inform of this manually.

Note: All admin users are created as permanent users in the system.


Allocation of contributors to tests

Instead of assigning a contributor to the test instance manually one-by-one, you can allocate contributors via CSV upload.

For more information about the contributors types, see the article Adding contributors to test in Help Center.


Test templates

Before you create each test instance manually, consider creating one or more test templates. All information, settings, and even users allocated to a test instance (candidates and contributors), can be saved as part of a template. If there are commonalities in the test instances you are to set up, create a template with these settings. For example, should all assessments require the use of Safe Exam Browser? Will they have a standard marking workflow? Is there a user who should have access to all tests? Should all home assessments allow candidates to review their submissions?

Create one test template for on-site assessments and a separate for home assessments, and the test instances can easily be created form the desired template later, inheriting the selected settings.

For more information about templates, see the article Test templates in Help Center.


Archiving candidates' results

If the candidates should be registered and archived in an external system, the results (marks and grades) can be exported from Inspera Assessment in the following ways:

  • The grading protocol that becomes available when grading is completed and confirmed contains a list of all candidates and their grades
  • CSV files
  • JSON files
  • Inspera APIs

Please note you can opt to give the candidates access to their results in Inspera Assessment. You can enable it in the test setup, and the results will become available on the candidate dashboard / candidate report when grading is completed.

Articles in this section

Was this article helpful?
1 out of 1 found this helpful