Closed as "WontFix", if the device policy "Erase all local user info, settings, and state after each sign-out" is enabled, no persistent accounts are kept by Google Chrome OS and all data from the user session will be discarded after logout. Hence, every login it will prompt you to "You're signed in!" screen.

https://www.chromium.org/administrators/policy-list-3#DeviceEphemeralUsersEnabled

The workings of the policy is clear. But students (and teachers) are not happy with the new message popping up all the time. The only option we have is to disable the "erase all local user info" policy. User profiles will be filling up the Chromebooks storage. And even than students will see the message often, because the Chromebooks in elementary schools are shared by students from the whole school. 

Chromebooks (at least the managed ones) should be easy to use for students and hustle-free... I think this change is not in line with this philosophy. 

Please explain why this message must be shown on every "new" device. The info in the message is not related to the specific chromebook but to the account settings that are the same on all chromebooks.

You can Turn Chrome Sync off for users and "You're signed in!" message won't be shown:

https://support.google.com/chrome/a/answer/6309115

Unfortunately turning off Chrome Sync for users does not stop the message from being shown.

I agree with this bug. This should not be labeled won't fix and working as intended.

If the device is enterprise enrolled - this message should not appear. I do not sign in to a windows domain network and get told I am sign in when roaming profiles are enabled. This now prompts the "enterprise user" to open settings and make changes to an already intended flow. 

Using the chrome users-js https://ssl.gstatic.com/accounts/chrome/users-1.0.js was to sync the password to lock the device and not prompt the users for a flow the network administrators did not intend, now we are faced with (yes, a simple) signed in message but again allowing or intriguing users to configure or even attempt to configure settings they have no reason to be doing in the first place.

Please disable or allow enterprise admins to disable this.

For 5 years we have 8000+ students sharing 6000+ Chromebooks without issue.  Google please make this notification go away.

I reopened another ticket since the status of this one was changed to won't fix. Maybe it will catch their attention. 

For me I have erase local info so that it speeds up the device for each individual user and maintains the cloud usability. Having this managed this way is just like windows networks roaming profiles. 

This sync message and options should not be prompted upon sign in for enterprise. If this was for just a regular user then I can understand but for enterprise networks this makes no sense and is taking a step backwards for network admins.

I just noticed that I was wrong in saying that turning off Chrome Sync for users does not stop the message from being shown.

It does stop the message, but the policy seems to take a while to kick in.

Question is: what functionality will the users miss when Chrome Sync is turned off. And I still think the message should not appear in the first place on managed devices with managed accounts.

Yes, I'd also like an answer to maarten's question?

Actually, after reading the Google answer link regrading Chrome Sync I have one questions?  Why in the world would you want to turn that off?  It removes all the benefits of using the cloud based shared experience.  It's not a solution at all.  In fact, I'd guess it would create more problems and frustrate users even more than having to select "ACCEPT AND CONTINUE" at every login.

 Issue 846004  has been merged into this issue.

This is not intended behavior. Students should never be shown a Chrome Sync disclosure regardless of ephemeral mode or not.

My use case is not edu but for corporate. Will this be the case for that as well?

For EDU, Chrome Sync is a core service of the GSuite EDU Agreement and hence falls under the provisions of the Data Processing Amendment. As a data processor, Sync does not show any disclosures to users.

Sync however is not a core server of the G Suite Enterprise Agreement and hence Enteprirse users are treated as consumers and shown the regular disclosures. If admins want to turn Sync off for their Enterpirse users, they can do that via Additional Service page on admin.google.com > Apps. If they want to keep it On though, Chrome will have to show users disclosures as Sync is not a core service for Enterprise, only for EDU.

I consider this a version 66 bug as well and Google administrators need greater control of the message on managed devices. This is impacting our student login experience which needs to be a simple and streamlined as possible. A student is not reading or understanding the agreement and requiring them to accept it at every login serves no real purpose. We erase local data at logoff because our devices are stored on carts and shared among many students and this allows us to manage the performance and storage on the devices.

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a3e0256975e4baaa56be1792d491279c581e6746

commit a3e0256975e4baaa56be1792d491279c581e6746
Author: Aga Wronska <agawronska@chromium.org>
Date: Fri May 25 21:50:23 2018

Add EnableSyncConsent policy.

This is a new User Policy that is used to determine if Sync Consent
should be displayed for the user during login.

TBR=atwilson@chroumium.org

Bug:  841156 
Change-Id: Ibf5e0bdbe7a1037b6c2760032901e3cbe1924146
Reviewed-on: https://chromium-review.googlesource.com/1073623
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562026}
[modify] https://crrev.com/a3e0256975e4baaa56be1792d491279c581e6746/chrome/test/data/policy/policy_test_cases.json
[modify] https://crrev.com/a3e0256975e4baaa56be1792d491279c581e6746/components/policy/resources/policy_templates.json
[modify] https://crrev.com/a3e0256975e4baaa56be1792d491279c581e6746/tools/metrics/histograms/enums.xml

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4eafa1713003d77ffa57491db1bd23ef7dbb93a6

commit 4eafa1713003d77ffa57491db1bd23ef7dbb93a6
Author: Aga Wronska <agawronska@chromium.org>
Date: Sat May 26 00:39:26 2018

Do not show Sync Consent when it is disabled by policy.

TBR=atwilson@chromium.org

Bug:  841156 
Change-Id: I2c559a127a35e0bc0da869b507f1c8000b3c475d
Reviewed-on: https://chromium-review.googlesource.com/1074187
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562085}
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/browser/chromeos/login/screens/sync_consent_screen.cc
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/browser/chromeos/preferences.cc
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/browser/policy/configuration_policy_handler_list_factory.cc
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/common/pref_names.cc
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/common/pref_names.h
[modify] https://crrev.com/4eafa1713003d77ffa57491db1bd23ef7dbb93a6/chrome/test/data/policy/policy_test_cases.json

Are #20, #21 fixes for this RBS?  If so please follow with a merge request soon since stable is approaching.  Thanks

Adding M66 to also track merge request for it once changes are confirmed

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/74f8b7cce8b5b3d1870b1f1a53b4421b4c368085

commit 74f8b7cce8b5b3d1870b1f1a53b4421b4c368085
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 19:52:34 2018

Add EnableSyncConsent policy.

This is a new User Policy that is used to determine if Sync Consent
should be displayed for the user during login.

TBR=atwilson@chroumium.org

Bug:  841156 
Change-Id: Ibf5e0bdbe7a1037b6c2760032901e3cbe1924146
Reviewed-on: https://chromium-review.googlesource.com/1073623
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562026}(cherry picked from commit a3e0256975e4baaa56be1792d491279c581e6746)
Reviewed-on: https://chromium-review.googlesource.com/1077030
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#32}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/74f8b7cce8b5b3d1870b1f1a53b4421b4c368085/chrome/test/data/policy/policy_test_cases.json
[modify] https://crrev.com/74f8b7cce8b5b3d1870b1f1a53b4421b4c368085/components/policy/resources/policy_templates.json
[modify] https://crrev.com/74f8b7cce8b5b3d1870b1f1a53b4421b4c368085/tools/metrics/histograms/enums.xml

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/13bfcac28559ca352db1d3f0315ad7c125040bed

commit 13bfcac28559ca352db1d3f0315ad7c125040bed
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 20:14:26 2018

Do not show Sync Consent when it is disabled by policy.

TBR=atwilson@chromium.org

Bug:  841156 
Change-Id: I2c559a127a35e0bc0da869b507f1c8000b3c475d
Reviewed-on: https://chromium-review.googlesource.com/1074187
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562085}(cherry picked from commit 4eafa1713003d77ffa57491db1bd23ef7dbb93a6)
Reviewed-on: https://chromium-review.googlesource.com/1077031
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#33}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/browser/chromeos/login/screens/sync_consent_screen.cc
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/browser/chromeos/preferences.cc
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/browser/policy/configuration_policy_handler_list_factory.cc
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/common/pref_names.cc
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/common/pref_names.h
[modify] https://crrev.com/13bfcac28559ca352db1d3f0315ad7c125040bed/chrome/test/data/policy/policy_test_cases.json

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cbd81807e5e667c506e9a6df003a55d2ae71a794

commit cbd81807e5e667c506e9a6df003a55d2ae71a794
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 21:07:46 2018

Add EnableSyncConsent policy.

This is a new User Policy that is used to determine if Sync Consent
should be displayed for the user during login.

TBR=atwilson@chroumium.org

(cherry picked from commit a3e0256975e4baaa56be1792d491279c581e6746)

Bug:  841156 
Change-Id: Ibf5e0bdbe7a1037b6c2760032901e3cbe1924146
Reviewed-on: https://chromium-review.googlesource.com/1073623
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562026}
Reviewed-on: https://chromium-review.googlesource.com/1077190
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/branch-heads/3359@{#850}
Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276}
[modify] https://crrev.com/cbd81807e5e667c506e9a6df003a55d2ae71a794/chrome/test/data/policy/policy_test_cases.json
[modify] https://crrev.com/cbd81807e5e667c506e9a6df003a55d2ae71a794/components/policy/resources/policy_templates.json
[modify] https://crrev.com/cbd81807e5e667c506e9a6df003a55d2ae71a794/tools/metrics/histograms/enums.xml

I thought that merges are already requested and approved for this issue as I was focused on cherry-picking.

Kevin, I am sorry for asking for approval post-factum.

I manually cherry picked the changes, resolved conflicts and  build them.

I added M68, since the initial changes were landed on Friday after branch.

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/453d3b264a428a0bcbadcbb78dd777660140c346

commit 453d3b264a428a0bcbadcbb78dd777660140c346
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 21:31:22 2018

Do not show Sync Consent when it is disabled by policy.

TBR=atwilson@chromium.org

(cherry picked from commit 4eafa1713003d77ffa57491db1bd23ef7dbb93a6)

Bug:  841156 
Change-Id: I2c559a127a35e0bc0da869b507f1c8000b3c475d
Reviewed-on: https://chromium-review.googlesource.com/1074187
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562085}
Reviewed-on: https://chromium-review.googlesource.com/1077310
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/branch-heads/3359@{#851}
Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276}
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/browser/chromeos/login/screens/sync_consent_screen.cc
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/browser/chromeos/preferences.cc
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/browser/policy/configuration_policy_handler_list_factory.cc
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/common/pref_names.cc
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/common/pref_names.h
[modify] https://crrev.com/453d3b264a428a0bcbadcbb78dd777660140c346/chrome/test/data/policy/policy_test_cases.json

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/857a4b4b8d92ce8ca17aa019ed51407e016f7b01

commit 857a4b4b8d92ce8ca17aa019ed51407e016f7b01
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 22:35:27 2018

Add EnableSyncConsent policy.

This is a new User Policy that is used to determine if Sync Consent
should be displayed for the user during login.

TBR=agawronska@chromium.org, atwilson@chroumium.org

(cherry picked from commit a3e0256975e4baaa56be1792d491279c581e6746)

Bug:  841156 
Change-Id: Ibf5e0bdbe7a1037b6c2760032901e3cbe1924146
Reviewed-on: https://chromium-review.googlesource.com/1073623
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562026}
Reviewed-on: https://chromium-review.googlesource.com/1077382
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/branch-heads/3396@{#716}
Cr-Branched-From: 9ef2aa869bc7bc0c089e255d698cca6e47d6b038-refs/heads/master@{#550428}
[modify] https://crrev.com/857a4b4b8d92ce8ca17aa019ed51407e016f7b01/chrome/test/data/policy/policy_test_cases.json
[modify] https://crrev.com/857a4b4b8d92ce8ca17aa019ed51407e016f7b01/components/policy/resources/policy_templates.json
[modify] https://crrev.com/857a4b4b8d92ce8ca17aa019ed51407e016f7b01/tools/metrics/histograms/enums.xml

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/188da952711d206961ac3c8f6b37880b4c6d2828

commit 188da952711d206961ac3c8f6b37880b4c6d2828
Author: Aga Wronska <agawronska@chromium.org>
Date: Tue May 29 23:44:25 2018

Do not show Sync Consent when it is disabled by policy.

TBR=agawronska@chromium.org, atwilson@chromium.org

(cherry picked from commit 4eafa1713003d77ffa57491db1bd23ef7dbb93a6)

Bug:  841156 
Change-Id: I2c559a127a35e0bc0da869b507f1c8000b3c475d
Reviewed-on: https://chromium-review.googlesource.com/1074187
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562085}
Reviewed-on: https://chromium-review.googlesource.com/1077490
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/branch-heads/3396@{#718}
Cr-Branched-From: 9ef2aa869bc7bc0c089e255d698cca6e47d6b038-refs/heads/master@{#550428}
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/browser/chromeos/login/screens/sync_consent_screen.cc
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/browser/chromeos/preferences.cc
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/browser/policy/configuration_policy_handler_list_factory.cc
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/common/pref_names.cc
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/common/pref_names.h
[modify] https://crrev.com/188da952711d206961ac3c8f6b37880b4c6d2828/chrome/test/data/policy/policy_test_cases.json

re c#27: Approvals were done as per email/chat. Removing request labels since  all branches are now up-to-date with these merges 

Please mark bug as fixed if no additional CLs are expected 

Where in the G Suite Admin Console are we supposed to go to suppress the consent?

Hi team, may we know what version exactly this fix was applied? We have a customer that's still experiencing the issue.

I have not seen an update on the Chrome Devices I have for testing.

Also where in the Admin Console where we find this policy?

The fix is in 10452.99.0 which should be available for devices that is available to most devices, some devices may not get it for a few more days though.

The policy is automatically set for EDU users, there will be no admin console setting.

I performed a ChromeOS update on a device I was having this issue with and it did resolve it.  Thank you.

So how would I enable this in a corporate environment ? My whole point is that a windows network which we can enable roaming profiles on (not storing the user profile) is the same type of setup we are looking to have and now I have this pop up which breaks our intended user environment.

Not happy about this.

j...@leadtrust.io, My apologies, I forgot to mention I'm an Administrator for a G Suite for Education customer.  However, the required behavior of no more prompt, is happening.

(bump)

Need this resolved as a setting for corporate env.

For non-EDU accounts, please reference https://bugs.chromium.org/p/chromium/issues/detail?id=841156#c14