devguard
Collections

Labels

Labels help you organize and categorize your data, making it easier to filter, search, and manage information across your risks, assets, and policies.

Overview

Labels offer a simple and effective way to categorize and organize information across your organization. They ensure consistent tagging of assets, risks, policies, and other objects, enabling teams to filter, search, and report efficiently while aligning with your organizational taxonomy.

Common examples include High Priority (a label used to mark critical risks or urgent policies), Internal Only (a label applied to documents restricted to internal teams), and Compliant (a label for assets or policies meeting regulatory requirements).

Core Functionality

We provide a central place to manage labels, ensuring consistency and clarity across all modules. Each label includes a name, slug, scope, and color, allowing teams to quickly categorize and filter information.

Users can apply labels to objects and use them for filtering, organizing lists, dashboards, and reports. Labels are integrated across devguard modules, ensuring uniform classification and alignment with organizational workflows.

Changes to labels are instantaneous, updating all linked objects automatically. The system also maintains an audit log to track label modifications over time.

Fields Explained

FieldDescriptionExample
NameThe label’s name, used for display and filteringHigh Priority
SlugUnique identifier generated from the name for linking and referencinghigh-priority
ScopeDefines the context or module where the label applies (optional)Risks, Policies
ColorThe color associated with the label for visual grouping and clarity#FF5733

Export and Import

Labels can be exported and imported from the platform. An export will provide a CSV with all fields, including related metadata. The import does not require all fields. The following is an example of a minimal CSV file:

labels.csv
slug,name,scope,color
high-priority,High Priority,Risks,#FF0000
internal-only,Internal Only,Policies,#1E90FF
compliant,Compliant,Assets,#228B22

Best Practices

  • Use clear, descriptive names that align with your organizational terminology.
  • Apply labels consistently to ensure effective filtering and reporting across modules.
  • Use colors meaningfully (e.g., red for critical, green for compliant) to improve visual clarity.
  • Regularly review and refine labels to avoid duplication or redundancy.
  • Establish clear guidelines for label usage within teams to maintain consistency.

For example, a label such as High Priority with a red color can be applied to critical risks or urgent policies, making them easy to identify in dashboards and reports. Similarly, a label like Compliant with a green color highlights assets that meet regulatory requirements.

Our platform ensures that labels provide clear, consistent, and actionable categorization across your systems, improving visibility and organizational alignment.

How is this guide?

On this page