Google Labs introduced Tabletop on November 11, a group-planning experiment rolling out through a U.S. waitlist for people aged 18 and older.

The big change

  • Tabletop turns supplied material into shared interactive tools. Google describes inviting a group to use the resulting space simultaneously.
  • An invitation and a permission rule answer different questions. Before putting sensitive details into any shared tool, establish who can read or change them and what happens if its link is forwarded.
  • A waitlist is not immediate access. We could not verify Tabletop’s pricing, retention, training or human-review terms, and rules for other Google products should not be substituted.

From an idea to a shared plan

Google says users add links, files and ideas, then prompt @tabletop or select a template. Examples include itineraries, dinner polls, expense splitters and tournament brackets; creators send an invite link to their group chat.

In the trip example, the proposal becomes something friends can work with together rather than a static answer one person forwards. That describes the intended workflow, not a tested itinerary or confirmed booking.

BIG CHANGE has not tested Tabletop. Our product-page retrieval failed, so we cannot verify additional controls or availability details. Before entering real names or spending plans, check the service’s current terms and settings.

Generated tools have a history

The idea of generating a tool rather than receiving only an answer predates this announcement. Google’s March 2025 Canvas introduction described creating and editing documents and code inside Gemini. Its example was an email subscription form: ask for the HTML, preview the form, request changes to fields or buttons, then inspect the updated preview.

That example makes the distinction concrete. The generated output is an interface someone can interact with, and revising the request changes that interface. The earlier announcement also described exporting written content to Google Docs for collaboration. These are historical Canvas capabilities, not evidence about Tabletop’s implementation or current permissions.

The link is only part of the decision

Google’s separate Canvas safety guidance explains why sharing rules deserve their own check. For a multi-user Canvas app, anyone with its public link can view and edit associated data. The guidance contrasts that with an app that does not share data between users, whose stored data is private to the person using it.

That is Canvas policy, not a finding about Tabletop. A familiar provider name does not establish that two products have the same access model.

The same Canvas guidance advises recipients to consider who created an app, even when a familiar person sent the link. It warns against entering sensitive information and urges caution over permissions such as camera or microphone access. Those are precautions for Canvas; they illustrate questions to resolve rather than permissions we have observed Tabletop requesting.

For a group choosing a planning tool, usability and access controls are separate decisions.