How to Assign Users in GoHighLevel Workflows

What the Assign User action does in GoHighLevel

The Assign User action updates the user associated with a contact when the workflow reaches the action. Depending on the selected configuration, GoHighLevel can preserve the current contact owner, assign a specific user, or select a user from an eligible pool.

This makes the action useful for more than distributing new leads. It can support ownership at different points in a lifecycle, such as assigning an inbound enquiry to sales, routing a qualified opportunity to a specialist, or transferring a customer to an account manager.

If the workflow only needs to alert a team while the existing owner remains accountable, an internal notification or task may be more appropriate. Use Assign User when the CRM record itself needs a different accountable user.

Where to add Assign User in a workflow

To add the action, open the relevant sub-account in GoHighLevel and go to Automation > Workflows. Open an existing workflow or create one, then select the plus icon on the workflow canvas and search for Assign User.

The available fields and labels can vary with the GoHighLevel interface and account configuration. Treat the visible settings in your account as the source of truth, and test the result before activating a workflow for live contacts.

1. Open the workflow that should control ownership.
2. Confirm that the trigger and any conditions identify the correct contacts.
3. Add the Assign User action at the point where ownership should change.
4. Choose the assignment method.
5. Decide whether an existing owner may be replaced.
6. Define the users eligible for assignment.
7. Save, publish, and test the workflow with representative contacts.

Choose the right assignment method

The assignment method should follow the operating rule for the workflow. The common choices are Contact Owner, Selected User, Any User, and Round Robin. These choices are not interchangeable because they express different forms of accountability.

Contact Owner

Use Contact Owner when the workflow should preserve or respect the current owner. This is useful when a contact moves between pipeline stages but should remain with the same salesperson, or when an automation performs administrative work without changing responsibility.

Before relying on this option, decide what should happen when the contact has no owner. An unassigned contact may require a separate fallback route, such as a fixed intake user or a controlled team pool. Do not assume that preserving ownership also solves the unassigned case.

Selected User

Use Selected User when every contact reaching that workflow path should be assigned to one known person. Typical examples include a dedicated qualification manager, a specialist handling one campaign, or an account manager responsible for a defined customer segment.

This option is simple, but it creates a concentrated ownership dependency. Review the selected user when roles change, and make sure the workflow does not continue assigning new contacts to someone who is no longer responsible for that work.

Any User

Any User allows GoHighLevel to choose from users that meet the configured eligibility rules. This can be appropriate when the main requirement is that a qualified person receives the contact, rather than a particular individual.

Use this option only when the eligible group is meaningful. A broad pool can create unclear accountability if it includes users who are not trained, available, or responsible for the relevant contact type.

Round Robin

Round Robin distributes contacts across a defined group in rotation. It is commonly used for new inbound leads where the team shares the same type of follow-up responsibility.

Round robin is not automatically fair or effective. It can distribute records evenly while still creating poor outcomes if some users are unavailable, have different territories, or handle different products. Confirm that the selected users share comparable capacity and responsibility before using this method.

Understand Reassign Contact before changing ownership

The Reassign Contact setting controls whether the action may replace an existing owner. This is one of the most important safeguards in the configuration.

• When reassignment is disabled, an existing owner can remain responsible instead of being overwritten.
• When reassignment is enabled, the selected assignment rule may move the contact to another user.

Use reassignment when the business process genuinely transfers accountability. For example, a qualified opportunity may move from an intake team to a specialist team. Avoid enabling it simply because the workflow needs to send a reminder or update a field.

A useful diagnostic question is: If this action changes the owner, who is expected to act differently afterward? If the answer is unclear, the workflow may need a notification, task, or status update rather than a new owner.

Configure the user pool and selection rules

When the workflow uses Any User or Round Robin, review every setting that limits or influences the pool. Depending on the account configuration, these may include a selected user type, a maximization or workload rule, and a list of available users.

Selected User Type

A user type or role filter helps separate eligible users from everyone else in the sub-account. Use it to distinguish sales representatives from administrators, support staff, or other users who should not receive this category of contact.

Do not treat a role label as proof of operational eligibility. Confirm that the users in the group have the right responsibility, permissions, working hours, and process knowledge.

Selected Maximization Rule

A maximization or workload rule influences how GoHighLevel selects among eligible users. The exact behavior and available labels should be verified in the account because configuration options can change.

Document what the rule is intended to achieve. For example, the goal might be a rotating allocation, a workload-aware choice, or a selection based on availability. If the team cannot explain the rule in plain language, it is difficult to audit when an assignment looks wrong.

Available Users

The available user list defines the people who may receive the contact through that action. Keep it limited to active users who are genuinely responsible for the relevant work.

• Remove users who have left the team or changed roles.
• Separate pools for different products, territories, or customer types where required.
• Review the pool when staffing or ownership rules change.
• Use a fallback path for contacts that do not match an eligible pool.

Use contact timezone carefully

The Use Contact’s Timezone option affects how time-based workflow behavior is interpreted around the contact. It can be useful when assignment is connected to follow-up actions that should respect the contact’s local time.

Timezone handling does not replace an ownership rule. A contact may be assigned correctly but still receive poorly timed communication if later workflow steps use the wrong timezone or if the contact’s timezone data is incomplete. Treat timezone as part of the follow-up design, not as a substitute for routing logic.

A practical setup sequence

This sequence keeps the configuration tied to a process instead of turning the workflow builder into a collection of isolated settings.

Example: routing new inbound leads

Imagine a business receives enquiries from a website. New contacts should be assigned to one of four sales representatives, but contacts already being handled by a representative should stay with that person.

A suitable design would first identify genuinely new inbound contacts, then use a controlled Round Robin pool for unassigned records. Reassignment would be disabled if the workflow can also be reached by existing contacts. A separate workflow path could handle qualified opportunities later, but only if qualification represents a clear transfer of responsibility.

By contrast, assigning every contact to the next salesperson regardless of current ownership may create duplicate outreach, split conversation history, and uncertainty about who should act next.

Test and maintain the workflow

Before publishing, test more than the successful path. Check at least one contact with an existing owner, one without an owner, one that should be excluded, and one that should enter each relevant assignment pool.

Monitor the workflow after launch by reviewing owner changes, unassigned contacts, duplicate follow-up, and contacts that remain untouched. If the workflow produces unexpected assignments, inspect the trigger, conditions, reassignment setting, and user pool in that order.

For broader CRM ownership design, pipeline structure, lead routing, and integration decisions, see ConsultEvo’s CRM Consulting service. A connected operating system also depends on clear relationships between CRM data, workflow actions, reporting, and team responsibilities. ConsultEvo’s client work portfolio provides additional context on connected CRM, automation, and operations systems.