Security Awareness Training

I would like to be able to mark training as completed. There are times where the user has completed the training but changes are made to the learners and they are sent the training again. This makes it show that the training has not been completed. It would be nice to be able to mark that user has having completed the training without them having to go through it again. Leonard Queen

Until now, I assumed since I saw 2 scenario's each month, that users were getting both of these scenario's delivered at random times throughout the month. Instead it appears there are two scenario's, and users get one of those randomly each month at random times. This seems like a waste of a good scenario and teaching moment. It would be great if there was an option to have both scenario's sent instead of just one.

I'd like the ability to either manually set the number of phishing templates used in the monthly managed phishing campaigns or perhaps just have it scaled up based on number of learners in the account. Currently, there are 2 templates chosen for each month. This is fine for small organizations but larger customers may find that these are too easy for the users to catch on to. For example, if there are 200 users, about half will get 1 template and the other half will get the 2nd template. It would be nice for an organization of this size to scale up to 4-5 different templates to keep the users on their toes.

Notify manager when one of their employees has clicked into the phishing email and how far they progressed, ie. compromised.

The ability to sort by account alphabetically, or users by tag, department, etc. would be fantastic to have.

Allow us to change the default authentication method for new organizations. For most our use cases, Magic Link is a better option vs Access Code, however changing this setting is something we have to manually do during client onboarding.

We've had customers reach out and ask "what happens" when a user in managed-phishing fails the campaign and gets compromised. It would be nice if the KB could outline in detail from the POV of the user failing and what the Campaign will do next for them. We've had to setup a test environment and fail the phishing-campaign and document manually to provide any guidance.

Similar to a phish email test, add the capability to call users and test their ability to detect the threat. Calls could perform social engineering, or ask the user to download a remote control tool, etc

When users fail a phishing simulation test they are asked to select the reasons why they clicked. Capture these responses for long term reporting, going beyond reporting on just the campaign in question. Use case: Do a "year in review" report to show organizations why their users are most frequently clicking on phishing emails. This can inform strategy around what type of SAT training will be most impactful to their users.

It would be nice to see a difficulty rating on each scenario. This would help organizations choose the level of adversary sophistication in their simulated phishing messages. For example, an email with a lot of spelling mistakes and bad branding might be rated as an 'easy' test, whereas a message with no spelling mistakes, good looking branding, a legit looking email address, but has a fake link could be rated as 'hard.' Allow organizations to select scenarios that meet the difficulty requirements for that particular campaign's goals. This can also tie in nicely to the reports section to show organizations how their users responded to phishing at varying levels of difficulty.