Gemini added 14 Connected Apps. The permission screen is now part of the product

The launch expands Gemini from answering into operating

Google began rolling out fourteen new Connected Apps on 23 September 2026. The list covers work systems, creative tools and consumer services rather than one narrow category. In Google's examples, a conversation can move from organising a database to creating a design, building a website or finding an event ticket without opening a separate browser tab for every task.

The important change is action. Google's help documentation says Connected Apps can give Gemini permission to edit and manage content in another service, depending on the integration's supported actions. That makes the connection more consequential than a search plug-in. A useful response can now depend on identity, third-party permissions and the state of a remote account.

The 14 partners fall into three different permission profiles

Partners named by Google in the September rollout

Group	Connected Apps	Likely task boundary to inspect
Productivity	Airtable, Linear, monday.com, PandaDoc, Wispr AI, Zoho	Read project records, create or edit work items, documents and notes
Creativity	Adobe, Picsart, Squarespace, Webflow	Generate assets or change content on a publishing surface
Lifestyle	Apartments.com, Experian, Peloton, SeatGeek	Search personal services, use account context or initiate a consumer task

Those rows should not be treated as one generic access level. Searching public apartment listings is different from reading a private project board. Drafting an image is different from publishing a website change. Checking credit information carries a different sensitivity from finding event tickets.

Google directs users to each app's detail page for its supported and unsupported actions. That detail matters more than the brand list. Before connecting a service, check whether Gemini can only retrieve information, can create drafts, or can make a change that becomes visible to colleagues or customers.

An @ mention can select an app, but Gemini may also choose one automatically

On the web, a user can type @ and select an app. If it is not connected, Gemini may connect it or request permission. Google's help page also says some Connected Apps are designed to work automatically and that Gemini can automatically use an available app for a request.

This creates two separate controls: which apps are connected, and which app is intended for a particular prompt. Naming the app explicitly is useful when a request could match several systems. A project update that belongs in Linear should not be left ambiguous if monday.com and Airtable are connected to the same account.

For higher-impact actions, the prompt should also name the object and desired result: create a draft, update one named record, or summarise without editing. Specific instructions reduce the chance that a broadly capable integration takes a technically supported but unwanted action.

Keep Activity is an availability switch as well as a history setting

Google says Connected Apps are unavailable on Gemini's web app, iOS and smart watches when Keep Activity is off. Android retains a smaller set consisting of Device assistance, Phone, Messages and WhatsApp. Public information from Google Search remains available even when the user is signed out or Keep Activity is off; some other public Google services require it to be on.

That distinction can surprise users who think they changed only a history preference. Turning the setting off changes which integrations Gemini can use. Teams writing support instructions should therefore record both the connection state and the Keep Activity state when diagnosing why an app is missing.

A five-minute review is enough to make the rollout safer

The useful comparison is capability multiplied by permission

The headline number is fourteen, but the operational story is the range of authority behind those connections. Connected Apps can save tab switching and transfer context into useful work. They also make consent, account scope and action review part of the quality of the answer.

A good integration is not simply one that completes the task. It makes the selected service, proposed action and final effect clear enough that the user can approve the right boundary.