1st of September 2026 – Changes to access codes for digital tests

As of 1 September 2026, changes will be introduced to how access codes are used for digital tests. Access codes on timeslot level will become available with the 21 June 2026 release. From that date onwards, both assignment-level and timeslot-level access codes can be used. From 1 September 2026, access codes configured at assignment level will no longer be supported, and new digital test timeslots created through the interface will automatically include an access code by default.

These changes improve the security and consistency of digital test access management by standardising access codes at timeslot level.

What does this mean?
From 1 September 2026 onwards:

• All newly created digital test timeslots in the interface will automatically receive an access code.
• Users creating timeslots through the interface will no longer need to manually enable or configure an access code.
• Access codes configured at assignment level will no longer be supported.
• The password attribute in the assignment API endpoint, which manages assignment-level access codes, will no longer be supported. To configure access codes through the API, integrations must use the access_code attribute on the timeslot endpoint.
• API integrations can still create timeslots without an access code.
• Existing timeslots and assignments created before 1 September 2026 will not automatically be changed.

From 21 June 2026 until 1 September 2026:

• Both assignment-level access codes and timeslot-level access codes will continue to work.
• If both are enabled, participants must enter both the assignment access code and the timeslot access code before they can start the test.

Timeslot access code behaviour (available from 21 June 2026 onwards):

• If a timeslot access code is disabled, participants can start the assignment without entering a code.
• If a timeslot access code is enabled after participants have already started the test, they can continue without entering the code. The same behaviour applies for refreshing the access code.
• New participants accessing the assignment, or participants continuing on a different device or in a different browser session, will be required to enter the access code if one is enabled.

Why are we making this change?
Access codes on timeslot level will be supported from the 21 June 2026 release onwards, making it possible to manage access protection in a more secure and flexible way. By standardising access codes at timeslot level and enabling them automatically for interface-created timeslots, the risk of unsecured digital test sessions is reduced while simplifying the configuration process for educators and administrators.