Description:

This step adds one or more users to an existing Active Directory group.

The Add Users To Active Directory Group workflow step connects to Microsoft Active Directory via a configured LDAP connection and adds the specified users to an existing Active Directory group.

The step identifies the target group by its name and accepts a list of usernames to add to it. Multiple users can be added in a single workflow step, simplifying user provisioning and access management operations.

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

The step supports:

• Active Directory group membership management
• Adding multiple users to an existing group
• Configurable LDAP connections
• Dynamic group name and username inputs using workflow variables
• Batch processing of multiple user accounts
• Integration with Microsoft Active Directory

This step can be used for:

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

Usage:

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

The workflow adds the specified users to the selected Active Directory group using the configured LDAP connection.

A typical workflow might look like this:

Once the users have been added to the group, later workflow steps can:

• 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 “clsAddADUsersToGroupDef” example:

• Create a new process definition named “clsAddADUsersToGroupDef” and open it in designer mode. 
• Drag a “clsAddADUsersToGroup” step to the canvas.
• Connect the dots between the “Start” and “clsAddADUsersToGroup” steps.
• Click the "clsAddADUsersToGroup" 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 “UserNames”. 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 “UserNames”. Click the Add Row (+) button to insert an empty row. Enter the Username, then click Save. You may add multiple Usernames 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 Users To Group step, FlowWright connects to the configured Active Directory server using the selected LDAP connection and attempts to add the specified users to the designated Active Directory group. If the operation completes successfully, the workflow follows the Added return path. If the group cannot be found, one or more users do not exist, the users are already members of the 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 add the specified users to the Active Directory group and return Added upon successful completion. Use the Get Group Members or Get User Groups workflow step to verify that the users have been successfully added to the group.

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 group exists before attempting to add users.
• Ensure that each specified user account exists in Active Directory.
• Use workflow variables to dynamically provide the group name and user 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 Users From Group 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 Active Directory group must already exist.
• All specified user accounts should exist before executing this step.
• Adding a user who is already a member of the group may not modify the existing membership.
• Network connectivity or authentication issues may prevent users from being added to the group.
• The workflow should include appropriate error handling for the NotAdded return path.
• The workflow result depends on the current state of the Active Directory group 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
• Group name mapping
• Username 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.