Make the new Chat AI button appear: Workspace rollout checklist

A teammate sends a screenshot: the new AI button is missing. You have a small team, an admin, and a launch to plan. The button appears only when plan eligibility, required settings, and rollout timing line up.

Google began releasing Ask Gemini in Chat on August 26, 2026, as a single input in Google Chat that can query Gmail, Drive, and Calendar. The ops lead owns the sequence: confirm the account is allowed, turn on the required settings, and wait for the release to reach the domain. For a small company, that split saves time: the founder asks for the capability, the admin confirms the plan, and the ops lead tracks the rollout.

The button is gated before it is visible

It depends on organization-level Gemini in Workspace in Chat and Workspace Intelligence settings, plus Workspace Smart Features enrollment, rather than an individual user toggle. The company does not choose the day it appears. It chooses whether the account is ready when the release arrives.

The checklist runs before the announcement

Use this list when a teammate asks why the button is missing. Each item is a quick check, and each one points to a different failure mode. Keep it with the rollout note so the team can see the order of the work.

• Confirm plan eligibility: Google Workspace Business Starter customers and personal Gmail accounts without a Workspace subscription are not eligible for Ask Gemini in Chat.
• Enable the organization-level Gemini in Workspace in Chat and Workspace Intelligence settings.
• Verify Workspace Smart Features enrollment for the people who need the button.
• Allow up to 15 days for feature visibility on both Rapid Release and Scheduled Release domains.
• Set language expectations: Ask Gemini in Chat initially applies only to accounts whose Google account language is English, while users with other language preferences continue using the previous Gemini side panel.

If the plan is not eligible, no setting creates the button. The settings checks make the feature available inside an eligible account. The timing window keeps the team from treating a missing button as a broken rollout, and the language limit prevents a quiet mismatch between what some users see and what others see.

Before you enable anything, write a short note for the team. Say what the button does, who should see it, when to expect it, and what to do if it is missing. Send it before the rollout window starts, so the team knows the timeline. That note becomes the reference when a question arrives, and it keeps the founder from making a public promise before the admin has finished the checks.

Make the rollout a standing ops item

Name an owner before the team starts asking questions. That owner checks the admin settings, records what changed, and tells the group when to look again. The owner does not need to be the founder; the person who can open the admin console and keep a short note is the right one.

Decide which roles need the button. The enrollment step is where you keep it out of accounts that do not need it. A small team may only need it for customer-facing people, or only for the ops lead. The smaller the group, the easier it is to watch for confusion.

Keep the note small: record the plan, the settings, the enrollment, the date you enabled them, and the language limits. If the button is missing after the release window, start with that note. It tells you whether the problem is eligibility, a setting, timing, or a user expectation.

Put a follow-up in the team calendar. The admin can finish the checklist and still wait. Check again after the window closes, then send one update: what is live, who should see it, and where to ask if it is missing. Treat the feature as an operations item, confirm readiness, and let the owner report the result in the next ops meeting.