Site Engagement Score should be settable through enterprise policy |
||||||||
Issue descriptionDescription: Today, Site Engagement Score (chrome://site-engagement/) is set through use. Some enterprises may want to pre-populate (or set) important sites to high (or low) engagement to force specific behavior. Use case: Email clients that are adopted enterprise wide may wish to be able to grant features like Persistent Storage (https://www.chromestatus.com/features/5715811364765696) to critical enterprise apps (e.g., mail clients and creativity tools). Motivation: This is product request from a Google team, but moving major line-of-business apps in general to the web requires durability for things like storage and ways to ensure it. Today, apps like Google Docs and Mail use Chrome Extensions to provide this durability. Existing workarounds: None.
,
Dec 6 2016
,
Dec 6 2016
omg...
,
Dec 6 2016
Would it be simpler to have an enterprise setting for durable storage?
,
Dec 6 2016
How would the setting be applied? Would it require the user to be signed in to Chrome with their enterprise account? What if they're not, would they not get durable storage then?
,
Dec 7 2016
I'm not fully across how enterprise policy works, however, I'm fairly sure it's possible to apply policies using a file-based mechanism, not just enterprise account logins.
,
Dec 10 2016
From the discussion above, it's not clear to me which type of "policies" were meant here. Typical enterprise policies are applied for managed users and/or enrolled devices (see e.g. https://support.google.com/chrome/a/answer/187202 for reference). There's generally no way to get an enterprise policy for a not managed user on a non-corporate device. Also, though I don't have enough context on the Site Engagement feature, I would support comment #4: policies are usually designed to control the specific features with a clear scope (while the statistics provided by the Site Engagement, AFAICS, may be used in a variety of pieces - for instance, for Flash plugin blocking).
,
Dec 12 2016
It feels to me that faking site engagement is rather the wrong way to achieve the goal intended. I agree that instead a policy could directly grant whatever special goodies - storage etc. related to high scores. Assigning to blumberg for further triage and prioritization.
,
Dec 12 2016
From what I understand, if there are any configured policies for https://www.chromium.org/administrators/policy-list-3#PluginsAllowedForUrls site engagement scoring is disabled. Alex, can you ping me off-thread and explain a bit of the backstory from the Google Team that is requesting this? I'd like to understand the use-case a bit more. Thanks,
,
Dec 12 2016
#9: site engagement scoring is independent of plugins. Html5ByDefault is a client of engagement; the PluginsAllowedForUrls policy simply controls whether plugins can be overridden by admins and forced on or off (avoiding a site engagement score check). It does not disable the underlying site engagement accumulation and does not affect other features (like durable storage) which use engagement.
,
Dec 15 2016
Thank you all for the data points. This FR is on hold for now and will be re-reviewed next quarter re:priority. Thanks
,
Apr 13 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by benwells@chromium.org
, Dec 6 2016