Quick summary
Use submission custom fields for dynamic, report-specific context.
Use asset custom fields for static, organizational context that applies across reports.
Both types can be exported and used for filtering.
Table of contents
1. What are custom fields?
Custom fields let you enrich submissions and assets with structured, company-specific data. They help you:
Streamline internal workflows
Improve reporting and exports
Filter information more effectively
All custom field values are visible only to your internal team, not to researchers.
2. Submission vs. Asset custom fields
Type | Best for | Examples of fields | Purpose |
Submission custom fields | Tracking vulnerability-specific context that varies per report | - Internal status (e.g. “In triage”, “Pending fix validation”) | Provides a structured alternative to tagging for consistent tracking, filtering, and reporting at report level. |
Asset custom fields | Capturing organizational context shared across all reports for the same asset | - Asset owner (e.g. “John Doe”) | Defines static context once at the asset level, avoiding repetitive mapping and keeping data consistent across reports. |
💡 Tip: Use both together. Submission fields for dynamic details, asset fields for static context.
3. Who can create custom fields?
Company & Program Administrators: Can add, edit, and archive submission fields.
Other roles: Can update field values for submissions in programs they have access to.
Program & Group Readers: Cannot update field values.
4. Submission custom fields
4.1 Create submission custom fields
Go to your program and navigate to More → Custom fields.
Click Create a custom field.
Choose a type:
Text: Editable free text.
Dropdown: Predefined list of options.
Toggle: On/off switch.
Name your field and define options (if Dropdown).
Click Save. The field appears on all submissions for that program.
💡Tips:
Use Dropdown for standardized values you’ll filter or report on.
Field types can’t be changed later. Create a new one if needed.
4.2 Update a submission’s custom field
Open a submission.
In the right-hand panel, find the Custom fields section.
Enter or select a value.
Text and Toggle save automatically.
Some fields require clicking the Save icon.
4.3 Manage submission fields
Edit: Go to More → Custom fields, click the three dots next to the field, then select Edit.
You can rename it or update dropdown options. (Type cannot be changed.)Archive: Click Archive custom field, confirm, and the field will no longer appear on submissions or exports.
5. Asset custom fields
Use asset-level fields to store static context that applies to all submissions linked to that asset.
Examples:
Asset owner
Development team
Business unit
Region
Environment (Production, Staging, Test)
This avoids repeating the same data on each submission and keeps reporting consistent.
5.1 Create asset custom fields
Go to your program’s Assets.
Open an asset or asset settings → Custom fields.
Click Create a custom field.
Choose a type:
Text: Editable free text.
Dropdown: Predefined options.
Toggle: On/off switch.
Name the field and define options (if Dropdown).
Click Save.
💡Tips:
Use Dropdown for standardized reporting.
Field types cannot be changed after creation. If needed, create a new field and migrate values.
6. Exports
Submission exports (CSV): Include submission custom fields and values.
Batch submission exports (CSV): Include submission and asset custom fields too — letting you connect vulnerabilities with business context for deeper analysis.
7. Filtering by custom fields
Go to your Submission overview.
Click Show filters.
Scroll to Custom fields.
Select the fields and values you want to filter by.
In short
Submission custom fields: Dynamic, report-level context (status, team, risk score).
Asset custom fields: Static, asset-level context (owner, environment, business unit).
Together: They reduce manual work and improve structure, filtering, and reporting.