New issue
Advanced search Search tips

Issue 778673 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

FR: Extensions need to be installed per Device

Reported by zpol...@tricountyhightech.com, Oct 26 2017

Issue description

Chrome Version       : 61.0.3163.120
URLs (if applicable) :
Other browsers tested: CHROME OS ONLY

What steps will reproduce the problem?
(1) N/A

What is the expected result?

I would like to be able to push extensions to ChromeOS on a device only basis. Currently the only way to push apps and extensions is per user, but this does not work for our needs. For example, we are currently trying to install device monitors on our student's Chromebooks. This would allow teachers to see what students are doing on their Chromebooks. We would like this set up so the teacher of RM202 only sees the Chromebooks in RM202's Google Org, regardless of who signs into it. 

Not only would this be what we want to happen for our device monitors, but perhaps we setup a Chromebox lab. We may want to push a specific extension to only that lab, again, regardless of who signs into it. 

What happens instead?

The apps are only installed via user. If the extension installs on any Chromebook that a monitored student would sign in to, then there is potential for that student to be monitored on a personal Chromebook. That is not something that we want happening. 

 
Components: Enterprise
Labels: OS-Chrome
Labels: Enterprise-Triaged
Owner: dskaram@chromium.org
Summary: FR: Extensions need to be installed per Device (was: Extensions need to be installed per Device)
David, could you please take a look? Thanks!
Something else that would possibly work for my issue would be the ability to choose to apply policies only to devices associated to our domain, thus excluding those extensions from installing on off-network devices.
Labels: -Type-Bug Type-Feature
Status: Untriaged (was: Unconfirmed)
Any updates to this?

Comment 8 by dskaram@google.com, Mar 19 2018

Owner: maxkirsch@chromium.org
Reassigning to Max. There is work on this front, but it probably won't be in the product before 6-9 months.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment