Overview
Report tags help you organize, categorize, and manage vulnerability reports across your organization. They are lightweight and intuitive, which makes it easier to filter, group, and prioritize findings.
Tags are scoped at the organization level and can be reused across all reports; this consistency supports better workflows, dashboards, and integrations.
Getting Started
Create Report Tags
To create a report tag (organization admin only):
Go to Organization settings.
Select Report Tags in the left navigation.
Click Add Tag.
Enter a name, then click Add Tag to finish.
To rename a tag later, select the edit icon next to it.
Add Tags to a Report
Option 1: From a Report
Open the report.
In the right panel, find Tags, then select the edit icon.
Choose one or more tags from the dropdown, then click Save.
To remove a tag, open the editor again and select the × next to the tag.
Option 2: From the Findings View
Open the findings view.
Add the Tags column to the table.
Add a tag to the report you want to update.
Option 3: Via the API
Automate tag management using the Update Report Tags API endpoint; this is useful for custom scripts.
Frequently Asked Questions
Can I rename a tag across all reports?
Yes. Renaming updates the existing tag and preserves all current associations. Manage this in organization settings.
Are tags visible to researchers?
No. Report tags are internal and only visible to organization members.
Can I use special characters in tags?
Most characters are supported (including hyphens and underscores). Tags are automatically converted to lowercase; leading and trailing whitespace is removed.
What’s the difference between tags and custom fields?
Tags are quick, reusable labels for any report. Custom fields (engagement level) are structured, support specific data types, and include validation. Use tags for flexible categorization and workflow management; use custom fields when you need structured data collection.
Tips
Keep names short and consistent so teams can scan and filter quickly. We recommend defining a small, shared taxonomy before tagging at scale.
Example taxonomy:Severity:
critical,high,medium,lowEnvironment:
prod,staging,devSource:
automated-scan,pentest,bug-bountyStatus:
triaged,in-progress,resolved
Use bold text when referring to UI elements such as buttons, menus, and field labels.
Aim for clear, concise steps; favor present tense and active voice.
Avoid em dashes by default; use semicolons or separate sentences when appropriate.
Next Steps
Create your first set of organization-wide tags in Organization settings → Report Tags.
Add the Tags column to your findings view to standardize usage across the team.
If you need automation, integrate with the Update Report Tags API endpoint.