VibeletsHow to create and share a collection
Put task lists, notes and other apps on one page, then choose who can open it.
- 01Bring apps together
Create a collection for one audience.
- 02Shape the page
Arrange apps, text and images.
- 03Invite your people
Choose public or restricted access.
A prompt you can start with
Build a simple team idea backlog. Each idea has a title, a short description, an owner and a status: New, Considering or Done. Let us filter by status and keep the data shared. I will add this vibelet to our team collection beside our task list.
Opens in Studio, ready to edit. Building starts when you send it.
Compare a vague request with a specific one.
Put everything in one huge app.
Keep our task list and idea backlog as separate vibelets, and bring them together in one team collection.
Read the full guide
A collection brings your vibelets together on a page of your own. Use it for a team workspace, a family hub or a set of tools for your customers. The Explore vibelets under Community is the separate public library where people discover and remix community creations.
1. Create your collection
Sign in to Studio and open My collections beside your profile. Choose Create new collection, give it a title and choose its web address. You can create several collections for different projects or audiences.
2. Add the vibelets that belong together
Use Publish to collection from a vibelet’s workspace menu or preview actions. Choose the collection and the version to publish. You can include the same vibelet in more than one collection.
You can also build a new vibelet from the collection page. For example, put a task list, meeting notes and an idea backlog in one team hub, so people don’t need to keep track of three different links.
3. Arrange the apps, text and images
Open the collection and choose Manage collection → Edit page. Add text, images and sections, arrange your vibelets and display them as cards or embedded apps people can use right on the page.
Use Describe changes to ask for a different look or a more complete solution. Try: “Make this a welcoming team hub with a short introduction, our task list and meeting notes side by side.” Review the proposal before accepting and publishing it. Changes to existing vibelets can also affect their other sharing links, so check the result before publishing.
4. Choose who can use it
Make a collection public or restrict it to selected registered users. In a restricted collection, its dedicated vibelet links follow the collection’s membership. In a public collection, individual vibelets can still require sign-in or access for named recipients.
Give members a Viewer or Contributor role. Contributors can send copies of their own vibelets into your collection; you own and manage the accepted copies. Share the collection’s page link as one starting point for your audience.
5. Configure shared data and AI budgets
Adding apps to a collection doesn’t automatically connect their data. Enable data sharing when you want vibelets to use each other’s data, then describe the connection in your prompt. For example: “Use the customer list from our CRM when choosing a customer for a quote.” Permissions still apply; check the data-sharing settings carefully before sharing publicly.
Each collection has a monthly AI usage budget. AI used through its collection links consumes the owner’s credits and counts towards that budget. Building and background automations have their own existing billing and limits; the collection budget isn’t a cap on everything your account does.