About Groups

Code Insight 6.14.2

Groups are used to organize scanned files. System-generated groups are populated with files that share version, component, or license information. For example, if a set of all files points to one license, it might be assigned a group by the system.

Publishing a group allows those working on the project to see the inventory associated with the project or workspace. As a project owner or auditor, you can create groups or assign files to existing groups. Files in a group can come from multiple workspaces in a project. You can view column headings associated with certain component names that refer to Workspaces as well as Projects.

Policies determine if a component in a group is allowed or disallowed. As an auditor, your job is to look all of the files in a workspace and determine which group best explains the existence (or origin) of that file.

When you publish a group in Detector, in effect, you make it visible as inventory that is ready for review to the entire project team. These project team members can view inventory details including a complete file list associated with the inventory item (published group). You can use the Quick Review feature to immediately review each inventory item, or you can use the complete Code Insight workflow to review fully each inventory item using the request form and a formal review process.

The job of the auditor is to fully vet the scanned codebase, and explain the origin of each file by assigning each to appropriate groups. However, once a group is published, it is up to the project team to deal with the review and remediation of the files association with the inventory items (if necessary). Groups that are published from Detector can be viewed by clicking on the Inventory tab in the Project screen.

Recalling a group removes the inventory item from the project. This allows the auditor to do additional analysis on the associated files and re-publish the group or delete it if appropriate.