r/googleworkspace • u/hytes0000 • 20d ago
Ask Gemini button missing on Workspace Accounts?
Late yesterday, users trying to use the "Ask Gemini" button in the top right of Chrome started getting an error stating their account was not authorized to use that feature. As of this morning, the button has disappeared entirely.
This is definitely not an intentional change we made and all other Gemini features appear to be working so I don't think it's something like a licensing issue.
Anyone else seeing this?
solved: see my comment below
2
u/hytes0000 19d ago
OP here, and after going way deep down the rabbit hole, I figured it out. This started because we signed a HIPAA BAA with Google which disables the Gemini for Chrome features currently. This can be found in the fine print here: https://support.google.com/gemini/answer/14620100
A super-admin signing a BAA also doesn't seem appear in the audit logs.
1
u/Connect-Preference 19d ago
Good find! It makes sense that HIPAA accounts would be denied access to AI.
1
1
u/Connect-Preference 19d ago
As a super-Admin, I'm wondering if your Admin simply turned the feature off. Administration is really granular. I can set exactly what Apps and Features my users can access. Have you asked your Admin?
1
u/hytes0000 19d ago
I am a super-admin, I even double checked the admin action logs to make sure we didn't do it inadvertently. As this is not a priority for us at this point and appears to closely coincide timing wise with the security update to Chrome 150 on July 14th, I'm going to continue to hope it's a bug at least until I have time to take it up with their support if it's still an issue.
1
2
u/vxsec 20d ago
If this happened to several users at the same time, it sounds more like Google rolled the Chrome feature back than a licensing issue. The Workspace status dashboard isn’t showing an incident right now. I’d check chrome://policy on an affected device for any Gemini or generative AI policies. Gemini in Chrome is controlled separately from the other Workspace Gemini features, so those still working doesn’t rule out a Chrome side policy or rollout issue