How to allow users to view other users print jobs

unknown

Greetings,

We just went live with LP and our HR staff would like to be able to follow our Accounting staff as they process through the new Payroll steps. They want to be able to view the accounting jobs.

I contacted INFOR support and I was told the only way would be to place all of the employees into the same LAUA Security Class.

I tested, and it does work. But I prefer to keep those employees seperated in LAUA security.

So I found a document that suggest flagging the two groups "Supervisor Class" as "Yes". I did that, and Hr employees can see other users jobs in other classes.....BUT, it appears that a couple of employees with admin rights or more priviledges can't be seen by users with less security ???? So as a member of a class with this flag you can see jobs of other users at or below the same security as the user trying to view ???

Our security was set up many years ago and was not documented, so I'm trying to document as I go along to prepare for a migration to LS. It does appear that the two security classes that I'm trying to allow to view each others jobs do indeed have the same scurity settings, so there must be something regarding the user that is different?

Does anybody have any insight on this topic?

unknown

It's been several years since I set all of this up, so I'm going mostly off memory here:
1) If the users are in the same LAUA security class, you can make the users a 'class supervisor' on their profile (think like this: this person is the supervisor for that specific security class). That will let them view and maintain jobs for anyone in that LAUA security class.
2) If they are in different LAUA security classes, you can make the security class a 'supervisor class'. I think that is what you were trying, and it works like this: Let's say you have a security class called SUPER_HR. That security class has access to PA100 but no access to PA105. Anyone in that SUPER_HR security class should be able to view anyone's PA100 from their print manager. But they will NOT be able to view anyone else's PA105.
3) You could also do something with distribution groups so that when folks run whatever job(s) they automatically get distributed to the users who you want to view them.
4) I think you could even make those folks a security officer, but remove LAUA from the environment category so that they can't actually get into LAUA. I think that would allow them to view anyone's print manager for anything that they already have access to.

Note that much of this access, except #3, also gives modify access to the jobs themselves. So there may be some level of risk there that you need to work out for yourself. Hope that helps.