Specify the text file to be imported.

The […] (three dots) button allows the user to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor.

More options

This setting specifies the filter that can remove data rows from the imported text file that satisfies the specific condition.

Define object properties to display in the output file.

The anchor attribute must be unique in the data source. Using the defined Anchor attribute, the rule checks to see if the anchor is already present in Active Directory. If the anchor is present, then this user was previously created, and the row in the data source is skipped.

Defines the column in the Data Source that will be used to determine if the user account already exists. This value is compared to the Active Directory Anchor attribute.

Because user names are likely to have duplicates, some other attribute with a unique value should be used to determine if records read from the data source have already been processed.

Determine the location within Active Directory to create new user accounts in.

RECOMMENDED: Create new objects in a separate OU then moved to the final location after provisioning is completed. The Text file | DynamicAttributes™ Relocate AD Users rule can be used to automatically move new user objects to the desired OU after the accounts are fully provisioned.

Account

By default, SamAccountName is automatically generated from the data source, provided it contains correctly named fields. If the field names differ from those required for the selected format, contact Cayosoft to configure an override format. Additionally, the SamAccountName must be unique within the target domain.

Define the domain name component of the new user UserPrincipalName (UPN). The default UPN suffix is defined in the Default domain setting within the AD Users web query. If you are using Microsoft 365, ensure this value is set to a domain registered in Microsoft 365/Entra ID.

By default, UserPrincipalName (UPN) is automatically generated from the data source, provided it contains correctly named fields. If the field names differ from those required for the selected UPN format, contact Cayosoft to configure an override format. The UPN value must be unique.

Define the FirstName data column in the data source. If the data source contains a field named FirstName, ignore this setting. Otherwise, use the selector. 

Define the Initials data column in the data source. If the data source contains a field named Initials, ignore this setting. Otherwise, use the selector. 

Define the LastName data column in the data source. If the data source contains a field named LastName, you can ignore this setting. Otherwise, use the Selector button to choose a field from the Data Source. 

Define the cn format. The default format uses fields named FirstName and LastName. You can use predefined options, use the expression builder to select a field from the data source, or contact Cayosoft for support.

Define the displayName format. The default format uses the cn value. You can use predefined options, use the expression builder to select a field from the data source, or contact Cayosoft for support.

Define the description data column in the data source. If the data source contains a field name Description, you can ignore this setting. Otherwise, manually enter a static text value or use the selector button to choose a field from the data source. 

Settings

Define a password for new accounts:

• Static text

• A custom data column in the CSV file

• A random password

NOTE: Static passwords and passwords from the data source must meet the Active Directory Password complexity policy of the target container; alternatively, the account is created in a disabled state. Randomly generated passwords are generated to match both the Active Directory password complexity policy and additional complexity requirements defined in the Cayosoft Administrator password complexity policy.

Define the settings to control default Active Directory user object settings.

Define the account expiration attribute for Active Directory. You can populate this field using a data source column or a static text string entered manually in the MM/DD/YYYY or YYYY-MM-DD format.

Organization

Define the values for the default organization attributes in Active Directory. If the data source contains the field names, you can ignore this setting. Otherwise, manually enter a static text value or use the selector button to choose a field from the data source.

Use the selector button to choose a field from the data source that is a unique identifier for the manager. Typically, the identifier used is the EmployeeNumber or EmployeeID value.

Define an Active Directory attribute used to link the manager and the Manager identifier value.

Contact info

Define the values for the default contact info attributes in Active Directory. If the data source contains the field names, you can ignore this setting. Otherwise, manually enter a static text value or use the selector button to choose a field from the data source.

NOTE: If you need alternative SMTP addresses, you can run the AD Users | Set Proxy Addresses rule after the create rule.

IMPORTANT: The country/region should be represented by a 2-character code based on ISO-3166. For example, use code DE to define Germany.

Alternative name generation rules

Define the behavior in case of a naming conflict:

• Suffix the name with a numeric counter value and continue

• Log error in the Execution History and continue

• Use alternative generation rules, log error in the Execution History and continue

• Use alternative generation rules, suffix the name with a numeric counter value and continue

Define the alternative values for the attributes. You can use the expression builder to define further generaion rules.

Define the counter format to suffix conflicting users with a numeric value and generate unique names across the organizations.

TIP: To use two-digit numbers, use 00. To start from a specific number (e.g., 5), specify 5.

Define the logic for the suffix addition:

• Always add the counter

• When naming is not unique

The counter suffix does not apply when the name conflict resolution logic is set to logging an error in the Execution History.

Multi-valued attributes

Enable or disable the support for multi-valued attributes in AD users.

Define a list of multi-valued attributes using the selector.

IMPORTANT: Link source data attributes to matched attributes in Other properties to assign multiple values to corresponding attributes. Otherwise, the values won't be assigned.

Other properties

Map data source columns and target user properties using the picker.

Data mapping also can be set by the script.

If you want every provisioned user to have extension attribute 1 populated with some string value then use this

:{@{'extensionAttribute1'='YourString'}}

If you want every provisioned user to have extension attribute 2 populated with the corresponding value from the column in your data source file, then use this:

{@{'extensionAttribute2'=$_.EXT2}}

since EXT2 is the name of the column from your data source.

NOTE: If you set mapping for the same properties both in Other properties and Other properties script, attribute values will be updated by the script.

Notify manager

Define the notification behavior for the user creation event.

NOTE: Pick Yes to send an email for each created user. Pick Yes (send one email) to send one email for all created users.

Email subject.

TIP: It is possible to customize email subjects by using different tokens, see Customizing an automation rule or web action output email. 

Message text.

TIP: It is possible to customize email messages by using different tokens, see Customizing an automation rule or web action output email.