Better Studio 3.17 gives our AQL assistant a name and a capability upgrade, closes the gaps in how organisations manage users and projects, and gives the community a direct way to shape what is available on Marketplace.
Every one of these changes is intentional and purposeful. Each update responds directly to real feedback from users, and each one makes the everyday experience of building in Studio feel more intuitive and enjoyable. Here’s the thinking behind Studio 3.17.
Meet Bea, your AI AQL assistant
An AI assistant only earns trust once users can rely on it consistently. And with that we are committed to consistent and constant improvements of our models. We have initially launched:
- An AQL assistant that can create simple queries and check for errors in existing ones.
- An AI supported documentation search that would help find the answers to our users’ most common questions quickly and efficiently.
We have improved the documentation search in previous releases, so now it was time for AQL to get an upgrade.
First and foremost, in our objective to unify all AI capabilities within Studio, we’ve given the AQL assistant a name: Bea.
With Studio 3.17, Bea can also keep better track of context across a conversation, and interpret relative time expressions such as “last month” correctly.
Take a look at the new capabilities in the video below:
The most significant change is how Bea handles complexity. For queries that genuinely need more than one AQL, Bea can now combine them into a JS View and return JavaScript instead of forcing a single-query answer that does not fit the question. Straightforward queries still get a straightforward single-AQL response.
User management on the organisation level
User management in Studio has, until now, mostly meant one thing: an admin looking after members within a couple of projects with the help of the Studio support team. And while that works well for a small-sized team, it breaks down if an organisation wants consistent oversight across multiple projects and bigger teams.
Studio 3.17 does not introduce user management as a new idea but rather expands the organisation-level structure so that day-to-day access can actually be handled by those who manage it, not routed around the Studio support team.
An organisation admin can create and manage the projects and users within their organisation directly: Assigning users, removing them or their projects from the organisation when needed. Email notifications keep people informed when their own access changes.
Streamlined suggestions for Marketplace content
One of our core beliefs is that without user input, no product or solution can be successful. User interviews, group sessions, and regular interactions have always brought forward the best ideas and most compelling challenges.
In line with that, we have added a very small, yet powerful change in Marketplace for you. From now on, if you want a new widget, template, form, bundle or another content type, you can simply place your new resource suggestion in Studio. To do so, you simply select Suggest resource in Marketplace, fill in the short form, and we will take it from there.
From feedback to release
The Studio 3.17 release is a set of substantial improvements, which span from an improved AI assistant to a smoother user management experience. This all points towards the same end goal: We want Studio to be easy to use and more efficient with every release we do.
“Studio 3.17 is a good snapshot of how we want to work. We look at where the experience could be smoother, whether that is Bea taking on more complex queries or organisation admins getting more control over their own teams, and we build towards that. Every improvement here traces back to something our users told us, and that will not change.”
— Kseniia Kravets, Product Manager, Better Studio
Your feedback and inspiring creative use of Studio continue to bring real progress and care, and we are excited for what the future will bring in the second half of 2026.
Ready to explore Better Studio 3.17?
