Securing Print Manager by a Group Structure

Sort:
You are not authorized to post a reply.
Author
Messages
JackNoody
New Member
Posts: 3
New Member
    Has anyone out there used a group structure to secure the print manager (Gen Username element specifically)?

    What we have is a hierarchy scenario when it comes to securing the job queues, and print manager.
    For Example:
    At the lowest level our facility can only see there own jobs/print files. Employees at Corporate can see their own jobs, and any facility that they are in charge of. There are also some other scenarios, but we will keep it simple for now.

    Our plan was to create a structure, and assign groups to the nodes.  Then we would use the expression "user.isAboveInStruct" to apply our logic.

    If anyone has used group structures to secure the print manager any help would be greatly appreciated.
    layzer1
    New Member
    Posts: 2
    New Member
      Here is an example of a rule that will allow the user to see the User Names of those having
      HRGROUP assigned in Group attribute value as well as their own User Name:
      UserName==user.getHostServiceId()||isMemberOf('HRGROUP',UserName)
      'All_ACCESS,'
      else
      'NO_ACCESS,'
      Or
      UserName==user.getHostServiceId()||isMemberOf('HRGROUP',UserName)&&user.isMemberOf('HR
      GROUP')
      'ALL_ACCESS,'
      else
      'NO_ACCESS,'
      Note: This second example allows the user to see their own User Name but also any user associated
      to HRGROUP as long as the user is also a member of HRGROUP. First example does not check
      user’s membership in the group just grants all User Names who are assigned the HRGROUP.
      You are not authorized to post a reply.