/build/static/layout/Breadcrumb_cap_w.png

K1000 - Restricting Process Tickets per User

We want to create various Process tickets for departments, but we only want people in those departments to be able to see and create the Processes specific to their department. We do not want separate queues. For example, HR would see the process ONBOARD NEW HR HIRE, but maintenance would see ONBOARD NEW MAINTENANCE HIRE. Can this be done? I am not seeing where to define the user labels who have approval to create a process in the process templates section. Thanks!

1 Comment   [ + ] Show comment
  • You probably won't achieve that without creating separate queues. Kace uses labels to separate the different queues. - Druis 7 years ago
    • Bummer. We really wanted to avoid having dozens of queues, but I guess that is what we will have to do. Thanks for your time! - taylora 7 years ago

Answers (2)

Answer Summary:
Posted by: Hobbsy 7 years ago
Red Belt
2

Top Answer

The challenge here is that different processes may require different ticket data, hence the need for separate queues, If the new HR hire and New Maintenance Hire tickets contain identical information, there is no reason why they could not both share a queue for the initial ticket and the process then branch into separate queues or tickets. Also you can restrict the view of processes by un-ticking display process to all users then creating labels of authorised users.

Comments:
  • Un-ticking "Display Process to All Users" is exactly what I was looking for. I can create labels such as "HR Manager" and add the users I would need in that group then only give HR Manager access to view that process. Thanks! - taylora 7 years ago
Posted by: Hobbsy 7 years ago
Red Belt
0
The challenge here is that different processes may require different ticket data, hence the need for separate queues, If the new HR hire and New Maintenance Hire tickets contain identical information, there is no reason why they could not both share a queue for the initial ticket and the process then branch into separate queues or tickets. Also you can restrict the view of processes by un-ticking display process to all users then creating labels of authorised users.

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