Differences

This shows you the differences between two versions of the page.

--- add_mail_recipients [2018/05/11 07:54] – lucy
+++ add_mail_recipients [2018/05/31 16:41] – lucy
@@ Line 1: / Line 1: @@
-===== How to Enter Your Recipients =====
+===== Introduction=====
-In every campaign you need to configure the target email addresses, USB devices or phone numbers (users) under Admin/Recipients.
+Every campaign needs a recipient group to work. The recipient group are the users which receive the attack simulation or the awareness content. You can create multiple groups for a single campaign. Groups can be used within LUCY to target users with specific phishing or training campaigns. Many organizations will begin with dividing users into groups by department, location (if you have multiple office locations), or even domains (if there are multiple domains). Recipients can be in as many groups as they need to be in, and you can have an unlimited number of groups set up.
+===== How to Enter Your Recipients? =====
+Recipients and groups can be configured under Admin/Recipients.
 {{ 45.jpg?direct&600 }}
@@ Line 11: / Line 16: @@
 We recommend importing them because it will enable you to create a custom text file with additional information about each target user (e.g. defining the division or location where they work). This information can later be used for automatic analysis and statistics. The more information you provide, the better.
-**Note**: Searching the internet without a Bing or Google API won't get you the same results as if you searched directly with a search engine. This feature is still in beta release.
+**Note**: Searching the internet without a Bing or Google API won't get you the same results as if you searched directly with a search engine.
 ===== Import Recipients =====
@@ Line 43: / Line 49: @@
 {{ 48.jpg?direct&600 }}
+===== Adding multiple groups in a campaign  and associating them with a scenario =====
+LUCY allows you to add multiple groups in one campaign. After you added a group, you will be asked to define:
+  - mapping (1)
+  - scenario (2)
+{{ mapping_rec.png?600 }}
+The default mapping is "campaign and awareness". This means the user group will recieve the phishing simulation and if configured, also the elarning content. If you wish, you can limit the mapping to "awarness only" or "campaign only". If you for example configure "campaign only", the according group would only get the attack simulation, but no elearning.
+The scenario association can be used to control, which group gets which attack scenario. In the screenshot you see (2) that all the available scenarios added to the campaign will be displayed. Example: If you select 2 scenarios with a specific group, each user from this group will get two emails (one from scenario 1 and one from scenario 2). If you don't want the users to get multiple emails, you can enable the checkbox "Distribute users over selected scenarios". Lucy will then randomly split the users over the selected scenarios. Every user will get a unique single attack and no user will be attacked with the same scenario twice. If you want to control the distribution of receivers even more deeply, you would have to create a [[scheduler|scheduler rule]]. This allows the distribution to be even more complex.
@@ Line 48: / Line 67: @@
 In LUCY you can add recipients to a running campaign. Please [[i_want_to_add_a_few_extra_mails_into_a_running_campaign|click here]] to read more.
 ===== Language considerations =====
@@ Line 67: / Line 87: @@
 {{ addrec3.png?600 }}
+===== Disable recipients from a group within a campaign =====
+You can load a group into LUCY and then uncheck users, you don't want to test or train in this specific campaign. Just click on the according checkbox:
+{{ recipient_filtering.png?600 }}
+===== Recipient actions within a running campaign =====
+Under the statistics/recipient tab you will have a table view of all recipients used in a campaign. In the last column you can (1) re-send an attack to a specific user, (2) edit the users detail or (3) remove the user stats from the specific campaign:
+{{ recipien_man.png?600 }}