If you are an administrator, you can define a Quest (or more) based on your compliance needs, company goals...etc by building quests for developers to complete.
Quests
To set up a quest you can select one or multiple vulnerabilities that you want learners to focus on. These could be goals to meet your compliance requirements or just the vulnerabilities that matter the most to your organization.
Note: To achieve the learning outcome, a learner must complete all the content associated with the chosen vulnerability or concept.
How to Add a Quest
Step 1
Navigate to the Quests dashboard by selecting the "Administration" dropdown and selecting "Quests"
Step 2
Click the "Create new" button
Step 3
Start by giving the quest a name, then configure it as desired.
- Quest Name: The name of the quest end learners will see.
- Mandatory Quest: Make the quest mandatory to prioritize it over optional quests.
- Badge: Upload a badge that learners will earn once they complete the quest.
- Objectives: The vulnerabilities that you want learners to focus on. You can create a quest based on specific vulnerabilities and/or Most Common Vulnerabilities
- Start Date: Determines when the quest becomes visible to learners
- End Date: Determine the quest's deadline, after which it will disappear for learners
Step 4
You have the option to assign the quest to specific teams. If you don't select a team, the quest will be assigned to the entire company including future users.
Step 5
Now the quest is ready to be published. Click the "Save & Publish" button to publish the quest or
"Save as draft" if you aren't ready to publish it yet.
Step 6
When you click the "Save & Publish" button, you will receive a pop-up to confirm that you want to publish the quest. Click "Publish" or "Schedule" to proceed
No Start date: learners will see the quest immediately
Start Date in the future:
Do users get notified when a new Quest is created?
Yes, but only if the "Send Quest based emails" setting in the "Communications" page is enabled.
Please keep the following in mind:
-
Users who have selected languages that are irrelevant to the quest - will not receive any emails.
Example: The user selected backend languages/frameworks and the vulnerabilities included in the quest are relevant to frontend languages/frameworks)
-
Users who have selected languages relevant to the quest - will receive an email titled "You have been assigned a new quest".
Example: The user selected backend languages/frameworks and the vulnerabilities included in the quest are relevant to backend languages/frameworks)
-
Users who have not yet selected a language(s) - will receive an email titled "Select your development languages on Secure Code Warrior"
Note: The reason this group of users doesn't get the "you have been assigned a quest" email is that it's not possible to determine whether the quest applies to them before they select their preferred language(s)
Can You Edit Quests?
The ability to edit any Quest depends on its status
Quest Status | Can Edit? | Can Archive? | Can Delete? |
Active |
❌ |
✅ | ❌ |
Scheduled |
❌ |
❌ | ✅ |
Finished |
❌ |
✅ | ❌ |
Archived |
❌ |
- | ❌ |
Draft |
✅ |
❌ | ✅ |
Related Links:
Comments
0 comments
Please sign in to leave a comment.