How Can We Help?

Access Control with Tickets

If you have selected one of the following as the Authentication Method (Access) of the task, users need a Valid Ticket to log in to the task:

  • By Invitation Code
  • By Asking 1 Credential
  • By Asking 2 Credentials

We’ve already explained how each Authentication Method works on the Access Settings page.

  • Using One Ticket, only one user can be logged into a task.
  • When the user logs into the task with a ticket, a room is created for him or her. The information in the ticket (with the defined exceptions) is transferred to this room. The ticket becomes used and can no longer be updated. (Only Room settings can be updated after this point.)
  • If the user wishes to log in again using the same ticket, the system directs the user to the room previously created for the same ticket.

Compatibility Between Ticket And Authentication Method

The tickets that you create with your chosen authentication method must be compatible with each other. For example, if you have selected the Asking 1 Credential as the Authentication Method and set the PIN Code as Credential 1 Name, the PIN Code section must be filled in for the Tickets.

Example 1: if you want users to be able to log in to the task with the PIN code:

  • You must select the Authentication Method ‘Asking 1 Credential’, in the Task Access Settings,
  • Credential 1 Name must be PIN code,
  • and the PIN code value must be defined in the User Information section of the ticket.
ACCESS : By Asking 1 Credentials
TICKETS : New Ticket

Example 2: if you want users to be able to log in to the task with their E-mail address and Password,

  • The authentication method that you specify in the Task’s Access Settings must be with a Dual Identification Information,
  • Identification Information 1 must specify the name as an E-mail address and Identification Information 2 must specify the name as a password,
  • and in the User Information section of the Ticket, the E-Mail Address and Password values to which the user will log in must be defined.

In the TICKETS tab of the task Editor, you can create new tickets or create bulk tickets; you can list your existing tickets.

Listing the Tickets

You can narrow down the tickets to be listed by selecting the following options:

  • By setting the date range (1)
  • By typing one of the following (2):
    • Display Name
    • E-mail Address
    • Credential 1 (if you have selected one credential information as authentication method)
    • Invitation Code
    • Group Name
  • Clicking on the NEXT button lists the tickets that are appropriate to your selections. You can set the number of tickets to be listed from the Batch Size. If the Next button is still active after the system has listed the tickets according the number of tickets you have determined as Batch Size, it means that there are more tickets to load according to your preferences. You can also list the remaining tickets by clicking the NEXT button again.
  • With these 2 filtering features, we can determine which tickets will be listed. Additionally, you can use the Batch Filter to search among the tickets listed according to your preferences. For example, by typing a user’s e-mail, invitation, code, credential 1, display name or group name etc. into the Batch Filter, you can search for a specific user or users among the listed tickets.

Creating A New Ticket

Click on the  icon to create a new ticket. The Ticket Editor opens.

The Ticket can include the following information:

  • Credential Information of the User
  • Group
  • Ticket-specific Availability Settings and Access Dates
  • Extra tags to associate the user or ticket with a set of data
  • Exceptions to be applied to the person who will have access to the task with this ticket

Now let’s examine these sections one by one.

User Information

This section of the ticket changes according to the Authentication (Access) Method you have selected .

If You Have Set The Authentication Method As A Personal Invitation

Specify the person’s Full Name and E-mail address (not required)

If You Have Set The Authentication Method ‘By Asking 1 Credential’

Specify the person’s Display Name and E-mail address (not required), as well as the Identification Information value that you set when selecting the Authentication Method. For example, if the name of the credential is the Student Number, type the Student Number of the relevant student on the ticket.

On the Access Settings page, we saw how access works with a Single Credential. When making this adjustment, you specified a name for the identification information that the system would require to identify the user. In the following example, because this name is set to “Student Number”, you are asked to specify the Student Number of the user in the User Information section of the ticket.

In the following example, since this Name is set to “Student Number”, you will be asked to specify the user’s Student Number in the User Information section of the Ticket.

People who enter the Credential Name Value (example: Student Number) that you have determined when defining the ticket in a complete and accurate way, can gain access to the task with this ticket.

If You Have Set The Authentication Method As Dual Identification Information

Specify the person’s Display Name and E-mail address (not required), as well as the credential values that you set when selecting the Authentication Method. For example, if the 1st Credential Name is Candidate Number, the 2nd Credential Name is Password, type the Candidate Number and Password of the respective person in the ticket.

On the Access Settings page, we saw how access works with Dual Credentials When making this adjustment, you had set a name for each credential that the system will request to identify the user.

In the following example, Credential 1 Name is Candidate Number, and Credential 2 Name is Password. In this case, the system will ask you to specify the Candidate Number and Password, in the User Information section of the Ticket.

Users who accurately and precisely enter the double recognition credentials (for example, Candidate Number and Password) that you have specified for the Ticket, can access the task.


You can set a group for the ticket. The group name you write is transferred to the Room created by the system upon entry of the user with a ticket and all exams to be taken by the relevant user. In this way, TicketsRooms and Exam Results can be grouped with a group name.

If more than 250 exams are to be performed on a task, grouping tickets will make the job easier. Creating a group will allow you to quickly and easily find Tickets, Rooms and Results for the group that interests you.

Availability (Access)

You can determine whether the ticket is valid (active / passive) and its availability dates:

  • If the ticket is Active, it can be used.
  • You can specify the dates on which the ticket will be valid:
    • Start Date: Determines from which date the ticket will be available or active.
    • End Date: Determines until which date the ticket will be available or active.
  • Overwrites Task’s Access Dates
    • If selected, the Access Dates you set in the Task will be invalid for this ticket and the validity dates you have set for the ticket will be used. (This way, you set an exceptional access date for this ticket.)
    • If not selected, the system gives first priority to the Access Dates established for the Task, and then checks the validity dates established for the Ticket..


You can associate the ticket with a number of tags. The tags you associate are also transferred to the Room and Exam Results. This way you can group The Ticketroom and Exam Results as you wish.

Determining Exceptions For Tickets

The choices we made in the Task Settings and Exam Settings apply to all participants. However, if you want one (or many) user to be subject to a set of settings other than the settings you have already made, you can define an Exception for that user on the ticket.

Let’s give a few examples:

  • All participants will take the exam in Step 1 in Full Screen, while the person with this ticket will take it without Full Screen.
  • All participants can take the exam in step 1 once, while the person with this ticket can take it twice.
  • While all participants take the exam in step 2, Video Recording will be done as a surveillance method, Photo Shooting will be applied as a surveillance method for the person with this ticket.

To specify a ticket-specific Exception, first select a Step, then select the exception to add.

As an example, we set up an Exception below for the owner of the ticket: “Let the English Level Test be carried out as a Full Screen for the owner of this ticket”.

Table of Contents