Four HubSpot updates from May 1: AEO LinkedIn drafts, Customer Success Rooms scope, multiple permission sets per user, and Sandboxes Roadmap visibility.
44:06
HubSpot Updates: May 1, 2026
Four updates landed in HubSpot's product updates feed on Friday, May 1, 2026, and they cluster around a theme: HubSpot is putting more weight on what happens after the sale. Two of them are evolutions of features we have seen before. Customer Success Rooms got a clarification that narrows what is actually in the beta today, and AEO LinkedIn content generation expanded from articles to posts. The other two, multiple permission sets per user and the Sandboxes Roadmap, are admin-side improvements that have been quietly requested for a long time.
If you watched the show today, you already heard the conversation around two of these. If you did not: Watch the recap to hear our thoughts on these updates and more.
Platform Updates Detailed
Generate LinkedIn Articles and Posts from AEO Recommendations
HubSpot's AEO tool now supports AI-generated LinkedIn posts in addition to articles, with drafts created directly inside HubSpot's social tool for editing, scheduling, and publishing. The tool already tracks how AI engines like ChatGPT, Gemini, and Perplexity respond to questions about your brand and recommends LinkedIn topics when LinkedIn is being cited in those answers. The new piece is the path from recommendation to draft, all inside HubSpot. If you have Brand Voice set up, the draft will reflect it. This is in private beta for Marketing Hub Professional and Enterprise customers enrolled in the AEO beta.
Why it matters: Buyers are increasingly asking AI engines for recommendations instead of searching the web, and LinkedIn is among the most commonly cited sources in those answers. AEO already tells you what to write to close the visibility gap. The bottleneck has been turning that recommendation into a published draft. This update closes most of that gap, and the fact that HubSpot is treating LinkedIn as a strategic surface for AI visibility tells you something about where they think attention is going.
For more details: AEO LinkedIn article and post generation private beta.
Customer Success Rooms
Customer Success Rooms is a shared workspace where customers and customer success managers can track project tasks, forms, and (eventually) documents and status updates inside one portal. Friday's update was a clarification: the current private beta supports task sharing and form submission. Document sharing and status updates are coming later. Rooms are created automatically through workflows triggered by events like deal close or project creation, and by default, all contacts associated with the project get access. Tasks tied to a customer on a project where Project Type equals Service - Onboarding will surface inside the room. Available for Service Hub Professional and Enterprise.
Why it matters: The shared Google sheet of who is doing what during onboarding has been overdue for replacement for years, and this is the more interesting half of where HubSpot is heading. Combined with the billing portal that opened in private beta last week, Customer Success Rooms is part of a larger move toward an Amazon-style customer experience inside HubSpot. One place where customers can see everything they have ever done with you. Not there yet, but the pieces are showing up.
For more details: Customer Success Rooms private beta.
Multiple Permission Sets per User
Admins will be able to assign multiple permission sets to a single user, with the most permissive combination of permissions taking precedence. Today's permission system requires admins to either build custom sets for every variation or manage individual permissions one user at a time, which gets messy fast when someone wears two hats. This is in public beta for Content, Marketing, Operations, Sales, and Service Hub Enterprise.
Why it matters: The cleanest example is the person who does both sales and marketing, or the team lead who needs slightly elevated access on top of their function-specific permissions. Today, admins handle this by creating one-off custom sets that nobody else can use, or by manually adjusting individual permissions and hoping they remember to revoke them later. Stacking permission sets is how this should have worked from the start. For larger Enterprise portals, this will quietly remove a category of admin overhead.
For more details: Multiple permission sets per user public beta.
See What's on the Sandboxes Roadmap
Admins can now see the sandboxes roadmap directly inside HubSpot, including upcoming betas and additional asset support, and share feedback on which asset types should be supported next. Previously, finding out which asset types worked in sandboxes meant searching the documentation or asking support. The roadmap lives behind a megaphone icon at Settings > Sandboxes. Available across Enterprise tiers (Commerce, Content, Marketing, Data, Sales, Service, and Smart CRM).
Why it matters: Sandbox planning is a quiet pain point for anyone running a complex portal. Knowing what is and is not testable in a sandbox before you start a build saves the rebuild later. Roadmap visibility also means you can time when you create a new sandbox to take advantage of new asset support, which is the kind of small efficiency that adds up across an admin's year.
For more details: Sandboxes Roadmap visibility.
Key Takeaways and Next Steps
Post-sale tooling is getting real: Customer Success Rooms and the recent billing portal beta are pieces of a larger move toward a unified customer experience inside HubSpot. If you are running Service Hub Professional or higher, the CS Rooms beta is worth requesting now so your team has time to shape the configuration before document sharing and status updates land.
AEO is becoming a content workflow, not a reporting tool: The first AEO release told you whether AI engines were citing your brand. The next ones told you what to write. Now AEO drafts the post for you. If you are on Marketing Hub Professional or Enterprise and have not enrolled in the AEO beta, this is a reason to.
Admin overhead is getting smaller in small ways: Multiple permission sets and Sandboxes Roadmap visibility are not headline features, but they are the kind of updates that quietly remove friction for the people running large portals. Worth flagging for any admin on your team who has been working around either of these limitations.
Produced by Value-First Media