Recipient Groups

This dropdown menu allows you to select which client the group is associated with. This helps in organizing and managing groups under different clients while ensuring recipient data remains segregated.

This dropdown menu allows you to set a default language for the group. This setting determines the language used for group content delivery when the recipient records do not specify a language.

Enable this checkbox if this group is intended to execute a Portable Media Attack.

Ensure the CSV is correctly formatted

The import file should contain text in UTF-8 encoding. Each line should represent one recipient. Each record can have 1 to 12 columns, separated by a comma, colon, or semicolon (, : or ;). The possible columns are:

1. Email - recipient's email address (mandatory)

2. Full Name - recipient's full name

3. Staff - job position or related information

4. Location - recipient's location

5. Division - company division

6. Comment - any custom comment

7. Link - unique link part for the landing page (ensure uniqueness if specified; otherwise, it will be generated automatically)

8. Phone - recipient's phone number

9. Language - recipient's language

10. Gender - recipient's gender ("m" for Male; "f" for Female)

11. First Name - recipient's first name

12. Last Name - recipient's last name

Import CSV

Select "Choose File" to import your recipients.

You can add your recipients by using an LDAP server. For setup instructions, refer to the LDAP Integration article.

Import Options

Update existing recipients

• If this option is enabled, any existing recipients in this group will have their attributes updated during the LDAP import. This ensures that the latest information from the LDAP server is reflected in the recipient list.

Add recipients to bound campaigns

• Enabling this option will add the imported recipients to any campaigns that are already bound to the group. This is useful if you want to expand the reach of your current campaigns to include new or updated recipients.

Send emails if bound campaigns are running

• If this option is selected, emails will be sent to the newly imported recipients if they are part of running campaigns. This ensures that any active campaigns will immediately include the new recipients in their email distribution.

Add more groups

• This option allows you to import additional groups already present in Lucy. This can be helpful if you want to organize recipients into specific categories or segment groups for targeted campaigns.

LDAP Server

Select the LDAP Server which needs to be associated with this group.

LDAP Search

You can use standard Active Directory search filters, such as:

(|(objectClass=inetOrgPerson)(objectClass=user))

For more information, refer to the Microsoft Documentation.

LDAP Search Examples

Goal: Import all users in the distribution group name "IntuneLucy-DevOps"

Directory Structure:

Base DN -> Beck.ai OU -> Admin Users OU -> Distribution Groups Group -> IntuneLucy-DevOps

A well-formulated Active Directory search filter to obtain all users in the Group = IntuneLucy-DevOps:

(&(objectClass=user)(memberOf=cn=IntuneLucy-DevOps,ou=Distrubution Groups,ou=Admin Users,dc=beck,dc=ai))

&: This is the logical operator "AND". It indicates that all the conditions enclosed within the parentheses must be true for the query to return a result. This operator combines multiple search filters.

(objectClass=user): This filter specifies that the object being searched should be of the type "user". The objectClass attribute in LDAP is used to define the schema or type of an object in the directory.

(memberOf=cn=IntuneLucy-DevOps,ou=Distrubution Groups,ou=Admin Users,dc=beck,dc=ai): This filter is used to find users who are members of a specific group. Here's a breakdown of the group's distinguished name (DN):

• cn=IntuneLucy-DevOps: "cn" stands for Common Name. In this case, it refers to the name of the group.

• ou=Distrubution Groups: "ou" stands for Organizational Unit.

• ou=Admin Users: Another Organizational Unit, indicating a higher-level grouping within the directory.

• dc=beck,dc=ai: "dc" stands for Domain Component. These components are part of the LDAP naming context and represent different levels of the domain.

This query is structured to ensure that only objects that are users (objectClass=user) and are members of the specified group (memberOf=...) are returned.

Import

After successfully retrieving the desired recipients from your company directory, select the checkbox to include All, and click "Import" to begin the import process.

You can add your recipients by using Azure Entra ID. For setup instructions, refer to the Azure Applications.

Import Options

Update existing recipients

• If this option is enabled, any existing recipients in this group will have their attributes updated during the Entra ID import. This ensures that the latest information from the Entra ID server is reflected in the recipient list.

Add recipients to bound campaigns

• Enabling this option will add the imported recipients to any campaigns that are already bound to the group. This is useful if you want to expand the reach of your current campaigns to include new or updated recipients.

Send emails if bound campaigns are running

• If this option is selected, emails will be sent to the newly imported recipients if they are part of running campaigns. This ensures that any active campaigns will immediately include the new recipients in their email distribution.

Add more groups

• This option allows you to import additional groups already present in Lucy. This can be helpful if you want to organize recipients into specific categories or segment groups for targeted campaigns.

Azure Application

Select the Azure Application which needs to be associated with this group.

Azure Search

Filter by Groups -> Select the Group dropdown menu:

Filter by Search Parameters -> Enter Microsoft search filters

Scenario 1: Filter by Email Domain

To import only recipients whose email domain ends with "@lucysecurity.company", use the endswith function:

(mail, '@lucysecurity.com')

This filter ensures that only users with emails ending in "@lucysecurity.company" are included in the import.

Scenario 2: Filter by Name Prefix

To import recipients whose names begin with "User", utilize the startswith function:

startswith(displayName, 'User')

This filter will match and import users whose display names start with "User".

Scenario 3: Filter by Location

To find all users located in 'Ext1', you can directly match the officeLocation attribute:

officeLocation eq 'Ext1'

This query ensures that only users with 'Ext1' listed as their office location are selected.

Scenario 4: Filter by Phone Number Exclusion

To exclude recipients whose phone number is '911', apply the ne (not equal) operator:

mobilePhone ne '911'

This filter imports users whose mobile phone number is not '911'.

Import

After successfully retrieving the desired recipients from your company directory, select the checkbox to include All, and click "Import" to begin the import process.

Automatically Add to Bounded Campaigns

When this option is selected, the recipients will be imported automatically and added to all campaigns the recipient group is bound to.

Automatically Add to Bounded Campaigns and Schedule Plans

When this option is selected, the recipients will be imported automatically and added to all campaigns the recipient group is bound to, in addition any Schedule Plans with this recipient group will also be updated to reflect the new recipients.

When this option is selected, the recipients not "Active" or deleted in the company directory will be automatically removed from the group and all subsequent campaigns.

When this option is selected, no recipients will be deleted even if Lucy has determined the recipient is not "Active" in your company directory.

Filter by Groups -> Select the Group dropdown menu:

Filter by Search Parameters -> Enter Microsoft search filters

Scenario 1: Filter by Email Domain

To import only recipients whose email domain ends with "@lucysecurity.company", use the endswith function:

(mail, '@lucysecurity.com')

This filter ensures that only users with emails ending in "@lucysecurity.company" are included in the import.

Scenario 2: Filter by Name Prefix

To import recipients whose names begin with "User", utilize the startswith function:

startswith(displayName, 'User')

This filter will match and import users whose display names start with "User".

Scenario 3: Filter by Location

To find all users located in 'Ext1', you can directly match the officeLocation attribute:

officeLocation eq 'Ext1'

This query ensures that only users with 'Ext1' listed as their office location are selected.

Scenario 4: Filter by Phone Number Exclusion

To exclude recipients whose phone number is '911', apply the ne (not equal) operator:

mobilePhone ne '911'

This filter imports users whose mobile phone number is not '911'.