AI Studio Access Is Now Live Across GoHighLevel

Wait Action Enhancement: TikTok DM Replies  

What’s New:
Instead of continuing after a fixed delay, your workflow can pause until someone replies to your TikTok DM.

Where in GHL:
Found in Automation → Workflows using the Wait action after sending a TikTok DM.

Impact:
Your automation responds when someone actually joins the conversation, rather than after a timer runs out.

Recommended For:
Anyone using TikTok DMs to start conversations with potential customers.

---

India Recurring Mandate Support for Affiliate Indian Signup Pages  

What’s New:
Supports recurring payment mandates for Indian affiliates, helping subscriptions comply with local banking requirements.

Where in GHL:
Available on Affiliate Program signup pages for users in India.

Impact:
Creates a smoother signup experience while reducing payment failures for recurring subscriptions.

Recommended For:
Agencies, SaaS businesses, and affiliate programs onboarding customers in India.

---

Housecall Pro – More Workflow Actions & Triggers  

What’s New:
Adds new workflow triggers and actions for the Housecall Pro integration, giving you more ways to automate field service processes.

Where in GHL:
Inside Automation → Workflows when using the Housecall Pro integration.

Impact:
Expands automation possibilities between HighLevel and Housecall Pro, reducing manual work and improving operational efficiency.

Recommended For:
Home service businesses, field service companies, and agencies managing Housecall Pro clients.

---

Email Services Dashboard for Agencies  

What’s New:
Introduces a centralized dashboard where agencies can monitor email services across their accounts.

Where in GHL:
Found in the Agency View under the new Email Services Dashboard.

Impact:
Makes it easier to monitor email health, identify issues, and manage deliverability from one place.

Recommended For:
Agency owners, support teams, and admins managing multiple client email services.

---

Email Sequences Now Available in Beta Labs  

What’s New:
Introduces Email Sequences as a Beta Labs feature, providing another way to create structured email follow-up campaigns.

Where in GHL:
Enable it from Settings → Labs, then access Email Sequences after activation.

Impact:
Cuts down the time spent checking different areas just to see how your email services are performing.

Recommended For:
Marketers, agencies, coaches, and businesses running nurture campaigns or onboarding emails.

---

Group Your Contacts by Source in Dashboards & Reporting  

What’s New:
Lets you organize contact reports based on where your leads originated.

Where in GHL:
Available within Dashboards & Reporting when viewing contact analytics.

Impact:
Makes it easier to compare lead sources and identify which marketing channels are producing the best results.

Recommended For:
Marketing teams, agency owners, and businesses tracking campaign performance across multiple lead sources.

---

MMLite Adoption Banner in Conversations  

What’s New:
Displays a helpful banner inside Conversations to encourage users to adopt the new MMLite messaging experience.

Where in GHL:
Appears within the Conversations module for eligible accounts.

Impact:
Helps users discover and transition to MMLite while highlighting its benefits directly inside the messaging interface.

Recommended For:

Current HighLevel users exploring the latest messaging experience and teams preparing to migrate to MMLite. 

AI Studio Access is no longer limited to Labs. It’s now live across all GoHighLevel locations, which makes it a much bigger part of the everyday GHL experience.

For agencies, the biggest change is not just availability. It’s control.

GoHighLevel is now putting more focus on who should actually have access to AI Studio. Instead of assuming every sub-account user or admin should be able to use it, access now needs to be managed more deliberately.

There’s also a new Home banner that appears when people inside your sub-accounts still need AI Studio Access. From that banner, eligible agency users can open the configuration screen, search for users, and decide who should be enabled.

You can switch AI Studio on for the whole team, or just pick the people who actually need it. That makes it easier to match access to each person’s job.

This is especially useful if you have client users, VAs, contractors, or team members who don’t need AI Studio as part of their day-to-day work.

After you confirm the users, GoHighLevel usually only needs a few minutes to finish the setup. Once it’s done, they can jump into AI Studio and start using it.

The biggest change with AI Studio Access is how permissions now work for sub-account users.

Sub-account users and admins no longer get access by default. Their AI Studio permissions are now turned off unless they already had AI Studio enabled while it was still in Labs.

That exception matters.

If a user already had access through Labs, GoHighLevel keeps that access in place. You don’t need to re-enable those users just because AI Studio has moved into wider release.

For everyone else, access now needs to be granted intentionally.

This puts the decision back in the agency’s hands. You can look at each user’s role and decide whether AI Studio makes sense for them instead of giving access across the board.

That can be useful if your agency has a mix of internal staff, VAs, contractors, client users, or team members with limited responsibilities.

The key takeaway is simple: don’t assume a user can open AI Studio just because they have access to the sub-account. AI Studio Access is now its own permission decision, and agencies need to review it accordingly.

AI Studio Access matters because agencies now have more control over who can use one of GoHighLevel’s newer AI tools.

It might look like a minor permissions tweak, but it matters a lot more when you’re managing several sub-accounts and a bunch of different users.

Not every user needs access to AI Studio.

Your team could have one person building campaigns, another handling admin work, and a client who only checks results. They don’t all need AI Studio, so now you can set access accordingly.

It keeps your setup from getting cluttered with access people don’t need.

It can also reduce confusion. If users only see the tools they actually need, there’s less chance of someone clicking into AI Studio without knowing what it’s for or how it should be used.

For agencies with growing teams, this becomes even more important. Permissions are easier to manage when they match the user’s role from the start.

The main benefit here is control. You can decide who actually needs AI Studio instead of giving every staff member, contractor, or client user the same access.

AI Studio Access is managed from the new Home banner in GoHighLevel. You’ll first open the configuration screen, then choose whether to give access to everyone or only selected users.

You’ll then confirm your choices and allow a few minutes for setup to finish. Here are the steps to configure AI Studio Access in GoHighLevel.

• Find the AI Studio Access Banner.
• Open the AI Studio Access Configuration.
• Choose Who Gets AI Studio Access.
• Confirm AI Studio Access.

To start, make sure you are logged in to your GoHighLevel agency account with a user role that can manage this access.

• Start from the GoHighLevel Home screen in your agency account.

1.1 Look for the AI Studio Access banner on the Home screen.

• This banner appears when people inside your sub-accounts still need AI Studio access configured.

• Use the Home banner to open the user access setup.

2.1 Click Configure on the AI Studio Access banner.

• This opens the area where you can choose which users should receive AI Studio Access.

• Decide whether you want to give access to everyone or only specific people.

3.1 Select the individual users who need AI Studio.

• This option works well when only certain staff, VAs, contractors, or client users need access.

3.2 Review your selections before confirming.

• Make sure the users you selected actually need AI Studio Access based on their role.

• Submit your user selections so GoHighLevel can apply the new permissions.

4.1 Confirm the access changes.

• GoHighLevel will begin setting up AI Studio for the users you selected.

Note: The changelog confirms the Home banner, Configure option, user search and selection, access for everyone or specific users, and the general setup time. It does not provide every current button label or screen detail beyond those points, so the steps above avoid adding unsupported interface details.

The AI Studio Access banner is not shown to every user inside GoHighLevel. It only appears for people who have enough access to manage AI Studio permissions.

Agency owners can see the banner.

Agency admins can also see it.

Agency users with write access can see it too, which means they can help manage who gets AI Studio Access across the sub-accounts they can control.

Sub-account users do not see the banner.

Read-only agency users do not see it either.

This matters when someone says, “I don’t see the AI Studio banner.” In many cases, that does not mean the feature is missing. It may simply mean that the user does not have the right permission level to configure access.

If you’re handling AI Studio access, make sure you’re signed in at the agency level with a user that can actually manage permissions. When there are still people to set up, the banner should show on Home.

So the banner does two jobs: it helps you set access up, and it lets you know when there are still users who haven’t been enabled.

Just because AI Studio is available doesn’t mean everyone in the account needs it.

Look at how each person uses the account. Someone working on content, workflows, or planning may need AI Studio often. Someone who mostly checks appointments or updates contacts may barely use it.

You also don’t have to use the “everyone” option just because it’s faster.

For agencies with VAs, contractors, or client logins, it often makes more sense to turn access on only for the people who need it.

It’s a good idea to see who already had AI Studio turned on through Labs. Their access carries over, which means there may be nothing else to do for them.

If someone’s responsibilities change, their access may need to change too. The same goes for anyone who leaves the team or no longer uses AI Studio.

Keep it simple: give people the tools they need for the job they’re doing.

This change gives agencies more room to set up users properly.

Your team probably isn’t made up of people doing identical jobs. One person may be building automations, another may be writing content, and a client user may only be logging in to check leads.

Those users don’t all need the same tools.

With AI Studio, you can now be more selective about who gets access.

That’s useful for keeping things organized, but it also helps people stay focused on the parts of GHL they actually use.

It also makes adding new users a little easier. Instead of giving everyone the same permissions, you can set up each person based on what they’ll actually be doing.

For larger agencies, that can make account management much less messy.

AI Studio Access is now live across GoHighLevel, but the rollout comes with an important change: not every sub-account user automatically gets access.

That means agency owners and admins should take a few minutes to review who actually needs AI Studio and configure access from the Home banner.

For users who already had AI Studio enabled through Labs, access stays in place. For everyone else, you can decide whether to enable everyone or only select users.

That extra control is a good thing.

It helps agencies keep permissions cleaner, gives teams access based on their actual roles, and makes it easier to manage AI tools across multiple sub-accounts.

If AI Studio is going to become part of your team’s daily workflow, now is the time to get those permissions sorted.

Have you already set up AI Studio Access for your team, or are you still deciding who should get it?