/build/static/layout/Breadcrumb_cap_w.png

Read only to all tickets in AdminUI

We have a need for a group of users (our Fixed Assets department) to view all tickets as they investigate asset locations.  We do not want them to have modify access to the tickets.  I understand the paradigm for the user UI permissions (read/write, submitter/owner, etc.).

Is there some way we can get those users the data they need without the undesirable side effects of write permissions??


0 Comments   [ + ] Show comments

Answers (4)

Posted by: jknox 12 years ago
Red Belt
4

You can create a read-only role and assign those users to it: Service Desk>Roles

Posted by: chucksteel 12 years ago
Red Belt
1

I don't think that the KACE permissions allow that kind of setup, unfortunately. Your best option might be to create reports that could be delivered to them, but it sounds like they need to search through tickets to get clues to asset locations, is that right?

Honestly if I were in this position I would probably write a quick web based app that connects to the KACE database with the reporting user. It shouldn't take more than an hour or two or so to whip up a quick read only interface to the service desk.

Posted by: grayematter 12 years ago
5th Degree Black Belt
1

Right now we are working with the following:

  • The user has read-only access to inventory and assets.
  • We are associating tickets to machines in inventory where appropriate.
  • The user, in researching a machine's location, sees that there are tickets associated with the inventory record.

Ideally the user would click on the associated ticket in the inventory record to pull up the ticket in read-only mode.  Until we can get this functionality, the user is emailing me the ticket number, I pull up the ticket, and I email it to the user with the "Email Ticket" function.

Posted by: SMal.tmcc 12 years ago
Red Belt
0

Would a CC email give them enough info


Comments:
  • If you are referring to the ticket CC field, that won't work. This research happens independently (and usually long after) of ticket activity. - grayematter 11 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ