SoftwareCentral · Applications

Application Delegation (Package Security Groups)

Decide which security roles can see which software.

Package Security Groups Security roles

1 Delegate applications

Applications are delegated to users by assigning them to Package Security Groups, and then assigning the Package Security Group to one or more Security Roles.

  1. Create Package Security Groups under Settings › Package Security Groups. See Package Security Groups.
  2. Assign packages to them in Assign Packages to Security Groups, or from the Software tab of the group itself. See Assign Packages to Security Groups.
  3. Assign the Package Security Group to one or more security roles from the Security Roles interface, or from the group’s own Security Roles tab.
Unassigned applications By default, applications that are not assigned to any Package Security Group, or only to shopping security groups, are available to all users in SoftwareCentral, except in the Shop.

A group marked Only apply to the shop is a shopping group: its memberships are ignored everywhere except in the shop. In the shop, membership of the group’s AD-Groups, Entra ID groups or user collections decides who sees the items.

For an example, see Package Security Group Example - Keep Test and Production packages separate on the same SCCM.

2 Best practice

  • Plan the groups around who should see what (department, location, test or production) before you create them.
  • Remember that software in no group is visible to everyone; assign new applications to a group straight away, or let a template do it.
  • Use a separate shopping group for software that should only be orderable by certain people in the shop, without limiting the helpdesk.