Agency Workflow Builder Default Settings

TL;DR

HighLevel now allows agencies to set a default Workflow Builder preference (Standard or Advanced) for their sub-accounts. This is a convenience update for agencies managing multiple accounts, not a critical action item this week.

Who this affects

This update affects agency owners and their teams managing Go HighLevel sub-accounts. Specifically, it impacts those who create new sub-accounts or want to standardize the workflow builder experience across existing ones. HighLevel has not confirmed which plans this feature is available on, so assume it is generally available to agencies.

What changed

Agencies now have more control over the default Workflow Builder experience for their sub-accounts. The core changes are:

• Agencies can set the default Workflow Builder to either Standard or Advanced from their agency-level settings.
• This default choice can be automatically applied to any new sub-accounts created within the agency.
• Agencies also have the option to apply this default Workflow Builder choice to their existing sub-accounts.

HighLevel has not confirmed if there are any limits or plan gating associated with this feature. HighLevel has not confirmed the rollout status.

Where to find it

This new setting is located within your HighLevel Agency account. Navigate to Agency Settings > Workflow Settings page to configure your preferred default Workflow Builder.

How agencies will use this

An agency owner, managing a portfolio of 50 client sub-accounts, decides to standardize all new and existing sub-accounts to use the Advanced Workflow Builder. This decision is made because their team of workflow builders is experienced and finds the Advanced Builder more efficient for complex automations. The agency navigates to Agency Settings > Workflow Settings page. They select 'Advanced' as the default Workflow Builder. They then choose the option to apply this setting to all existing sub-accounts. Now, whenever a team member creates a new sub-account or opens the workflow builder in an existing sub-account, it will default to the Advanced view, streamlining their team's operations and reducing friction in their workflow development process. This eliminates the need to manually switch the builder type for each sub-account or educate clients on two different builder interfaces.

Our take

This is a convenience update. It addresses a minor point of friction for agencies, particularly those creating many new sub-accounts or those with specific preferences for the Workflow Builder interface. It's not a major new feature that unlocks new capabilities for clients or significantly alters how agencies operate this week. It simply standardizes a preference. HighLevel has labeled this update as 'major' in significance, but without a reason, it's hard to justify that assessment based on the stated facts. For most agencies, this is a background setting to check once and then forget.