Credential separation for console users

Follow

sean johnson

• January 10, 2018 15:29

I vaguely remember hearing about credentials becoming unique to console users at some point. Is this still being planned or is there a better way to implement the following.

With 6 console users I need to have 2 that only have access to install or scan 2 separate sets of computers (servers and specialty systems). I would like to have all this in the same PDQ Inventory to keep our inventory management all together but I need some way to split up credentials between console users.

 

IE PDQ.Client (given to all desktop support console users)

PDQ.Server (for server admin capable console users)

PDQ.Special (etc...)

 

or is my thinking all out of whack, I welcome any ideas/recomendations. 

1

• 

  Luke Nichols

  • January 10, 2018 20:33

  I asked PDQ support about something similar back in September 2016 and they said it might be possible after the Central Server functionality was released. We've had Central Server for quite a while now but I'm still not aware of any permissions granularity available in PDQ-- you're either a console user with full access or you're not and have no access.

  1

  Comment actions Permalink
• 

  Ze Wong

  • February 07, 2018 02:37

  Just wondering if there's been any progress for this idea?

  We are planning to roll out PDQ Deploy and Inventory to the support staff members but would like to control access differences between a support staff and a senior support staff members. 

  Example, support staff being only able to deploy and senior support be able to generate packages/ approve updates etc.

  0

  Comment actions Permalink
• 

  Jeff Roberts

  • January 03, 2019 23:23

  Has there been any movement on this?

  1

  Comment actions Permalink
• 

  Mark Blackham

  • December 04, 2019 23:36

  I am in the same boat here. Would love to see something like this. 

  1

  Comment actions Permalink
• 

  Robert Steele

  • December 13, 2019 15:56

  I would love it if PDQ could implement this. I have several administrators that I only want to be able to deploy packages in PDQd and view collections in PDQi, and 1/2 admins that should have the capacity to create new collections and packages. Would be great though, if it could be even more granular, and allow one admin access to a Folder of packages, and another access to a different folder of packages. 

  Separation of duties, and all.

  1

  Comment actions Permalink
• 

  Seth Leary

  • August 25, 2020 14:55
  • Edited

  Agreed. Duh, really. Should have been on the whiteboard as a critical piece during initial design. I've used PDQ in the past and am trying to sell my current employer on it, but this is the big hurdle. It's hard to argue against their concerns.

  1

  Comment actions Permalink
• 

  Manny Lopez

  • March 26, 2021 22:26

  Would like to see this implemented as well.  Thanks!

  1

  Comment actions Permalink

Please sign in to leave a comment.