Differences

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

--- add_mail_recipients [2020/01/20 18:18] – lucy
+++ add_mail_recipients [2021/10/26 13:18] (current) – [Import Recipients] lucysecurity
@@ Line 1: / Line 1: @@
 ===== Introduction=====
-Every campaign needs a recipient group to work. The recipient group are the users who receive the attack simulation or 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 start by grouping users by department, location (if you have multiple office locations), or even domains (if there are multiple domains). The recipients can be in any number of groups and you can set up an unlimited number of groups.
+Every campaign needs a recipient group to work. The recipient group is the users who receive the attack simulation or 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 start by grouping users by department, location (if you have multiple office locations), or even domains (if there are multiple domains). The recipients can be in any number of groups and you can set up an unlimited number of groups.
 ===== How to Enter Your Recipients? =====
-Recipients and groups can be configured under Admin/Recipients.
+Recipients and groups can be configured under **Settings -> Recipients**.
 {{ 45.jpg?direct&600 }}
-You can either add them manually (1), import them (2) or search the internet by using the "[[scan_for_mail_addresses|SCAN FEATURE]]" (3). The groups are always defined globally and you can re-use them among different campaigns.
+You can either add them manually (1), import them (2), or search the internet by using the "[[scan_for_mail_addresses|SCAN FEATURE]]" (3). The groups are always defined globally and you can re-use them among different campaigns.
 {{ 46.jpg?direct&600 }}
@@ Line 21: / Line 21: @@
 ===== Import Recipients =====
-You can import the recipients via file or via [[ldap_integration|LDAP]]. There is no restriction on the number of recipients you can add to a group (even though your license might restrict the sending of all mails).
+You can import the recipients via file, via [[ldap_integration|LDAP]] or via [[azure_synchronization|Azure AD synchronization]]. There is no restriction on the number of recipients you can add to a group (even though your license might restrict the sending of all emails).
-**SYNTAX**: LUCY requires a [[recipient_import_and_syntax_issues|special syntax]]. Otherwise it will throw an error. In LUCY version > 3.1 it will continue the import with the correct recipients. In an awareness or phishing campaign which is send via email, it will need at least the mail address as a mandatory field. All other fields are voluntary.
+**SYNTAX**: LUCY requires a [[recipient_import_and_syntax_issues|special syntax]]. Otherwise, it will throw an error. In LUCY version > 3.1 it will continue the import with the correct recipients. In an awareness or phishing campaign which is sent via email, it will need at least the mail address as a mandatory field. All other fields are voluntary.
-The import file should contain one recipient per line. Each record should consist of 1 to 7 columns separated by the colon symbol (:). All columns, except for the first one, are optional. If you want to skip the column value, just don't type anything between columns separators (:). You can skip the columns at the end of the record - for example, if you have only Email and Name, you can just specify these 2 columns. The email address is mandatory for the Recipient list. All other fields (like Name) are compulsory. If you want to send a personalized email (using the %name% variable within the email or landing page) you need to define the Name field too. The possible columns are:
+The import file should contain one recipient per line. Each record should consist of 1 to 12 columns separated by the colon (:) or semi-colon symbol (;). All columns, except for the first one, are optional. If you want to skip the column value, just don't type anything between column separators (:). You can skip the columns at the end of the record - for example, if you have only Email and Name, you can just specify these 2 columns. The email address is mandatory for the Recipient list. All other fields (like Name) are compulsory. If you want to send a personalized email (using the %name% variable within the email or landing page) you need to define the Name field too. The possible columns are:
   * 1.Email - Recipient's e-mail address
-  * 2.Name - Recipient's name
+  * 2.Full Name - Recipient's full name
-  * 3.Staff - Job position or related
+  * 3.Staff - Job position or related to that
   * 4.Location - Recipient's location
   * 5.Division - Company division
   * 6.Comment - Any custom comment
   * 7.Link - Unique link part for the Landing Page. Only use this if access to the internet by clicking on a link in an email is not possible (e.g. if you use some terminal client or a separate browser to access the internet). More information about this can be found [[configuration_for_clients_that_cannot_click_on_links_in_mails|here]].
-  * 8.Phone - recipient phone number
+  * 8.Phone - Recipient's phone number
-  * 9.Language - recipient language
+  * 9.Language - Recipient's language
+  * 10.Gender - Recipient's gender.("m" - Male; "f" - Female)
+  * 11.First Name - Recipient's first name
+  * 12.Last Name - Recipient's last name
-Note about language: if you upload a recipient group file (txt or CSV) and want to specify the language you need to use the English description (example "spanish").
+Also in LUCY, it is possible to add **Custom Fields** to recipient groups. So if there are any custom fields one has to add values for these fields by adding columns to the end of the line separating them with colons or semi-colons too.
+Note about language: if you upload a recipient group file (txt or CSV) and want to specify the language you need to use the English description (example "Spanish").
-**FILE FORMAT**: You can import a plain text file (.txt) or -csv format and name it as you want.
+**FILE FORMAT**: You can import a plain text file (.txt) or CSV (.csv) format and name it as you want.
-**EXAMPLE**: Your CSV or TXT file should look something like this:
+**EXAMPLE**: Please note that **Sample File** is available for download from **Import** page. Your CSV or TXT file should look something like this:
-john@example.com:John Doe:senior consultant:new york:accounting
+john@example.com:John Doe:senior consultant:new york:accounting\\
-marcus@aurelius.com:Marcus Aurelius
+marcus@aurelius.com:Marcus Aurelius\\
-peter@example
+peter@example.com\\
-sarah@example:Sarah::boston
+sarah@example.com:Sarah::boston\\
-{{testrecipient2.png?600}}
+{{import_recipients.png?600}}
+Please note, that using the file import into one particular group containing new or updated info in any fields (except email address) would result in the data being overwritten with the new file import.\\
+For example, Recipient Group 1 contains a recipient with an email user1@default.com who has Country set as Luxemburg. The file import is initiated into this recipient group and the user has Country in the .csv file set as Germany. Once the import is completed, the info will be updated with the over-written Country value to Germany.
 ===== Adding multiple groups in a campaign  and associating them with a scenario =====
@@ Line 60: / Line 65: @@
 {{ 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 default mapping is "campaign and awareness". This means the user group will receive the phishing simulation and if configured, also the le-earning content. If you wish, you can limit the mapping to "awareness only" or "campaign only". If you for example configure "campaign only", the according group would only get the attack simulation, but no e-learning.
-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.
+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 85: / Line 90: @@
 Step 3: Rename your group in order to identify it better
-As an alternative you can also hover over the link and look at the group ID. When you hover over the groups within the generic recipient settings, you will see also the corresponding ID's.
+As an alternative, you can also hover over the link and look at the group ID. When you hover over the groups within the generic recipient settings, you will see also the corresponding ID's.
 {{ recipient_association.png?600 }}
@@ Line 112: / Line 117: @@
 ===== 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 to checkbox:
+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 to the checkbox:
 {{ recipient_filtering.png?600 }}
@@ Line 119: / Line 124: @@
 ===== 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:
+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 user's details or (3) remove the user stats from the specific campaign:
 {{ recipien_man.png?600 }}
@@ Line 134: / Line 139: @@
 ===== Import Error-Log =====
-LUCY will create an import error log which will help you to quickly identify import errors with mail addresses that had a syntax error. For LUCY please [[recipient_import_and_syntax_issues|click here]]. Please not that LUCY cannot handle wrong syntax. Also don't use header lines. Duplicate or wrong entries will not be imported.
+LUCY will create an import error log which will help you to quickly identify import errors with mail addresses that had a syntax error. For LUCY please [[recipient_import_and_syntax_issues|click here]]. Please note, that LUCY cannot handle the wrong syntax. Also, don't use header lines. Duplicate or wrong entries will not be imported.
 {{ import_error.png?600 }}
@@ Line 141: / Line 146: @@
 ===== Custom Recipient Fields =====
-In LUCY you have the ability to create custom recipient fields. You can add any new recipient attribute you want (e.g. city, gender, education etc.). Those attributes can be used for using customized statistics in LUCY (dashboard filters or raw exports).
+In LUCY you have the ability to create custom recipient fields. You can add any new recipient attribute you want (e.g. city, gender, education, etc.). Those attributes can be used for using customized statistics in LUCY (dashboard filters or raw exports).
@@ Line 147: / Line 152: @@
 In order to create a new custom field go to recipients. Under the recipient link you will find the "custom field" link:
-{{ recip_custom.png?600 }}
+{{ custom_fields1.png?600 }}
 The new recipient attribute (can be freely chosen) is then added as a new attribute in the recipient list:
-{{ recipient_custom2.png?600 }}
+{{ custom_fields2.png?600 }}
-{{ recipient_csutom3.png?600 }}
+{{ custom_fields3.png?600 }}
 ====== E-Mail Scanning Feature (E-Mail Spider) ======
-Under the recipient tab you find an option to scan for mail addresses in the internet.
+Under the recipient tab, you find an option to scan for mail addresses on the internet.
 {{ scanmails.png?600 }}
@@ Line 166: / Line 171: @@
 ====== Analysis of the campaign based on recipient attributes ======
-All attributes defined within the Recipient group can be analyzed within the campagin statistics or data exports:
+All attributes defined within the Recipient group can be analyzed within the campaign statistics or data exports:
 {{ custom_attr_stats.png?600 }}