Studió AI

I had AI Studio create a beautiful one time offer for me only to find out, I cannot port it over into a GHL Funnel. So AI Studio is a silo'd app that really doesn't integrate with much of anything else in GHL. Crazy. This would be a huge competitive game changer if made possible. Just saying.

Would be great to be able to create a database for the app. Or, securely stored API credentials for external data sources.

Currently, when you publish an AI Studio project and add a custom domain, each project requires its own unique domain or subdomain. This means that if you manage 50+ projects as an agency, you end up with 50+ separate DNS records in Cloudflare (or any other DNS provider) — which is completely unmanageable at scale. What I'd love to see: The ability to set one custom base domain (e.g. preview.myagency.com ) and have each AI Studio project automatically published under a unique path, like: preview.myagency.com/client-one preview.myagency.com/client-two preview.myagency.com/saas-dashboard This way, you only need one DNS record for all your productions. Clean, scalable, and professional. Bonus feature request: Add a "Deploy to Account" button inside AI Studio. When clicked, it lets you select a sub-account and automatically pushes the AI Studio production (page, funnel, website) directly into that account as a funnel or website — no copy-pasting, no rebuilding. This would make AI Studio a true production tool for agencies, not just a prototyping sandbox. This combination would make AI Studio incredibly powerful for white-label agencies running dozens or hundreds of client accounts.

The title says it all!! Hopefully we'll be able to do this soon!

Currently, if we build an e-commerce website, the AI can build the UI. Still, it actually never integrates with the CRM payment modules, even though we have integrated a payment gateway inside the CRM. They have no connection at all. Since the AI studio can only create front-end applications, it is not appropriate to store payment keys and secrets on the front-end, so this must be handled by the CRM system. Also, for the products and orders, they need to be able to 1 key integrate with the AI studio ecommerce site and the CRM system. So when the website receives orders, it can sync to the CRM system. When we list new products, they shall be able to show in the respective shop/collection/product pages. It is more like the eCommerce website created by AI studio is a headless front end, and the CRM system is the CMS system, like the Shopify or WooCommerce Backend.

Since we are bale to view the source, why don't allow us to edit the code directly, as sometimes only need to update some text, no need to ask AI Agent to do it?

We'd love to see dedicated permission toggles added for AI Studio and Vibe Coding within the user Roles & Permissions settings at the sub-account level. Currently, the only AI-related permission available at the sub-account user level is AI Agents, which doesn't cover access to AI Studio or Vibe Coding. As these are powerful (and potentially sensitive) tools, it's important for sub-account admins to be able to control which team members have access to them. As an admin managing a sub-account with a team of varying roles and responsibilities, I need the ability to restrict access to AI Studio and Vibe Coding on a per-user basis, without affecting other permissions. Not all users within a sub-account should have access to these advanced features, and right now there's no way to limit that at the sub-account level. If you could: Add a parent toggle for AI Studio under sub-account Roles & Permissions and...include granular sub-permissions (e.g., View only vs. View & Manage)

To make the AI studio friendly to a Web Design Agency, I suggest adding a menu item: Transfer Ownership. The logic of this operation: After the user clicks this, a popup to ask which location ID to transfer to. Then, the web design agency will ask for the client's location ID, paste it, and submit. A confirmation action needs to be done, similar to deleting anything in the system. The recipient client's company email (Or all user Admins) will receive an email, asking them to confirm the receipt of the web app. If they reject, then the web app will be at the original location and one web app can only be transferred 1 time per day to avoid flood actions. This will help the design agencies to design a web app for clients in their own account and transfer it to their clients' account location after it is done. Similar to Shopify Client transfer store (Previously called development store).

Add a microphone to use here please!

There are elements that are consistent on multiple pages or even all pages, like headers and footers. I think it is absolutely mandatory to have something like this for AI Studió to work on larger sites. Otherwise every time we do an adjustment in these common elements, we have to go through every page and do the same adjustment. Ideally I would say we would need to create "global" content blocks. I'm using this term from Elementor. But the idea is that we need elements that get updated on every page simultaneously when edit is done.