Error when deploying app using HubSpot CLI

RKhaire
Member

I’m deploying a User Level App using the HubSpot CLI and I’m getting a permission error saying I cannot set isUserLevel: true. How to enable User Level Apps for my developer account?

0 Upvotes
1 Accepted solution
BérangèreL
Solution
Community Manager
Community Manager

Hi @RKhaire and welcome, it's a pleasure to have you here!

To enable user-level apps (isUserLevel: true) for your developer account, you need to join the HubSpot MCP server (remote) beta. This is a prerequisite for creating user-level apps.

Here is how to "Opt your HubSpot account into a beta feature".

Also, let's consult our Top Experts: Hi @Bryantworks@jpsanchez and @evaldas do you have other suggestions to help @RKhaire, please?

Have a wonderful day! 🌞
Bérangère





loop


Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth.

Learn More




View solution in original post

0 Upvotes
2 Replies 2
BérangèreL
Solution
Community Manager
Community Manager

Hi @RKhaire and welcome, it's a pleasure to have you here!

To enable user-level apps (isUserLevel: true) for your developer account, you need to join the HubSpot MCP server (remote) beta. This is a prerequisite for creating user-level apps.

Here is how to "Opt your HubSpot account into a beta feature".

Also, let's consult our Top Experts: Hi @Bryantworks@jpsanchez and @evaldas do you have other suggestions to help @RKhaire, please?

Have a wonderful day! 🌞
Bérangère





loop


Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth.

Learn More




0 Upvotes
MuhammadAmjad
Participant

Just adding to what Berangere shared, the permission error you're hitting is actually pretty common when starting with user-level apps. Here's what I've found helpful when working through this exact scenario.

Once you've joined the MCP server beta and opted into the beta feature like Berangere mentioned, there's usually a small delay before everything propagates through your account. Sometimes simply logging out of the CLI and logging back in after the beta access is enabled can resolve those lingering permission issues.

Also worth checking is your hubspot.config.yml file to make sure the account ID matches the one you've enabled beta access for. I've seen cases where developers have multiple accounts configured and the CLI is trying to deploy to the wrong one. Running hs accounts list can help you verify which account is currently active.

If you're still hitting permission errors after the beta access is confirmed, try clearing your local CLI cache and re-authenticating completely. That usually clears up any stale credentials that might be causing the isUserLevel permission rejection.

0 Upvotes