On Mon, 2016-05-16 at 12:21 +0930, Tim wrote:
Referring to: http://localhost:631/help/policies.html
Part of the cupds.conf file:
#Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
With @OWNER being the owner of the particular print job. They should be able to load up the CUPS webpage http://localhost:631/ (or the hostname of the print server instead of localhost), go to the jobs page, and manage their print job(s).
Just a bit of clarification:
You actually do have "@OWNER" typed in there, you're not supposed to replace OWNER with real user names. It's a variable that *it* works out the meaning of.
Likewise, with @SYSTEM (it's a variable, that it works out what it means). Which most likely is just root, but could include other users with system privileges. I don't know *how* that interpretation would be made (perhaps, such as being in the wheel group), I haven't looked that closely into it.
The original poster had made the point, elsewhere, that they'd tried adding users to different groups. But, I don't recall seeing whether any restarts of software, re-log-in, or reboots, had occurred, so that any changes can be noticed. I'd guess that the CUPS daemon would need a restart, at least.