In most cases, these users will also build dashboards for reporting information to their respective department/ team. This role includes all the Patch Reader permissions.ģ) Patch User: This role is designed for the operators of the Patching job, who interact and manage patching activities on a regular basis. This role has only view permissions on assigned jobs, assessment profiles, and dashboards.Ģ) Patch Dashboard Author: This is a special role that would be needed only for larger organizations that delegate development of dashboards to a dedicated team especially, one that does NOT operate/ manage the patching jobs. This role is granted to allow users viewing/ read-only capabilities in the Dashboards developed to provide an insight into the Patching operations. Each role, except Patch Security, is an incremental role to the previous one.ġ) Patch Reader: This is the default role designed to most (sub-)users, present in the system today, with minimum permissions possible. We have 5 OOTB (Out-of-the-box) roles for PM users. Role Based Access Control gives you flexibility to control access to Patch Management features based on the roles of the individual users.Įach user is assigned a pre-defined user role which determines what actions the user can take. User Roles and Permissions for Patch Management
0 Comments
Leave a Reply. |