Description:

This step adds a user to one or more existing Active Directory groups.

The Add User To Active Directory Groups workflow step connects to Microsoft Active Directory using a configured LDAP connection and adds the specified user to one or more Active Directory groups.

The step identifies the user by username and accepts a list of Active Directory group names. Multiple groups can be specified in a single workflow step, simplifying role assignment and access provisioning operations.

This step provides an efficient way to automate group membership assignments during employee onboarding, role changes, department transfers, project assignments, or identity lifecycle workflows.

The step supports:

• Active Directory group membership management
• Adding a user to multiple Active Directory groups
• Configurable LDAP connections
• Dynamic username and group name inputs using workflow variables
• Batch assignment of multiple group memberships
• Integration with Microsoft Active Directory

This step can be used for:

• Employee onboarding
• Role-based access assignment
• Department transfers
• Project team provisioning
• Identity lifecycle management
• Access management
• Business process automation

Usage:

The Add User To Active Directory Groups step is typically placed after user creation, approval, onboarding, or role assignment activities within a workflow.

The workflow adds the specified user to all configured Active Directory groups using the selected LDAP connection.

A typical workflow might look like this:

Once the user has been added to the required groups, later workflow steps can:

• Enable the user account
• Assign application permissions
• Synchronize identity systems
• Notify administrators
• Generate audit reports
• Validate group memberships
• Continue identity lifecycle management processes

You need to set up an LDAP connection before using this step.

Go to:

Integration → Connections → Generic Connections

On the Manage Generic Connections page, click:

Actions → Create

Configure an Active Directory connection before using this workflow step.

A sample connection is provided here for reference. 

Example:

Let’s build and execute the “clsAddADUserToGroupsDef” example:

• Create a new process definition named “clsAddADUserToGroupsDef” and open it in designer mode. 
• Drag a “clsAddADUserToGroups” step to the canvas.
• Connect the dots between the “Start” and “clsAddADUserToGroups” steps.
• Click the "clsAddADUserToGroups" step to configure its "Required" properties. Provide a name for the step. Select the LDAP connection from the drop-down list. Enter the “User Name”. Click the button to configure the “Group Names”. Click the Save button to confirm. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to configure the “Group Names”. Click the Add Row (+) button to insert an empty row. Enter the “Active Directory” group name, then click Save. You may add multiple group names using the Add Row feature. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Add User To Groups step, FlowWright connects to the configured Active Directory server using the selected LDAP connection and attempts to add the specified user to each configured Active Directory group. If all requested group membership assignments are completed successfully, the workflow follows the Added return path. If the user cannot be found, one or more groups do not exist, the user is already a member of a group, or the LDAP connection cannot be established, the workflow follows the NotAdded return path.

• Click the process step to view its properties. The step should successfully add the specified user to the configured Active Directory groups and return Added upon successful completion. Use the Get User Groups workflow step to verify that the user has been assigned to the expected groups.

Tips:

• Verify that the LDAP connection has been configured before using this step.
• Ensure that the LDAP account has permission to modify Active Directory group memberships.
• Verify that the specified user exists before attempting to assign group memberships.
• Ensure that each specified Active Directory group already exists.
• Use workflow variables to dynamically provide the username and group list.
• Use the Added and NotAdded return paths to implement appropriate success and error handling.
• Combine this step with Create User, Enable User, Update User Attributes, Get User Groups, or Remove User From Groups steps to automate complete Active Directory identity management workflows.

Notes:

• A valid LDAP connection must exist before this step can execute.
• The configured LDAP account must have sufficient permissions to modify Active Directory group memberships.
• The specified user account must already exist.
• All specified Active Directory groups must exist before this step is executed.
• Adding a user who is already a member of a group may not modify the existing membership.
• Network connectivity or authentication issues may prevent group membership assignments from completing successfully.
• The workflow should include appropriate error handling for the NotAdded return path.
• The workflow result depends on the current state of Active Directory and the permissions granted to the configured LDAP connection.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Note: Verify and complete any missing configuration after importing the sample, including:

• LDAP connection
• Username mapping
• Group name list mapping
• Workflow variable mappings
• Active Directory permissions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.