Key takeaways:
Assets groups are managed on program level.
Program Admins/Editors can create/remove asset groups, add/remove assets to/from the group and add a group description.
Who this article is for:
Company Admins
Program Admins
Program Editors
What are asset groups
An asset group represents a logical cluster of assets within your program’s scope. They’re designed to make your scope easier to browse, understand, and maintain especially for programs with a large scope.
Asset groups can be used to separate assets by product line, environment, or other logical categories. Organizing assets this way helps researchers quickly browse through your program's scope and identify where to focus their testing.
How to manage asset groups
Program Admins and Editors manage how assets are grouped:
Create groups: Add new groups to organize your program’s scope.
Delete groups: Remove outdated or redundant groups when your program structure changes.
Order groups: Adjust the display order of your asset groups to make the most important or highest-priority ones appear first. A clear, logical order helps researchers navigate your scope more efficiently.
Add group description: Add program-specific descriptions to groups within your scope.
Add asset to a group: Assign existing assets to the appropriate group.
Remove assets from a group: Clean up groups as your scope evolves.
Best Practices:
👍 Use meaningful group names with a clear purpose.
👍 Add concise descriptions to provide context at the group level, this reduces the need for repeating information on individual assets.
👍 Keep groups balanced in size and scope to make browsing easier for researchers.
👎 Create overlapping or duplicate groups with similar assets, this can cause confusion for both your team and researchers.
Common pitfalls:
Using a single asset (e.g., with type Other) as a “pseudo-group” containing multiple assets in its description.