The second tab in the task editor, named ACCESS, determines When and How users can access the task.
- Task URL address: each task has its own unique access address. Users reach The Task’s Welcome Page through this address.
- If you visit the task URL address with your current browser, the system will cause you to log out of the account you are currently using and begin to see you as a user. In this case you need to re-log in to access the Task Editor. Therefore, to avoid logging out of your current account, it is recommended that you visit the task URL address with another browser.
- By visiting the task URL address with another browser, you can observe the changes you have made to your task.
- Active: If it is checked, your mission is accessible.
- If you enter a date/time in the “When will be active” section, the task can be accessed after the relevant date.
- If you enter a date/time in the “When is it going to be active” section, the task can be accessed before the relevant date.
- 1st Note: set date / time entry according to example: Year-Month-Day Time: Minutes (example: 2020-03-20 14:00)
- 2nd Note: If your task is Inactive (Passive), you are not allowed access to the task regardless of the dates set.
- If you set a Fee, users can access the Task only if they pay the fee you set.
The Authentication Method determines how users will access the task.
No Authentication Required
Users can access the task directly, without any authentication process. Information can be collected from the users participating in the task by using the Data Collection Form.
Accessing with an Invitation Code
An Invitation Code is created for each user that you want to be able to access the task, and users can access the task using that invitation code. Each invitation code is unique and different from the others.
When you create a new Ticket, the Invitation Code is automatically generated by the system.
Access Method Asking 1 Credential
Users access the task by filling out the Information from one (1) Credential. The information of the Credential that will be considered valid is specified when creating a new Ticket.
The Name of the Credential will be determined by you. For example, if you specify Student Number as the Credential name, the system prompts users to enter a Student Number. If the entered Student Number is defined as the 1st Credential among the Tickets you have created, the user can access the task.
Consider the following examples for Credentials:
- Candidate Tracking Number
- ID Number
- Passport No.
- PIN code
- User Number
Access Method Asking 2 Credential (Dual Identification Method)
Users access the task by filling out 2 recognition credentials. You can specify which two Credentials will be accepted as valid when creating a new Ticket.
The Name of the Credential will be determined by you. For example, if you define the E-mail for the 1st Credential Name and Password for the 2nd Credential Name; the system requests users to enter their Username and Password to access the task. If the E-mail and Password provided by the user are saved under the Tickets you have created, the user can access the task.
Consider the following examples for Dual Credentials:
- E-mail Address and Password
- The User Number and Password
- ID No and Password
- Candidate No and Pin Code