...
Please note that each role includes at least the permissions of the roles below it. For example, if someone should be a content creator, you do not need to add them to the field support or helpdesk role since the content creator role already includes all the permissions from the more limited roles.
The roles below are listed in order of permissions. The first item on the list has the most permissions and the last item on the list has the least.
Roles
- LANDesk Administrator
...
The Group Admin role is limited to those invidividuals within the University who use LANDesk extensively and need access to many of the less commonly used features. This role has access to Patch Management.
- Content Creator (Security Group: LANDesk ContentCreator Role)
Content Creator has very similar permissions to field support. The primary differences are that content creators can edit and create scripts, distribution packages, delivery methods, and provisioning templates. Content creator is also the lowest group that has the ability to view software license monitoring information.
- Field Support (Security Group: LANDesk FieldSupport Role)
Field support is the role most often used for anyone who does a lot of desktop support. Similar to the helpdesk role, field support can use remote control tools, view security and patch information, and view reports. The field support role has the ability to view and deploy scripts, LANDesk agents, software packages, provisioning templates, and can edit reports.
- Content Creator (Security Group: LANDesk ContentCreator Role)
Content Creator has very similar permissions to field support. The primary differences are that content creators can edit and create scripts, distribution packages, delivery methods, and provisioning templates. Content creator is also the lowest group that has the ability to view software license monitoring information.
- Help Desk (Security Group: LANDesk HelpDesk Role)
...