4 ms·

BAH. "This Google Account isn’t supported" "Bard does not currently support Google Workspace accounts or when our systems indicate you may be under 18." Smoo

by akulbe 4y ago

BAH. "This Google Account isn’t supported" "Bard does not currently support Google Workspace accounts or when our systems indicate you may be under 18." Smooth move, Google. PAYING Workspace customers should be the first ones to get access. This blows my mind. Oh wait, no… it doesn't. They did this with other devices and apps too. You couldn't use your Workspace account. You had to use a personal account. Really dumb. You'd think they would give the good stuff to the people PAYING them, first.

tsejerome97 4y ago
prolly some legal stuff
- kevincox 4y ago
  This is the reason. The Google Workspace agreements has strong promises about how you data is used. IIRC there is a section about not using your data to improve the service for others. So this means that they would be unable to train the model with data from workspace users (other than fine-tuning which is only used by that specific account). For MVP they don't have the correct labeling and filtering in place to be sure that they aren't using Workspace data in a way that isn't allowed so they take the easy route and disable the service. This is the reason why many Google features and services are not available or are missing features for Workspace accounts. Of course it would be nice to be able to opt-in either globally or by service and accept that these interactions are not protected with the usual data rules. But this takes even more effort and legal work to implement, so no one has bothered.
- cmsj 4y ago
  A Googler explained it to me once - it's something like as if the Workspace accounts are on a completely different instance of Google, and supporting both in an app is surprisingly hard. Still, after all this time the geniuses at Google kinda ought to have solved this :)
  - sangnoir 4y ago
    > Still, after all this time the geniuses at Google kinda ought to have solved this :) It won't be solved until the day Google stops selling ads. Regular Google accounts are designed to vacuum up any useful user data and use it to improve Google services in any way Google chooses, and they may update the terms with a EULA updates. Workspace accounts are the opposite: user data is controlled by the account admin, and agreement is not with individual users, but their org. Beta releases work well when information can be freely gathered and reported upstream. The nature and class of information collected may change over time, and is not covered under Workspaces agreements
andykellr 4y ago
Also I can't switch to a personal account. Only option is to log out of all accounts. Other tabs (gmail, etc) show all accounts and let me switch. Not bard.
- jmkni 4y ago
  Go back to Google homepage and switch there, then back to Bard
  - 331c8c71 4y ago
    Yeah, but it's Google. Don't they have employees to think a bit and check the possible scenarios? It's kind of obvious that some people have multiple accounts and not being able to switch right there is sickening.
- brandmeyer 4y ago
  Shout-out to Firefox Multi-Account Containers, which Just Works (TM) for exactly this use case.
- rezonant 4y ago
  Ugh, the Google Play Console had this issue for a very long time. How is this not completely unified and identical across all G products by now?
- falcor84 4y ago
  I just found that you can append `/u/1/` (or whatever logged-in account id) to the url to switch between them - it's only the GUI that's missing.
- pclark 4y ago
  What a lousy bug
tumetab1 4y ago
I think the "Workspace" rule is just a simple check if it's a company account and I think it's the right choice to disable access for employees unless strictly authorized by Workspace manager.... and that feature probably does not exist yet for Workspace admins.
crazygringo 4y ago
> PAYING Workspace customers should be the first ones to get access. That has virtually never been the case, it's generally always the opposite. Because IT admins need advance time to decide whether to enable features for parts of their org or not, and to implement or update training materials. Also if a feature breaks it's worse if you're paying. Not to mention all the additional regulations around data retention/location/etc. that sometimes have to be implemented, that free accounts don't have to worry about. So Google generally rolls out new features to free accounts first, and then it comes to paid once fully tested at scale and compliant and admins have had time to evaluate for their institutions. This is a feature, not a bug.

by akulbe 4y ago

tsejerome97 4y ago

prolly some legal stuff

kevincox 4y ago
This is the reason. The Google Workspace agreements has strong promises about how you data is used. IIRC there is a section about not using your data to improve the service for others. So this means that they would be unable to train the model with data from workspace users (other than fine-tuning which is only used by that specific account). For MVP they don't have the correct labeling and filtering in place to be sure that they aren't using Workspace data in a way that isn't allowed so they take the easy route and disable the service. This is the reason why many Google features and services are not available or are missing features for Workspace accounts. Of course it would be nice to be able to opt-in either globally or by service and accept that these interactions are not protected with the usual data rules. But this takes even more effort and legal work to implement, so no one has bothered.
cmsj 4y ago
A Googler explained it to me once - it's something like as if the Workspace accounts are on a completely different instance of Google, and supporting both in an app is surprisingly hard. Still, after all this time the geniuses at Google kinda ought to have solved this :)
- sangnoir 4y ago
  > Still, after all this time the geniuses at Google kinda ought to have solved this :) It won't be solved until the day Google stops selling ads. Regular Google accounts are designed to vacuum up any useful user data and use it to improve Google services in any way Google chooses, and they may update the terms with a EULA updates. Workspace accounts are the opposite: user data is controlled by the account admin, and agreement is not with individual users, but their org. Beta releases work well when information can be freely gathered and reported upstream. The nature and class of information collected may change over time, and is not covered under Workspaces agreements

andykellr 4y ago

Also I can't switch to a personal account. Only option is to log out of all accounts. Other tabs (gmail, etc) show all accounts and let me switch. Not bard.

jmkni 4y ago
Go back to Google homepage and switch there, then back to Bard
- 331c8c71 4y ago
  Yeah, but it's Google. Don't they have employees to think a bit and check the possible scenarios? It's kind of obvious that some people have multiple accounts and not being able to switch right there is sickening.
brandmeyer 4y ago
Shout-out to Firefox Multi-Account Containers, which Just Works (TM) for exactly this use case.
rezonant 4y ago
Ugh, the Google Play Console had this issue for a very long time. How is this not completely unified and identical across all G products by now?
falcor84 4y ago
I just found that you can append `/u/1/` (or whatever logged-in account id) to the url to switch between them - it's only the GUI that's missing.
pclark 4y ago
What a lousy bug

tumetab1 4y ago

I think the "Workspace" rule is just a simple check if it's a company account and I think it's the right choice to disable access for employees unless strictly authorized by Workspace manager.... and that feature probably does not exist yet for Workspace admins.

crazygringo 4y ago

> PAYING Workspace customers should be the first ones to get access. That has virtually never been the case, it's generally always the opposite. Because IT admins need advance time to decide whether to enable features for parts of their org or not, and to implement or update training materials. Also if a feature breaks it's worse if you're paying. Not to mention all the additional regulations around data retention/location/etc. that sometimes have to be implemented, that free accounts don't have to worry about. So Google generally rolls out new features to free accounts first, and then it comes to paid once fully tested at scale and compliant and admins have had time to evaluate for their institutions. This is a feature, not a bug.