Cloud Print Report that will track users who tried printing file that exceeded the file size limit. |
||||
Issue descriptionDescription: Customer wants to be able to generate a report that will allow him to check users usage from the Google Cloud printer that he shared. Use case: On multiple occasions they have had students print very large jobs hundreds of times over to waste resources. This can be costly but they cannot track it from the Chrome devices as the Cloud Print Service is registered with a generic print account that they created. By adding this feature, it will be easier for them to see and track who is printing more than 40 MB file size limit that causing a delay from the print jobs queue and when. Motivation: Motivations behind this feature would be to cut down on resources being wasted in an organization. Printing can become costly and it can become expensive if our staff isn’t able to catch it in time. Most of the time, print jobs stuck on queue and sometime it's showing In progress and they need to check it every time. If this feature is enabled, all users that prints more than 40 MB file will personally informed and they will not do it in the future. Existing workarounds: Unaware of any workarounds to fix this issue.
,
May 18 2017
I also have another customer who wants to have this feature wherein they want to identify the user who sends out a specific print job. Below is their scenario why they are also requesting for it. *Description:*In an environment where Chromebook devices are assigned printers according to the OU they're placed in, it is necessary to be able to see which user printed a print job from a particular device. *Use case:*We had a student send 999 copies of a 40 page document to a printer. If someone wasn't there to notice what was going on and stop the printer, it would've exhausted the entire contents of the printer (around 10,000 sheets of paper if fully loaded). It's important to know who is sending large jobs to printers so the administration can take the proper steps to deal with the offending student. Another use case would be if a student sends offensive or threatening content to a printer from a District Chromebook. Currently we would have no way of tracing who sent the threatening content to a printer. *Motivation:*Given the first scenario, there's an environmental and financial impact. In the second situation, being able to find the culprit internally would speed an investigation significantly and help determine the seriousness of the situation. The current alternative would require the local police needing to subpoena Google for information regarding the threat sent by a District device to a District printer if we're required to assume every situation we can't immediately explain requires maximum response. *Existing workarounds:* Disallow students from all printing privileges, which is not possible because the District curriculum requires students to print some documents.
,
Jul 24 2017
,
Apr 13 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||
►
Sign in to add a comment |
||||
Comment 1 by pmarko@chromium.org
, Mar 20 2017